Operating System - HP-UX
1833268 Members
2768 Online
110051 Solutions
New Discussion

Re: vx_nospace file system full

 
SOLVED
Go to solution
Ronald Cogen
Frequent Advisor

vx_nospace file system full

Hello out there!

First, a description of the configuration and situation:
HP-UX 11.00 on HP9000 L3000, 4GB Mem, internal SCSI disks.

We download zip files. A java routine unzips them, a unix routine sorts them and a java routine appends them.
For some reason we get the following message:
vmunix: vxfs: mesg 001: vx_nospace - /dev/vgapp01/lvol6 file system full (1 block extent).

The result of this is that the whole routine stops what he is doing and then goes on tho the next command, thus leaving the programmed task incomplete.

I don't know where to start analysing this occurance. Can someone give me a tip?

Regards,
Ron
I've been down so long it looks like up to me
9 REPLIES 9
Clemens van Everdingen
Honored Contributor

Re: vx_nospace file system full

Hi,

Your file system got full.
So you should clean that file system.

That's all.

C.
The computer is a great invention, there are as many mistakes as ever, but they are nobody's fault !
federico_3
Honored Contributor

Re: vx_nospace file system full

Shahul
Esteemed Contributor

Re: vx_nospace file system full

Hi

This error comes when ur lvol become full, Means no free space. U can find out by using this command,

#bdf | grep /dev/vgapp01/lvol6

If it is used 100%, U have to free up some space before proceeding to do anything in this filesystem, Or U have to extend the lvol. This is up to U.

Best of luck
Shahul
Nico van Royen
Frequent Advisor

Re: vx_nospace file system full

You filesystem mounted at /dev/vgapp01/lvol6 is full. Check with a bdf wich mountpoint it is, and clean it.

-NvR-
If all else fails, try reading the manual...
T G Manikandan
Honored Contributor

Re: vx_nospace file system full

Just do a bdf to check the size of the file system
Ronald Cogen
Frequent Advisor

Re: vx_nospace file system full

Hello,

I know that the file system got full! the real problem is that some kind of io exception takes place. the result is that the data gets jumbled where some of it appears in the wrong place. Should this happen merely because the file system is full?

Regards,
Ron
I've been down so long it looks like up to me
Darren Prior
Honored Contributor
Solution

Re: vx_nospace file system full

Hi Ron,

That filesystem is full. You can either increase the size of the filesystem, or you'll need to troubleshoot your script to see which stage is causing the problem (most likely the unzipping bit as you probably have the zip file, a temp file and a number of unzipped files.) If you're running all this from a shell script you could add a set -x at the top of the script (below the shell definition), or you could use redirect echo and date statements to a file to help debug it.

You could try changing your routines to use a different filesystem for the unzipping part.

regards,

Darren.
Calm down. It's only ones and zeros...
Chuck J
Valued Contributor

Re: vx_nospace file system full

Like everyone else said, it just means your volume has 100% space capacity. Some tips:

* Increase space on the volume
* Delete files on the volume
* Tar & Gzip anything that is not needed at present but you would like to keep

Chuck J
Chuck J
Valued Contributor

Re: vx_nospace file system full

You could also get the script to do it's "work" on another mountpoint then store the final output on /dev/vgapp01/lvol6 in the location you need.