Hi!
I'm getting problems with raid1 creation using new superblock format.
Kernel used is 2.6.12.2 (with drivers/md and include/linux/raid taken from
2.6.13-rc1 to have a support for bitmaps and bug correction of md
failing when starting resync), all compiled together.
For mdadm I tried both mdadm-2.0-devel-1 and mdadm-2.0-devel-1a.
Compiles only if -Werror is removed from the Makefile, otherwise
/usr/include/asm/byteorder.h:6:2: #warning using private kernel header; include
<endian.h> instead!
raid1 creation with superblock 0.90 goes OK.
However, when I try using superflock version 1, I get the following from
mdadm-2.0-devel-1a:
# mdadm -C -e 1 /dev/md2 -l 1 -n 2 /dev/sdb /dev/sdc
mdadm: /dev/sdb appears to be part of a raid array:
level=1 devices=2 ctime=Tue Jul 5 18:55:26 2005
mdadm: /dev/sdc appears to be part of a raid array:
level=1 devices=2 ctime=Tue Jul 5 18:55:26 2005
Continue creating array? y
mdadm: internal error - sb_offset is wrong
Aborted
(Note that md_p.h already has md_p.h: __u8 pad1[128-100]; /* set
to 0 when written */)
and the following from mdadm-2.0-devel-1:
# mdadm -C -e 1 /dev/md2 -l 1 -n 2 /dev/sdb /dev/sdc
mdadm: /dev/sdb appears to be part of a raid array:
level=1 devices=2 ctime=Tue Jul 5 18:55:26 2005
mdadm: /dev/sdc appears to be part of a raid array:
level=1 devices=2 ctime=Tue Jul 5 18:55:26 2005
Continue creating array? y
VERS = 9002
mdadm: ADD_NEW_DISK for /dev/sdb failed: Device or resource busy
Also I think --zero-superblock doesn't do the job since I tried it,
but the superblock still remains.
Please advise.
Thanks,
Maxim.
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
