topic Re: File System Space... in Operating System - HP-UX

File System Space...

Hazem Mahmoud_3 — Mon, 02 Feb 2004 14:04:47 GMT

I am trying to increase the space of my /home file system. I do the following:
lvextend -L 76 /dev/vg00/lvol4
then I do:
fsadm -F vxfs -b 77824 /home.
It comes back with the following error message:
vxfs fsadm: /dev/vg00/rlvol4 is currently 53248 sectors - size will be increased
vxfs fsadm: attempt to resize /dev/vg00/rlvol4 failed with errno 28
Also, I tried to remove some really large files from the file system. It looks like it removed them but there is still no space left. When I do a bdf I get the following:
/dev/vg00/lvol4 53248 53248 0 100% /home
There is an generous reward for anyone who can help me figure out the problem:)
Thanks!

-Hazem

Re: File System Space...

Steven E. Protter — Mon, 02 Feb 2004 14:09:03 GMT

Most likely there is a open process that is connected to that file you tried to remove. Space will not be freed up until the process dies.

fuser -cu /home

to display the proceses

caution:

fuser -cuk /home

to kill all processes on the /home filesystem.

SEP

Re: File System Space...

Sridhar Bhaskarla — Mon, 02 Feb 2004 14:09:09 GMT

Hi,

You will need to have some free space in the filesystem to use onlineJFS to extend the filesystem online.

"Deleting largefiles" in /home should have freed up enough space for the fsadm to work. Looks like you deleted the files that are still open by the procesess.

So, I would suggest you use lsof to find out the processes that have the these files opened and kill those processes. Or detele the files that are not opened by any of the processes.

Once you get a little space freed, then 'fsadm' should work.

-Sri

Re: File System Space...

Marco Santerre — Mon, 02 Feb 2004 14:11:27 GMT

Looks like you still have a process hanging on to one of the files you probably deleted.

Use lsof to find out which process, and once that process dies, the space will be reallocated again, and you can then pursue with your fsadm command.

The problem with fsadm is it need a little bit of space to work.

Re: File System Space...

Hazem Mahmoud_3 — Mon, 02 Feb 2004 14:22:49 GMT

Ok, I tried that, found two processes, killed them and it is still giving me 100% and the same error message with the fsadm command.

-Hazem

Re: File System Space...

Sridhar Bhaskarla — Mon, 02 Feb 2004 14:26:09 GMT

Hi Hazem,

You will need to use 'lsof' to really get the picture. Search the forums to know from where to get the lsof installed.

lsof /home

will show all the processes and their opened files.

Try deleting|moving some more files to get atleast your fsadm working.

-Sri

Re: File System Space...

Hazem Mahmoud_3 — Mon, 02 Feb 2004 14:28:42 GMT

Well, I was able to delete more file, to free up enough space for fsadm and IT WORKED! Here is my question however, how come I didn't get the space back for the previous big files that I deleted when I was at 100%? Thanks!

-Hazem

Re: File System Space...

Sridhar Bhaskarla — Mon, 02 Feb 2004 14:33:01 GMT

Hi Hazem,

That was because those files were opened by processes. As I said, you will get a good picture if you try 'lsof'. It's a must to have tool on the system along with 'tusc'.

How much free space did you get?. Is it around 75 MB which is you added just now?. If so, then you still have those largefiles opened.

-Sri

Re: File System Space...

Steven E. Protter — Mon, 02 Feb 2004 14:40:10 GMT

http://hpux.connect.org.uk/hppd/hpux/Sysadmin/lsof-4.70/

tusc is availble somewhere at http://software.hp.com or perhpas the ftp site.

Installing lsof generates an error but the product is usable after install. The error is fixed by suid on the lsof binary and reinstalling.

SEP

Re: File System Space...

generic_1 — Fri, 07 May 2004 22:14:54 GMT

When looking for space in home these might be handy.

find -name /home core
*.gz
*.tar

cd /home
du -sk * | sort -nr | head

finds top offending users :).