- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Booting up hang - vxfs: mesg 001: vx_nospace - /de...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2004 03:14 PM
05-27-2004 03:14 PM
pls help me. I'm running HPUX 11.0.
When using 'sam' in console, something wrong with the keyboard, that force me to kill some 'sam' processes via telnet, than run 'shutdown -r -y 0'.
In the process of shutting down, this message appeared:
____________________________________
Stop RPC daemon ........................................... OK
Stop DCE daemons ..........................................
vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
OK
Stopping OSPF MIB Network Management subAgent ............. N/A
____________________________________
Then, we it starting up showed failure in below steps:
____________________________________
...
Configuer LAN interface...... [FAIL] *
Start name server daemon..... [N/A]
Start NFS core subsytem ..... [busy/wait]
____________________________________
The process keep hanging in that status until now.
My friend told me to use ISL to clean the full space, I don't know steps to do that.
- What should I do to get into ISL ?
- What command to freeze space in /dev/vg00/lvol4 ?
Very much appreciate to your helps....
Regards,
Jayy.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2004 03:21 PM
05-27-2004 03:21 PM
SolutionYOu have your /tmp filesystem full.
Boot into single user mode and delete the files which you may not require.
***) boot the server
***) interrupt the boot sequence, when prompted to within 10 seconds
***) type in boot pri at main menu
***) It asks whether you want to interact with ISL...type Y
***) comes to ISL prompt...and type hpux -is
you are booted into single user mode.
mount /tmp
cd /tmp
and you can remove the files
then type init 3 to boot into multi user mode
with best wishes
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2004 03:57 PM
05-27-2004 03:57 PM
Re: Booting up hang - vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full
I've run into single user mode.
When mounting /tmp, this message appears:
vxfs mount: /dev/vg00/lvol4 is corrupted. needs checking.
when seeing into /tmp, found hundreds of file like sh???.1 sh???.2 etc...
'cat'-ing on of file showing:
_________________________________________
Subject: HOSTNAME modified during active DHCP lease....bla..bla..bla..
can view config in : /usr/lbin/dhcpdb2conf
_________________________________________
looking into /usr there is no file nor directory under it. ls => total 0
run "init 3", still resulted same failure:
____________________________________
....
vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
...
Configuer LAN interface...... [FAIL] *
Start name server daemon..... [N/A]
Start NFS core subsytem ..... [busy/wait]
____________________________________
Pls further help.... thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2004 04:03 PM
05-27-2004 04:03 PM
Re: Booting up hang - vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full
boot in the single user mode
do an fsck on /dev/vg01/lvol4
before mounting
mount the /tmp.
delete those files
you are not able to see anything in /usr becuase your /usr is not mounted.
mount /usr
and you will be able to see the contents of /usr
with best wishes
naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2004 05:11 PM
05-27-2004 05:11 PM
Re: Booting up hang - vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full
From tyhe console press Control+B and then go to GSP mode enter login and password(for my case login and password are nothing so we entered it).
From the GSP mode press TC command(RS command also will reset and reboot the system but to check what went wrong it is better user TC so that log willbe there)
Then it will reboot and follow Naveen's procedure to make it single user mode.
Now fsck /dev/vg00/lvol4
Now, mount the /tmp.
Now,mount /usr
Delete files which is causing problem and then reboot the system.
That's all.
Rgds
Tapas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2004 07:17 PM
05-27-2004 07:17 PM
Re: Booting up hang - vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full
Thank so much for your help.
It works now !!
Rgds,
Jayy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2004 01:06 AM
11-01-2004 01:06 AM