| 1 |
You probably have files opened that have since been deleted. du doesn't report |
| 2 |
them as the names are no longer in the directory and df doesn't report them as |
| 3 |
they are pending deletion once the last handle to them is closed. |
| 4 |
|
| 5 |
It's a nasty thing to find. Run this: |
| 6 |
|
| 7 |
lsof | grep deleted |
| 8 |
|
| 9 |
You should find a ton of junk temp files (they will go away when you log out). |
| 10 |
Look for big numbers in column 8 |
| 11 |
|
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
On Sunday 09 May 2010 00:46:28 Crístian Viana wrote: |
| 16 |
> it doesn't seem so :-( |
| 17 |
> |
| 18 |
> Filesystem Inodes IUsed IFree IUse% Mounted on |
| 19 |
> /dev/sda6 20856832 108698 20748134 1% /home |
| 20 |
> |
| 21 |
> I didn't know that the filesystem could run out of inodes before the disk |
| 22 |
> space itself! thanks for the information :-) |
| 23 |
> |
| 24 |
> On Sat, May 8, 2010 at 4:07 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
| 25 |
> > On 05/08/2010 09:21 PM, Crístian Viana wrote: |
| 26 |
> >> hi everyone, |
| 27 |
> >> |
| 28 |
> >> something weird is happening on my system. I can't create new files, it |
| 29 |
> >> says "No space left on device", but the disk has several gigabytes of |
| 30 |
> >> free space! |
| 31 |
> > |
| 32 |
> > The filesystem probably ran out of inodes. "df -i /home" will show inode |
| 33 |
> > usage. This can happen when you have many small files; they eat inodes |
| 34 |
> > but not storage space. |
| 35 |
|
| 36 |
-- |
| 37 |
alan dot mckinnon at gmail dot com |
Archives