> -----Original Message----- > From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid- > owner@xxxxxxxxxxxxxxx] On Behalf Of Robin Hill > Sent: Friday, February 26, 2010 9:42 AM > To: linux-raid@xxxxxxxxxxxxxxx > Subject: Re: mdadm 3.1.1 fails to hot remove device - No such device or > address > > On Fri Feb 26, 2010 at 08:37:51AM -0500, Foster_Brian@xxxxxxx wrote: > > > Hi Neil, > > > > We run mdadm in a NAS framework and recently updated to 3.1.1 after > > using older revs for quite some time. We recently observed an issue > > where we've been unable to hot remove a failed device from an array, > > where that member device has been physically removed from the system. > > 'mdadm /dev/md# -r /dev/sdg#' returns a "No such device or address > > error." > > > > It turns out this occurs due to the dev_open() call added in the code > > referenced below. The hot remove works as expected if we revert this > > change with the patch shown below. Was the dev_open() added for some > > functional reason I'm not aware of (i.e., are we now breaking some > > other error path by doing this)? For future reference, is there a > > better way to handle the situation where the member device is > > physically gone? Note that we currently have a static set of > devnodes; > > no udev or anything like that. Thanks. > > > Does "-r failed" or "-r detached" not work? That should be the easiest > way to remove failed/detached drives from the array. > Hmm, this sounds like what I'm missing. I'll try it when I have access to the system again. Thanks! Brian -- 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
