On 11/21/2016 04:30 PM, Anthony Youngman wrote: > So basically, there's no point using 1.0 for any form of parity raid. In > which case, if you convert a mirror to parity, it would be nice to be > able to create said offset and move the superblock. Not for new parity arrays, no. v1.0 is what you get if you convert an old v0.90 array to v1.x using --assemble --update=metadata. I simply don't know if a v1.0 superblock will run with a non-zero data offset. That would have to be an intermediate step before the superblock and the rest of the metadata could be relocated. >> V1.1 and v1.2 are identical except for the superblock offset (one 4k >> block difference). v1.1 reshapes just like v1.2. >> > Any reason for that difference? How big is the superblock? Did v1.1 fill > most of the first 4K and just leave not much room with a default 4K data > offset initially? v1.1 places the superblock in the first sector of the device. v1.2 skips the first 4k, making such arrays resistant to destruction by accidental creation of MBR partition tables or similar crises. Phil -- 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
