RE: OK, Now this is really weird

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

 



> > >> >     So what gives?  /dev/sdk3 no longer even exists, so why hasn't
> it
> > >> > been failed and removed on /dev /md3 like it has on /dev/md1 and
> > >> /dev/md2?
> > >>
> > >> Is it possible there has been no I/O request for /dev/md3 since
> > >> /dev/sdk failed?
> > >
> > >        Well, I thought about that.  It's swap space, so I suppose it's
> > > possible.  I would have thought, however, that mdadm would fail a
> missing
> > > member whether there is any I/O or not.
> > >
> > > --
> > > 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
> > >
> >
> > I thought so as well. But how will mdadm know is the device is faulty,
> > unless the device is generating errors? (which usually only happens on
> > read and/or write)
> 
> With very recent mdadm the command
> 
>    mdadm -If sdXX
> 
> will find any md array that has /dev/sdXX as a member and will fail and
> remove it.

	No, it's version 3.1.4, and that gives me a "Device or Resource
busy" error.  It does report that it set sdk3 faulty, but the hot remove
fails.

	So how can I remove the drive (so I can add it back)?

--
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