topic Re: vxfs:msg001:vx_nospace /dev/root in Operating System - HP-UX

vxfs:msg001:vx_nospace /dev/root

Peter Kovacs 1.0rc — Tue, 05 Feb 2008 14:56:53 GMT

Hi,

I am getting the error message in the Subject.

df -k gives

/ (/dev/vg00/lvol3 ) : 606208 total allocated Kb
0 free allocated Kb
606208 used allocated Kb
100 % allocation used

for the root device.

Executing
du -x / | sort -n |less
gives me:
...
10320 /etc/opt/mx
10320 /etc/opt/mx/config
20592 /etc/vx/type/fsgen
22608 /etc/vx/static.d/build
24128 /etc/vx/static.d
25472 /etc/opt/resmon/lbin
32448 /etc/vx/type/raid5
34768 /sbin/fs/vxfs
36528 /etc/opt/resmon
43440 /etc/vx/type/gen
56288 /sbin/fs/vxfs4.1
62976 /etc/opt
69008 /etc/vx/type/static
103920 /sbin/fs
165504 /etc/vx/type
192208 /etc/vx
267824 /etc
315840 /sbin
1176000 /

I am not quite sure if the maths here are OK, but...can anyone suggest me what could I delete from the root filesystem, so I can get some more space?

Thanks
Peter

PS:
I was trying to use "Forum advanced search" of this site, but based on the first minute of waiting, it was going to take ages for the search page to load.

Re: vxfs:msg001:vx_nospace /dev/root

TwoProc — Tue, 05 Feb 2008 15:20:37 GMT

Peter,

You can move (NOT DELETE) the stuff in /etc/opt and /etc/lp. You can move these to be theor own mount points safely. HOWEVER, that may depend on what software you've got running on boot up. So, you need to test this out on a test server that is running all of the services of the production server first.

Re: vxfs:msg001:vx_nospace /dev/root

Peter Kovacs 1.0rc — Tue, 05 Feb 2008 15:32:50 GMT

Thanks!

My plan was:

1. mv /etc/opt /opt/etc/
2. ln -s /opt/etc/opt /etc/opt

For the first steop, I got this:

bash-3.00# mv /etc/opt /opt/etc/
rm: emsagent not removed. Text file busy
rm: p_client not removed. Text file busy
rm: registrar not removed. Text file busy
rm: directory lbin not removed. Directory not empty
rm: librescli.so.1 not removed. Text file busy
rm: libresmon.so.1 not removed. Text file busy
rm: directory hpux32 not removed. Directory not empty
rm: librescli.so.1 not removed. Text file busy
rm: libresmon.so.1 not removed. Text file busy
rm: directory hpux64 not removed. Directory not empty
rm: directory lib not removed. Directory not empty
rm: directory resmon not removed. Directory not empty
rm: directory /etc/opt not removed. Directory not empty
mv: /etc/opt: Cannot unlink.

Did I mess up the system for good?

Thanks
Peter

Re: vxfs:msg001:vx_nospace /dev/root

MarkSyder — Tue, 05 Feb 2008 15:34:11 GMT

What? Someone complaining about the forum search facility? Surely not!

I notice /dev isn't listed in your output, but it's worth looking for an ordinary file in there. What typically happens is someone mistypes a tape device name and creates a large text file in /dev.

Apart from that, check if any applications are writing to / that should be writing to their own dedicated filesystem.

Mark Syder (like the drink but spelt different)

Re: vxfs:msg001:vx_nospace /dev/root

Robert-Jan Goossens_1 — Tue, 05 Feb 2008 15:49:44 GMT

could you post or attach the complete output of

# du -ksx / | sort -n

Re: vxfs:msg001:vx_nospace /dev/root

Peter Kovacs 1.0rc — Tue, 05 Feb 2008 15:52:55 GMT

bash-3.00# du -ksx / | sort -n > /opt/du.log
bash-3.00# less /opt/du.log
586760 /
bash-3.00#

Thanks
Peter

Re: vxfs:msg001:vx_nospace /dev/root

TwoProc — Tue, 05 Feb 2008 15:53:32 GMT

Peter,

You've got to have some available disk space handy, and you've got to create some lvols on them, then format them, add them to /etc/fstab... etc.

Did you make mount points from disk already?

The problem is - this process needs to be done to survive a reboot, and then, on reboot it has to come back up - and yes, it requires a reboot, or at least, single user mode.

1: Make two lvols, format them with a file system, and mount them. I'm going to assume that you already know how to do this, if not, that's another question to ask the forum.

2: Mount the newly created lvols at a temporary location - say /tempopt and /templp
3: copy the files (not move).
$> cd /etc/opt
$> find . | cpio -pdmvu /tempopt
$> cd /etc/lp
$> find . | cpio -pdmvu /templp

3: Fix the /etc/fstab to mount the two lvols that you created at /etc/opt and /etc/lp using vi. You'll need to add two lines in this file, one for each mount point. Once again, I'm presuming you know how to do this.

4: Get all users off and applications (databases, web servers, application servers, java servlets, etc.) shut down

5: Go to single user mode
$> init s

6: remove all files in /etc/opt and /etc/lp
$> rm -rf /etc/opt
$> rm -rf /etc/lp

7; remake the directories that you just deleted so that you can mount back up
$> mkdir /etc/opt /etc/lp

8; reboot your server, or at least go back to init level 3 ( or whatever your default init level is). It is easiest to reboot
$> shutdown -r now

Above all, make sure and do this on a TEST server first to make sure that you know how to correctly and easily do this.

Re: vxfs:msg001:vx_nospace /dev/root

Peter Kovacs 1.0rc — Tue, 05 Feb 2008 16:44:25 GMT

I simply forgot to make a listing of / itself. There was a 300MB log file in there. Removing the log file solved the problem.

(I copied back the /etc/opt directory to its initial location. I got a few "file busy" error messages in the process. I am crossing my fingers and hope that those files were so busy when I was trying to move them away that "mv" didn't touch them either at that time.)

Thanks
Peter

Re: vxfs:msg001:vx_nospace /dev/root

Peter Kovacs 1.0rc — Tue, 05 Feb 2008 16:51:37 GMT

Delete large log file.