On Saturday 26 November 2005 23:32:51, David M. Strang wrote
Please forgive me for pinging you direct on this Neil; but I fear you are
the only one who can answer it.
I am a bit considered by this in the startup log:
Nov 26 21:47:35 xenogenesis kernel: md: raid1 personality registered as nr
3
Nov 26 21:47:35 xenogenesis kernel: md: md driver 0.90.2 MAX_MD_DEVS=256,
MD_SB_DISKS=27
Nov 26 21:47:35 xenogenesis kernel: md: bitmap version 3.39
While mdadm lets me start a v1.0 superblock; I fear that I missing some
level of kernel patch.
Nov 26 21:47:35 xenogenesis kernel: md: Loading md_d0: /dev/sdb1
Nov 26 21:47:35 xenogenesis kernel: md: invalid raid superblock magic on
sdb1
Nov 26 21:47:35 xenogenesis kernel: md: sdb1 has invalid sb, not
importing!
Nov 26 21:47:35 xenogenesis kernel: md: md_import_device returned -22
Just a quick update; I've been putting forth some due diligence on this --
and it appears basically, that do_mounts_md.c is an antique. I've added a
small debug line to md.c under md_import_device; and then also traced thru
the do_mounts_md.c code; and basically the crux of the situation is
do_mounts_md.c doesn't evaluate the superblock of the device and set
SET_ARRAY_INFO for persistent superblocks. So, everything defaults to the
legacy superblock type. (Superblock v0.90.x)
-- David M. Strang
-
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
