> > fails with a device busy error. Every time it has happened, a simple > > umount > > command without the -l switch fails, but a "lazy" umount appears to > work, > > with the exception that sometimes I still cannot stop the array. > Clearly, > > the NFS export is sometimes the culprit, but not always. What else can > it > > be? > > It's best not to use --lazy if yo really want to stop the array. > It makes it harder to find the problem. Well, OK. I always try an ordinary umount first, but when it fails, sometimes a lazy umount works. > You seem to have covered everything that I can think of that would > keep a filesystem active... > > > > > The second item is assembling an array which was formerly stopped. > > By my reading, `mdadm --assemble --scan` should work, but it doesn't. > It > > keeps telling me no devices are found for the array. Here is a sample > > from > > one of the /etc/mdadm/mdadm.conf files: > > > > Try adding --verbose to the "mdadm --assemble" line. If that doesn't > give you any hints, post the output and it might give me some hints. OK, thanks. The next time it happens, I will. -- 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
