From: Deb (deb@tickleme.llnl.gov)
Date: Mon Aug 12 2002 - 19:14:04 EDT
Hi Folks,
I've got a Sol 2.7 production system. A vxfs volume had errors when
writing to it during a cron job last night. When I try to umount the
volume, it claims it's busy - I've done fuser, no PID is returned.
I've unexported the volume, and ascertained that the clients cannot
automount it (they get permission denied on an "ls").
As I said, fuser reports nothing; I tried lsof, but I'm having trouble
getting anything meaningful due to my lack of experience with this
command.
I've also restarted nfs and automountd, but to no avail.
What I want to do is umount the volume and "fsck -F vxfs" it. Last
night's errors were correctable, but I want to do some further
checking.
Short of rebooting the Ultra 250 to release the busy state on this
volume, does anyone have any other suggestions? If this was Solaris 2.8,
I'd do the umount -k command - but that's not available with 2.7. :-(
Thanks,
deb
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-
There are 010 types of people in the world:
those that understand binary, and those that don't.
t?t
~
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:45 EDT