1833078 Members
2643 Online
110050 Solutions
New Discussion

Re: LV full

 
YOGI_3
Frequent Advisor

LV full

Hi All,
We were getting error on console that /appl file system is full..please refer below error
-------------------------------------------
Jul 6 12:35:15 mbpscw01 syslog: Pid 28626. Failed to write to Info Log file . Err=
--------------------------------------------
we removed some unwanted file from this LV.
And when we check
# du -k /appl
289128 /appl
while
# bdf | grep /appl
/dev/vgapp01/appl 4612096 4612096 0 100% /appl
###it should show 289128MB allocated..
how its showing 100% full in bdf o/p bou in du -k its showing 289mb allocated.....

Waiting for replay.....
yog
There is never a wrong time to do the right things
4 REPLIES 4
Paul_481
Respected Contributor

Re: LV full


Hi Yogi,

Although the "du" command shows that the space is already free, some process still has lock over the blocks.

Use "lsof" to determine the process and kill it.


Regards,
Paul
Giacomo TOTTI
Advisor

Re: LV full

Hi,
try to reboot your system, sometime LVM doesn't know that you had canecelled a file, especially when the file system is on 100%.
If you cannot reboot, try the fsync and sync commands (they are not dangerous),

regards

Giacomo
Sudeesh
Respected Contributor

Re: LV full

This can happen if there is too many open files of big size. Use fuser -cu to find out the pid of application accessing this file system, then use glance to identify if there is any open files related to these PID.

glance -> Select Process (give PID) -> Open Files.

Hope this helps

Sudeesh
The most predictable thing in life is its unpredictability
Joseph Loo
Honored Contributor

Re: LV full

hi yogi,

u may like to refer to this doc which explains the reason why:

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000076907951

regards.
what you do not see does not mean you should not believe