Operating System - HP-UX
1834007 Members
1636 Online
110063 Solutions
New Discussion

Re: vx_nospace - /dev/root file system full (1 block extent)

 
SOLVED
Go to solution
VMG
New Member

vx_nospace - /dev/root file system full (1 block extent)

Hi everybody!

As you can see, we have some problems with a server...
There's no way of login from the console, neither the lan console neither remotely with the command remsh {server} /usr/bin/ksh -i that was recomended in another message.
Any idea will be really wellcomed!!!


5 REPLIES 5
Sridhar Bhaskarla
Honored Contributor
Solution

Re: vx_nospace - /dev/root file system full (1 block extent)

Hi,

I don't think you can use any of the tools to get in unless you already have a window opened.

You will need to reboot the server to single-user mode and fix the problem. YOu will have to hardreset the box either through GSP/Console and do a 'rs' or turn the ker off/on or turn off/on the power switch depending on your system.

Interact with isl at the bootadmin. Get into single user mode

isl> hpux -is

Once you are in single user mode mount /usr, /var and /tmp

#mount /usr
#mount /var
#mount /tmp

#du -xk |sort -n|tail

Look at the directories|files that are culprits. It may be that one of your device files (like /dev/rmt/0m) might have become a regular file or there is a big coredump by one of the processes.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Mic V.
Esteemed Contributor

Re: vx_nospace - /dev/root file system full (1 block extent)

Once you're back up, it would be useful to understand how it happened in the first place, then prevent it in the future (or you'll be doing this again).

In addition to previous comments, you can also look for log files or mistakes made by someone with root privs (accidentally copying a file to the wrong place).

Mic
What kind of a name is 'Wolverine'?
Jeff Schussele
Honored Contributor

Re: vx_nospace - /dev/root file system full (1 block extent)

Hi,

mic is right on.
You need to determine just *what* filled /
Usually it's someone mistyping /dev/rmt/0mn or /dev/dsk/cXtYdZ or such & then this becomes a user education issue. Ain't life as a SA grand?

My $0.02,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Tony Horton
Frequent Advisor

Re: vx_nospace - /dev/root file system full (1 block extent)

While I realise this should now have been solved, one thing that may have worked would be to try to ftp to the box and delete the offending file.

I can remember using ftp in the past to get out of a sticky situation where I couldn't login on the console, or from telnet (Can't remember exactly what the problem was though)...

Tony.
No man is an isthmus
Steven E. Protter
Exalted Contributor

Re: vx_nospace - /dev/root file system full (1 block extent)

Handy root fs check script

du -kx / | sort -rn

Helps you hunt down those files.

Any file copied into a filder like /var while unmounted becomes hidden after mount. This space is used on the root filesystem.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com