Doug Ledford wrote:
On Mon, 2007-10-22 at 16:39 -0400, John Stoffel wrote:
I don't agree completely. I think the superblock location is a key
issue, because if you have a superblock location which moves depending
the filesystem or LVM you use to look at the partition (or full disk)
then you need to be even more careful about how to poke at things.
This is the heart of the matter. When you consider that each file
system and each volume management stack has a superblock, and they some
store their superblocks at the end of devices and some at the beginning,
and they can be stacked, then it becomes next to impossible to make sure
a stacked setup is never recognized incorrectly under any circumstance.
It might be possible if you use static device names, but our users
*long* ago complained very loudly when adding a new disk or removing a
bad disk caused their setup to fail to boot. So, along came mount by
label and auto scans for superblocks. Once you do that, you *really*
need all the superblocks at the same end of a device so when you stack
things, it always works properly.
Let me be devil's advocate, I noted in another post that location might
be raid level dependent. For raid-1 putting the superblock at the end
allows the BIOS to treat a single partition as a bootable unit. For all
other arrangements the end location puts the superblock where it is
slightly more likely to be overwritten, and where it must be moved if
the partition grows or whatever.
There really may be no "right" answer.
--
bill davidsen <davidsen@xxxxxxx>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
