All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Dave Johnson <dave-lkml-01@centerclick.org>
Cc: Bart Samwel <bart@samwel.tk>,
	linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [ext3] kjournald writing after each read despite noatime,commit=nnn
Date: Thu, 01 Jan 2009 14:16:38 -0600	[thread overview]
Message-ID: <495D24A6.7010707@redhat.com> (raw)
In-Reply-To: <18781.6904.837987.584032@wellington.i202.centerclick.org>

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

      reply	other threads:[~2009-01-01 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31 21:28 [ext3] kjournald writing after each read despite noatime,commit=nnn Dave Johnson
2009-01-01 14:02 ` Bart Samwel
2009-01-01 16:49   ` Dave Johnson
2009-01-01 18:59     ` Bart Samwel
2009-01-01 19:18       ` Dave Johnson
2009-01-01 19:35         ` Dave Johnson
2009-01-01 20:16           ` Eric Sandeen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=495D24A6.7010707@redhat.com \
    --to=sandeen@redhat.com \
    --cc=bart@samwel.tk \
    --cc=dave-lkml-01@centerclick.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.