Re: raid array with 3T disks and GPT partition

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/09/2011 17:33, Louis-David Mitterrand wrote:
[...]
Auto-assembly and metadata are not related: I regularly use 1.2 metadata
on non-boot partitions and they auto-assemble fine.

Not possible. The kernel will not auto-assemble anything other than 0.90 metadata. You must have mdadm in your initrd.

However lilo won't boot on anything other than 0.9, this I found the
hard way :)

I have had lilo boot from 1.0 metadata just fine. It does need to be the metadata-at-the-end layout though, hence 1.0 but not 1.1 or 1.2.

Kernel auto-assembly seems quite useful and desirable to me, especially
when using, say, initrd to unlock dm-crypt partitions (no need to
configure madadm.conf in the initrd).

Neil Brown took the decision ages ago not to add any more what ought to be userland use-once tools into the kernel, and this is the general direction across the whole kernel. If you have an initrd unlocking a dm-crypt partition you might as well have mdadm in there as well starting your arrays.

BTW, what is that 0xDA type?

Non-FS data.

Cheers,

John.

--
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


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux