On Tue, 2004-11-30 at 13:05 +1100, Neil Brown wrote:
> On Sunday November 28, robin-lists@xxxxxxxxxxxxxx wrote:
> > Guy wrote:
> > > I use mdadm's monitor mode to send me email when events occur.
> >
> > Guy,
> >
> > I've been meaning to write this for a while...
> >
> > I tried monitoring once but had a problem when shutting down as the
> > arrays were reported as "busy" because mdadm --monitor was running on
> > them. I guess it needs to be killed earlier in the shutdown process.
>
> That bug was fixed in mdadm 1.6.0
>
> NeilBrown
>
>
> From the ChangeLog:
> Changes Prior to 1.6.0 release
> ...
> - Fix bug in --monitor where an array could be held open and so
> could not be stopped without killing mdadm.
> ...
If I recall correctly, this fixes the primary symptom, but not the whole
problem. When in --monitor mode, mdadm will reopen each device every 15
seconds to scan its status. As such, a shutdown could still fail if
mdadm is still running and the timing is right. In that instance,
retrying the shutdown on failure would likely be enough to solve the
problem, but that sounds icky to me. Would be much better if mdadm
could open a control device of some sort and query about running arrays
instead of opening the arrays themselves.
--
Doug Ledford <dledford@xxxxxxxxxx>
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
-
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
