From: Rob Landley <rob@landley.net>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tracking down disk spinups.
Date: Mon, 14 May 2007 16:28:35 -0400 [thread overview]
Message-ID: <200705141628.35617.rob@landley.net> (raw)
In-Reply-To: <20070514185734.GM27604@redhat.com>
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.
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.)
Most filesystem drivers aren't compatible with each other anyway. Sounds like
what you really want to do is put the ext3 driver into "ext2 mode", and stop
journaling. Many people have wanted this over the years, but alas our dream
of "one darn driver for the ext# family" got squashed years ago because
people wanted two different codebases for the same filesystem that could
diverge, require the same bugs to be fixed twice, become incompatible...
Rob
next prev parent reply other threads:[~2007-05-14 20:28 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 [this message]
2007-05-14 20:46 ` Dave Jones
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=200705141628.35617.rob@landley.net \
--to=rob@landley.net \
--cc=davej@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox