Right. That was 'smart' :D Here's the tar now.
mdadm is as before:
root@ubuntu:/tmp# mdadm -E /dev/sdc /dev/sdc1
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ef584e09:52f1d802:3d7ec530:e2926701
Name : ubuntu:SATAs (local to host ubuntu)
Creation Time : Tue Feb 22 23:50:59 2011
Raid Level : raid6
Raid Devices : 6
Avail Dev Size : 3907028896 (1863.02 GiB 2000.40 GB)
Array Size : 15628114944 (7452.07 GiB 8001.59 GB)
Used Dev Size : 3907028736 (1863.02 GiB 2000.40 GB)
Data Offset : 272 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 59f2e93e:39e5e899:5647c5cf:afe86dee
Update Time : Fri Mar 25 14:57:31 2011
Checksum : 1f74ccf6 - correct
Events : 36
Layout : left-symmetric
Chunk Size : 128K
Device Role : Active device 0
Array State : AAAAAA ('A' == active, '.' == missing)
mdadm: cannot open /dev/sdc1: No such file or directory
But considering I only used Maverick's mdadm to create the array, which
doesn't support DDF1 or Intel MS, I couldn't have used DDF1. Basically
the metadata choice went between 0.9 and 1.2 natives.
So if the Intel/Adaptec BIOS couldn't have created the DDF1 group, and
mdadm couldn't have, how did I end up with double DDF1 metadata on my
disks!?
** Attachment added: "dmraid.tgz"
https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/742145/+attachment/1949169/+files/dmraid.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
ddf1 format should be disabled in dmraid in favor of mdadm
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
