Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
cancel
Showing results for 
Search instead for 
Did you mean: 

vxfs: mesg 001: vx_nospace

malki_3
Frequent Advisor

vxfs: mesg 001: vx_nospace

I have a performance problem with a HP_UX machine on 11.O level
when I chacked, I had find just this error on the dmesg
vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
can someone give me an idea with this
Thanks
12 REPLIES
T G Manikandan
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

Your lvol4 filesystem was 100% sometime back.
(any day after the system was brought upi.e.rebooted)

Just clear up some space from the file system.

There is no problem with these messages.
Make sure that the filesystem is having free space

check using

#bdf


Thanks
Rainer von Bongartz
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

Your files system on /dev/vg00/lvol4 is full.

Check where this lvol is mounted to

mount | grep lvol4

and check if you can free up disk space

Regards
rainer
He's a real UNIX Man, sitting in his UNIX LAN making all his UNIX plans for nobody ...
Pete Randall
Outstanding Contributor

Re: vxfs: mesg 001: vx_nospace

Do a bdf -l to find out which filesystem is mounted to lvol4. It's probably either / or /home. Then start looking for big files that are clogging things up. If it's /, the check the /dev directory for things like /dev/rmt/om (instead of 0m) - someone may have run a backup to a wrong device file. Look for core files. Use "du -sk /DIRNAME/* |sort -n" to give you a list of the biggest offenders first.

And do a search on the forums for "file system full". There's hundreds of hints out there.

Pete

Pete
V. V. Ravi Kumar_1
Respected Contributor

Re: vxfs: mesg 001: vx_nospace

hi,
the message is saying file system lvol4 is nearing full. give bdf and grep lvol4
#bdf |grep lvol4

see the last column to identify on which the file system is mounted and delete some of the files if u can.

regds
Never Say No
James R. Ferguson
Acclaimed Contributor

Re: vxfs: mesg 001: vx_nospace

Hi:

This message simply means that at sometime, the filesystem mounted on '/dev/vg00/lvol4' was full. This may or may not represent a current state.

The 'dmesg' buffer is small and circular. That is, it is updated and overwritten by the kernel as necessary.

If you wish, you can timestamp and capture 'dmesg' messages as they occur by creating a crontab entry that runs:

# dmesg - >> /var/adm/messages

...every 10-minutes.

Regards!

...JRF...

Regards!

...JRF...
malki_3
Frequent Advisor

Re: vxfs: mesg 001: vx_nospace

Sorry but I forgot to confirm that /tmp(/dev/vg00/lvol4) is used at 36%
Ravi_8
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

Hi,

/dev/vg00/lvol4(/tmp) is full. You need to remove unwanted files under /tmp or increase size of /tmp.
never give up
V. V. Ravi Kumar_1
Respected Contributor

Re: vxfs: mesg 001: vx_nospace

hi,
since u run dmesg, it reads from its buffer, all are not fresh messages. the message is, some time back the /tmp was full. if it is 36% now u need not worry.

regds
Never Say No
Sajid_1
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

hello,

One nice try will be this:
a) Backup lvol4
b) newfs -F fs_type /dev/vg00/rlvol4
c) Restore data back.

Normally errors on file system makes these type of error message.

Another thing is the patch level. Install the latet patches.
learn unix ..
Darrell Allen
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

You shouldn't worry much about this. Probably someone created a file in /tmp that used all the free space and then deleted the file. Perhaps the process that created the file deleted it once /tmp was full.

If it happens often, you will need to consider increasing the size of /tmp.

Darrell
"What, Me Worry?" - Alfred E. Neuman (Mad Magazine)
Sean OB_1
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

Since lvol4 is /tmp and is now 36% utilized there is nothing to worry about.

Most likely a user or application generated a large temporary file and filled the file system. Once the file was removed the problem went away.

If this happens on a regular basis I would consider increasing the size of /tmp if you can.
Tim D Fulford
Honored Contributor

Re: vxfs: mesg 001: vx_nospace

Pritty much as above except I'm trying to read between the lines here....

1 - Does "bdf" show 34% or did you use "du -sk /tmp"? If the second a file may well be "hogging" the space. This will be cleared if the process hogging the space is killed or dies or at the next reboot (unmount). There are many threads on this subject

2 - You should be able to find out when the message ocured by
# egrep "vx_nospace" /var/adm/syslog/syslog.log | tail

Regards

Tim
-