Thanks to all who responded:
Jeffrey Marans <email@example.com>
stern@sunne.East.Sun.COM (Hal Stern - NE Area Systems Engineer)
firstname.lastname@example.org (Andy Feldt)
email@example.com (Russ Poffenberger)
Mike Raffety <firstname.lastname@example.org>
I didn't get to try any of the suggestions because I ran out of time,
so I'll just summarize the reponses. I will definitely need this
information in the future though, so everything was very helpful.
email@example.com suggested mucking about with the in.statd
directory and file structures ("man sm" for more info on this one).
stern@sunne.East.Sun.COM suggested "umount -f".
firstname.lastname@example.org and email@example.com state that there is no
choice other than to kill any user processes blocking the mount.
firstname.lastname@example.org suggests trying "mount -o remount", given some
constraints as outlined in the man page. email@example.com
thinks that this should work even with blocking user processes.
reuss@Stars.Reston.Unisys.COM suggests a "umount" followed by a "mount
-a"; I know this won't work in my situation, since I've already tried
it. The umount will skip over busy/blocked mounts and let them stay
/ony Yen - firstname.lastname@example.org ... Sail tough
SPARC SysAdmin - UT/Austin - Economics or go home ... Kowabunga! ...
email@example.com (Anthony Yen) writes:
> If I have a "Device busy" message on a filesystem I wish to re-mount
> over NFS, how would I re-mount it short of killing the user processes
> that are blocking the umount? I'll summarize back to the list as
> /ony Yen - firstname.lastname@example.org ... Sail tough
> SPARC SysAdmin - UT/Austin - Economics or go home ... Kowabunga! ...
}-- End of excerpt from Anthony Yen
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:49 CDT