1833192 Members
2878 Online
110051 Solutions
New Discussion

file system full

 
SOLVED
Go to solution
???_185
Regular Advisor

file system full

Strangily, Idon't understand why does lvol have sufficient space looks like full?
/dev/vg01/lvol2 8929280 7051484 1761050 80% /var/opt/OV


Dec 6 23:04:02 imis_sms vmunix: msgcnt 254569 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (8 block extent)
Dec 6 23:04:08 imis_sms vmunix: msgcnt 254571 vxfs: mesg 001: vx_nospace - /dev/vg01/lvol2 file system full (8 block extent)
6 REPLIES 6
A. Clay Stephenson
Acclaimed Contributor
Solution

Re: file system full

Generally this happens when a process creates temporary files, unlinks them, and when this process dies the files close and the space is freed. When you ran the df command all was well; if you had run df just before the errors were logged the filesystem would have been almost full.
If it ain't broke, I can fix that.
Sivakumar TS
Honored Contributor

Re: file system full

Dear Zungwon,

As Clay said, every process reserves/locks some space in disk while it is running. This will be freed up once the process dies and the reserved space may not be shown in bdf also.Thats the reason you bdf shows free space and still you get the nospace error.

With Regards,

Siva
Nothing is Impossible !
Yogeeraj_1
Honored Contributor

Re: file system full

hi,

it might also be time to purge your old log files from /var.

kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Geoff Wild
Honored Contributor

Re: file system full

Also - if you deleted files that were open - well - that space won't be reclaimed until the process goes away...

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
leaon_1
New Member

Re: file system full

BDF is current capacity.
Cem Tugrul
Esteemed Contributor

Re: file system full

"bdf" and "du -s" display different size: space process bound DocId: TBRIXKBRC00001367 Updated: 4/16/04 11:20:00 AM

PROBLEM
The filesystem has filled up, so action was taken to delete 800MB of logfiles.

The command:
"du -s"

shows the space as 'freed' but "bdf" doesn't. How can that be?


CONFIGURATION
hpux 10.x 10.20 11.x s700
s800
RESOLUTION

Obviously there is a difference in how du and bdf behave.
This may occur if we touch open files.

"du" shows output in a positive view: it shows the number of currently allocated
blocks and counts the blocks you've just deleted as free.
"bdf" has a more negative perspective: it shows the free disk space available.

The difference is here: if a still-active process has allocated blocks (such as
for a logfile that you've just deleted), "bdf" counts these as still occupied.
This won't change until the process closes the file ("deallocates the blocks")
as it usually happens when the process terminates.





ALT KEYWORDS
fs vxfs jfs hfs space display difference delete remove free
up

Good Luck,
Our greatest duty in this life is to help others. And please, if you can't