unmountable filesystems

[w5000]

anyone knows, what does really mean when some filesystems can't be umounted in any way.

some filesystems from a non-rootvg VG are mounted and can;t be unmounted even if there are only common root's processes in the system, fuser doesn show any process keeping it as well as lsof doesn;t see filesystem locked.

so what a ghost locks them?

how to hadle such weird issues? I met it several times in the past and always had to ignore due to lack of solution (= reboot the system).

Even during reboot, the system reports problem that can't unmount some filesystems....

0513-044 The IBM.DRM Subsystem was requested to stop.
0513-044 The IBM.CSMAgentRM Subsystem was requested to stop.
0513-044 The xntpd Subsystem was requested to stop.
All processes currently running will now be killed...
Unmounting the file systems...
umount: error unmounting /dev/cfklv: Device busy
umount: error unmounting /dev/guklv: Device busy

 

[mrbernsca]

Try running lsof /filesystem name and see what processes have locked it ..

Also, if you find the file system then smit fs and change it not to mount on reboot.

Also, make sure they are enot nfs mounts - hard mounts - if the system is not availiable then it will take forever on reboot ...

 

[blarneyme]

fuser -kucx /filesystem

 

[haexpert]

I would also check with fuser -xuc /filesystem to check what is lock the FS
If you are feeling agreesive use fuser -xuck /filesystem to just kill them.

 

[MoreFeo]

I think fuser with -d option will show open but deleted files.
Maybe this can help.