On Fri Feb 08, 2013 at 11:22:20 -0800, Keith Keller wrote:
> Hi again everyone,
>
> On 2013-02-07, Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > # mdadm /dev/md127 --remove /dev/sdg
> > mdadm: hot remove failed for /dev/sdg: Device or resource busy
>
> In poking around a little bit more, I have noticed something strange
> about sdg. While the controller does not think that the device exists,
> it seems like udev still does (see below). Could this be the root of
> the problem, and if so, what would be the canonical way of cleaning up
> after the device failure? I realize that this may be a udev issue, not
> md, so feel free to point me elsewhere if that's the case. (I stumbled
> across this when I tried to do mdadm --remove detached; when it failed,
> I wondered whether sdg had not been completely and cleanly detached.)
>
> I do feel like it would be handy to be able to tell mdadm that the
> device is really gone, and remove it even if it still seems available.
> From my reading of man mdadm --remove does not accept the --force
> switch; would it make sense to apply it to a scenario like this?
>
"mdadm --remove failed" would probably be best. There's also
"mdadm --remove missing" which is the other option in these
circumstances.
HTH,
Robin
--
___
( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
Attachment:
pgp5vQgigSYzx.pgp
Description: PGP signature
