hazel /virtual # mdadm -C /dev/md0 -c 32 -n 4 -l 5
--parity=left-asymmetric missing /dev/etherd/e0.[023]
mdadm: /dev/etherd/e0.0 appears to be part of a raid array:
level=5 devices=4 ctime=Sat Apr 22 13:25:40 2006
mdadm: /dev/etherd/e0.2 appears to be part of a raid array:
level=5 devices=4 ctime=Sat Apr 22 13:25:40 2006
mdadm: /dev/etherd/e0.3 appears to contain an ext2fs file system
size=720300416K mtime=Wed Oct 5 16:39:28 2005
mdadm: /dev/etherd/e0.3 appears to be part of a raid array:
level=5 devices=4 ctime=Sat Apr 22 13:25:40 2006
Continue creating array? y
mdadm: array /dev/md0 started.
hazel /virtual # mount -t ext2 -r /dev/md0 /md0
hazel /virtual # df -H
Filesystem Size Used Avail Use% Mounted on
/dev/hda4 67G 5.8G 58G 10% /
udev 526M 177k 526M 1% /dev
/dev/hda3 8.1G 34M 7.7G 1% /tmp
none 526M 0 526M 0% /dev/shm
/dev/md1 591G 11G 551G 2% /virtual
/dev/md0 591G 54G 507G 10% /md0
now I'm doing a:
(cd /md0 && tar cf - . ) | (cd /virtual/recover/ && tar xvfp -)
thank you thank you thank you thank you thank you thank you
Molle Bestefich wrote:
Jonathan wrote:
Well, the block sizes are back to 32k now, but I still had no luck
mounting /dev/md0 once I created the array.
Ahem, I missed something.
Sorry, the 'a' was hard to spot.
Your array used layout : left-asymmetric, while the superblock you've
just created has layout: left-symmetric.
Try again, but add the option "--parity=left-asymmetric"
-
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
