linux-kernel - Re: tracking down disk spinups.

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200705141628.35617.rob@landley.net>
Date:	Mon, 14 May 2007 16:28:35 -0400
From:	Rob Landley <rob@...dley.net>
To:	Dave Jones <davej@...hat.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: tracking down disk spinups.

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/