Re: Using a newer mdadm version just for re-adding a device

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

 



On Thu, 31 May 2012 19:24:14 +0200 (CEST) Sven Hartrumpf <hartrumpf@xxxxxxx>
wrote:

> To answer my own question (about a RAID-1):
> 
> Wed, 30 May 2012 19:38:15 +0200 (CEST), I wrote:
> > Is it safe to mix mdadm versions in the following scenario?
> ...
> > Now my question is:
> > Can I safely use the resulting binary (renamed to mdadm325 to avoid confusion)
> > to re-add the device and then continue to use the 3.2.2 package from openSUSE?
> 
> I made a backup and tried the above: it worked perfectly.

I like it when people work out the answer themselves :-)

The only possible issue is that when 3.2.5 adds a new device it will try to
give it a larger "Data Offset".  This won't confuse md, but it might confuse
you in later life.

About the only time you need to ensure you have a consistent version of mdadm
is when re-creating an array that died in some way and you want to recover
the data off it, but "-assemble --force" doesn't work.

NeilBrown

Attachment: signature.asc
Description: PGP signature


[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