topic Re: umount in Operating System - HP-UX

umount

hpuxhelp — Thu, 30 Jan 2003 23:50:59 GMT

can you umount the filesystem when the vg is activated??

Re: umount

Rodney Hills — Thu, 30 Jan 2003 23:52:14 GMT

Sure, as long as no processes have any files open on that file system.

HTH

-- Rod Hills

Re: umount

Michael Tully — Fri, 31 Jan 2003 00:08:09 GMT

Make sure that new processes have the filesystem locked.

# umount /fred
umount: cannot unmount /fred : Device busy

# fuser /dev/vg01/fred
1234c
Once the process has been terminated, you can unmount the filesystem

Re: umount

Patrick Wallek — Fri, 31 Jan 2003 00:10:19 GMT

To umount a file system the VG must be activated. If the VG is not activated then the filesystem can't be mounted.

An easier fuser command to user to find who is using a mount point:

# fuser -cu /mountpoint_name

Re: umount

Sridhar Bhaskarla — Fri, 31 Jan 2003 00:15:27 GMT

Patrick ;-)

If vg is in deactivated state, how would file system be in mounted state?

-Sri

PS: One of the tongue slips?

Re: umount

Patrick Wallek — Fri, 31 Jan 2003 00:22:27 GMT

You're right Sridhar. I probably didn't say what I meant to say very clearly.

If a VG is NOT activated, a filesystem CAN NOT be mounted, hence no reason to use umount.

Re: umount

Steven E. Protter — Fri, 31 Jan 2003 02:47:09 GMT

how about a sledgehammer

fuser -cuk /mountpoint

That will kill everything. Don't do it on var.

Sounds like the problem definisiton is confusing people. Details please.

P

Re: umount

Stanimir — Fri, 31 Jan 2003 08:01:48 GMT

Hi!
It seems you want to do something like
fsck with your file system. So you can
do this with umounted fs & activated VG.
Simply do
#umount -F ...
#fsck -p

If you need to manipulate with VG like
vgextend, lvextend, extendfs ... :
#umount -F ...
#vgextend ....
Regards

Re: umount

Jose Mosquera — Fri, 31 Jan 2003 11:44:52 GMT

Hi,

If you are trying with a vg00 basic operating system file system I recommend you set your system in single user mode. If you want do this in others files systems you must ensure that is not busy by your own session or by any SAM session (i.e. listing current VG/LV configuration), etc.

An effective way to free your FS is the following:
#fuser -ku /dev/vg[nn]/lvol[n];umount /

This execute umount command immediately after the fuser command minimizing the possibility that it is busy again.

Rgds.