On Tue, Nov 16, 2021 at 4:07 AM Wol <antlists@xxxxxxxxxxxxxxx> wrote: > > On 15/11/2021 18:39, Markus Hochholdinger wrote: > > (Because of other reasons, we have intentionally choosen the superblock at the > > end of the device.) > > > > We change the device size of raid1 arrays, which are inside a VM, on a regular > > basis. And afterwards we grow the raid1 while the raid1 is online. Therefore, > > the superblock has to be moved. > > A perfect example of this (although I can't see myself growing the > partitions in this case) is a mirrored /boot. > > Superblock 1.0 means that anything can read the partition without > needing to know about raid. One less thing to go wrong. And I can raid-1 > an EFI partition - I just need to make sure I only modify it from within > linux so it gets mirrored across both drives. I would want that as > protection against my primary drive failing - then my EFI partition is > mirrored letting me boot from the secondary. Hi Wol Thanks for the case. If I understand right, this is a case of using super1.0 right? Because before boot, it can't know this is a raid device. So it can't read data if the raid is created with superblock 1.1 and 1.2. Only super1.0 can be used, Because the data is stored at start of member disk when using super1.0. The system can read partition table even they don't know it's a raid device leg. Regards Xiao
