Re: 0.90 vs 1.X - Differing behavior for device # during fail/remove/add operation

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

 



On Thu, 9 May 2013 11:30:26 -0400 Dusty Mabe <dustymabe@xxxxxxxxx> wrote:

> On Wed, May 8, 2013 at 1:39 PM, Dusty Mabe <dustymabe@xxxxxxxxx> wrote:
> > CentOS 6.3
> > 2.6.32-279.19.1
> > mdadm-3.2.3-9.el6.x86_64
> >
> >
> > I have noticed that the device number printed in the mdstat file gets
> > changed if you fail->remove->add a member device of a 1.X metadata
> > array, but for a 0.90 metadata array the device will go back to the
> > original value once recovery has finished.
> >
> >
> > Is this by design? I know 1.X version of metadata use dev_roles rather
> > than this_disk and the mdp_disk_t structure so maybe it is by design?
> >
> 
> Hey guys.. Sorry to be a pain. Has anyone seen this before? Is it by
> design or a known issue?
> 
It is an unfortunate consequence of incoherent design.
I've occasionally wondered if I should "fix" it.

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