public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Rob Landley <rob@landley.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tracking down disk spinups.
Date: Mon, 14 May 2007 16:46:52 -0400	[thread overview]
Message-ID: <20070514204651.GA7242@redhat.com> (raw)
In-Reply-To: <200705141628.35617.rob@landley.net>

On Mon, May 14, 2007 at 04:28:35PM -0400, Rob Landley wrote:
 > On Monday 14 May 2007 2:57 pm, Dave Jones wrote:
 > > Why did the kernel ignore what I told it to do ?
 > > I'm sure it thinks it knows better than me for a reason, but
 > > I'd like to know what it is.
 > 
 > Remount doesn't switch filesystem drivers, it tells the existing filesystem 
 > driver to accept new flags and/or a new option string.

yes, I had misinterpreted what 'remount' did. I thought behind the scenes
it actually did a umount/mount.

 > To switch drivers you have to umount the old sucker and mount the new one.  
 > (The idea of handing off consistent cache data from one mounted filesystem 
 > driver to another...  Ouch.)

a umount would purge the cache, but that's irrelevant given it doesn't
work that way.

Anyways, I rebooted after s/ext3/ext2/ on my fstab, and found things
hadn't really got any more obvious what was going on.
Instead of 'kjournald' writing stuff out, now it's 'pdflush'.

*has sudden brainwave*

Ahh, it's doing atime updates. Duh.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-05-14 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14 18:57 tracking down disk spinups Dave Jones
2007-05-14 19:03 ` Xavier Bestel
2007-05-14 19:21   ` Dave Jones
2007-05-14 19:24 ` Jeremy Fitzhardinge
2007-05-14 19:28   ` Xavier Bestel
2007-05-14 20:12     ` Jan Engelhardt
2007-05-14 20:13 ` Jan Engelhardt
2007-05-14 20:28 ` Rob Landley
2007-05-14 20:46   ` Dave Jones [this message]
2007-05-14 21:02     ` Jan Engelhardt
2007-05-15  4:49     ` Rob Landley

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=20070514204651.GA7242@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox