Re: RAID1 assembled broken array

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

 



On Thursday September 17, maan@xxxxxxxxxxxxxxx wrote:
> On 07:01, NeilBrown wrote:
> > > Wrong lesson.  The correct lesson to gather from this is to prefer
> > > version 1.1 or 1.2 superblocks wherever possible.  Superblocks at the
> > > beginning of the device disappear when there is no partition table,
> > > superblocks at the end can be confused for superblocks belonging to
> > > the whole device when there is no partition table.
> > 
> > 1.0 also protects from this problem.  The 1.x metadata stores the
> > offset of the superblock from the start of the device.  That will appear
> > to be wrong if you find a partition-superblock when reading from a
> > whole-device, so mdadm will reject the device as not having a valid
> > superblock.
> 
> BTW: Why are new arrays still created with 0.90 metadata format by
> default?

Because I'm a chicken....

I guess it probably is time ... but to we make the default 1.0, which
is compatible with people's expectations, to 1.1 which is generally a
safer approach (you cannot mount a bare device by mistake).

Of course a distro can import their own default using the CREATE line
in mdadm.conf.


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

[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