On Friday March 16, wltjr@xxxxxxxxxx wrote: > > Instead of passing along an interpretation, here are some IRC log > snippets that pertain from #gentoo-dev @ freenode.net > > kingtaco|work: livecd ~ # mdadm --create --level=1 --raid-devices=2 /dev/md0 /dev/sda1 /dev/sdb1 > kingtaco|work: mdadm: /dev/sda1 is too small: 0K > kingtaco|work: mdadm: create aborted > > Now despite suggesting it pretty early on, it took a bit of time to > realize that error was existing only because of file system type. Once > he realized the problem and changed fs type. All was well, and he was > able to create the arrays and move on. > > kingtaco|work: wltjr, see, raidtools would have let me create an array eventhough the type wasn't fs > kingtaco|work: er, fd > kingtaco|work: mdadm just isn't that smart > kingtaco|work: (and that fixed it) > > So ot to sure about the error or why they would get that just because of > file system type. This failure has nothing do to with the partition type. As I mentioned, mdadm doesn't see the partition type at all. When you change the partition type, fdisk (or whatever) normally tells the kernel to reread the partition table. It would seem that the partition table hadn't been read properly before this point, so /dev/sda1 didn't exist. After running fdisk that partition table had been read by the kernel and everything was fine. I.e. it was using fdisk to write the partition table that 'fixed' the problem, not changing the partition type. And the problem was not causes by mdadm but by something else not setting up the partitions properly (or removing them maybe). NeilBrown - 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
