linux-ext4 - Re: [ext3] kjournald writing after each read despite noatime,commit=nnn

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 01 Jan 2009 14:16:38 -0600
From:	Eric Sandeen <sandeen@...hat.com>
To:	Dave Johnson <dave-lkml-01@...terclick.org>
CC:	Bart Samwel <bart@...wel.tk>, linux-kernel@...r.kernel.org,
	linux-ext4@...r.kernel.org
Subject: Re: [ext3] kjournald writing after each read despite noatime,commit=nnn

Dave Johnson wrote:
> Dave Johnson writes:
>> Bart Samwel writes:
>>> This looks like it's a generic property of syncing an ext3 file system.
>>> Try turning off laptop_mode and then running "sync". You will probably
>>> see the same behaviour.
>> yep, every sync() causes a gratuitous write to disk N seconds later
>> even when no data has been read or written since the last sync().
> 
> Woops, correction, every sync() call causes a single gratuitous write,
> no delay.
> 
> $ for n in 1 2 3 4 5; do sync; done
> 
> Jan  1 14:32:54 gw kernel: kjournald(760): WRITE block 2682 on hda1 
> Jan  1 14:32:54 gw kernel: kjournald(760): WRITE block 2684 on hda1 
> Jan  1 14:32:54 gw kernel: kjournald(760): WRITE block 2686 on hda1 
> Jan  1 14:32:54 gw kernel: kjournald(760): WRITE block 2688 on hda1 
> Jan  1 14:32:54 gw kernel: kjournald(760): WRITE block 2690 on hda1 
> 

This may be http://bugzilla.kernel.org/show_bug.cgi?id=12224

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html