Inodes not being released !! 4

[joedyq]

We have a situation where the filesystem is showing as full, in actuality its not !! Inodes have not been released post large file deletion . Is there anyway to gwt this space back without rebooting the server . I have tried resizing the filesystem in the hope that the action might do the job !!

J

 

[gileb]

Hello,

looks like you have deleted a file being used by a process which is still running... If you are in 433 you can use fuser -dV /dev/lvname to find this process. And you will have to stop that process to release spacetaken. It is a normal unix behavior => never delete a file opened by a process, just copy /dev/null in yourr file.

 

[Required]

If you deleted all the links to a file and it is still in use and growing, then "lsof" is the perfect tool. It will allow you to find the file and the process using it.
This tool is free, excellent, and you can download it from ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/lsof.tar.gz and ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/lsof.tar.Z

 

[joedyq]

I want to thank you all for the help you have posted here !! The solution is as we have found to umount the filesystem and fsck , umount and just mount did not work . It is the strangest I have seen. For more info we extended the filesystem by 500mb and it filled that more or less immediately, then added a further 500mb and again filled that immediately. In truth , the extra allocated space was not utilised , just appeared to be . Again thank you all !!

 

[MoshiachNow]

as i thought ...

It actualy was repotten to me this week from one of the customers. "Long live king Moshiach !"

 

[joedyq]

Good Morning guys ,

The posting from gileb re: using fuser -dV works a treat , the same problem has just raised its ugly head once again and I found the problem processes with this command. Basically it notes the inode number the process id and the size of the problem file. The main application using this system has some basic problems that need to be adressed !!
Great stuff gileb.

 

[conniefu]

I have same experience too. This trick always works for me. Find out which process is opening that big file. Then kill that process, the inode will be released. and "df -k" will show the correct output.


cheers,

connie