1 |
On Sunday 09 May 2010 01:39:54 Crístian Viana wrote: |
2 |
> I shutdown this computer everyday, those temp files shouldn't be alive for |
3 |
> months. |
4 |
> |
5 |
> I ran lsof | grep deleted and it returned 132 lines, the biggest number |
6 |
> being 2032226 (2 MB?), belonging to the Chromium browser process. even if |
7 |
> every line had that value (which is not), that would sum up 264 MB, but the |
8 |
> difference of reported/real free space is way bigger than that. |
9 |
> |
10 |
> changing the filesystem back to ext3 can solve this problem? it was ext3 |
11 |
> before I've changed it to ext4 some months ago. |
12 |
|
13 |
I'm fresh out of ideas on this one. |
14 |
|
15 |
As I understand it, downgrading from ext4 to ext3 normally doesn't work out. |
16 |
There are features in ext4 that make it very attractive and most folk enable |
17 |
them, but they are incompatible with ext3. Or so I have read. |
18 |
|
19 |
I would boot into a rescue system and run an fsck on that volume if you have |
20 |
not already done so. |
21 |
|
22 |
|
23 |
|
24 |
|
25 |
|
26 |
> |
27 |
> On Sat, May 8, 2010 at 8:00 PM, Alan McKinnon |
28 |
<alan.mckinnon@×××××.com>wrote: |
29 |
> > You probably have files opened that have since been deleted. du doesn't |
30 |
> > report |
31 |
> > them as the names are no longer in the directory and df doesn't report |
32 |
> > them as |
33 |
> > they are pending deletion once the last handle to them is closed. |
34 |
> > |
35 |
> > It's a nasty thing to find. Run this: |
36 |
> > |
37 |
> > lsof | grep deleted |
38 |
> > |
39 |
> > You should find a ton of junk temp files (they will go away when you log |
40 |
> > out). |
41 |
> > Look for big numbers in column 8 |
42 |
> > |
43 |
> > On Sunday 09 May 2010 00:46:28 Crístian Viana wrote: |
44 |
> > > it doesn't seem so :-( |
45 |
> > > |
46 |
> > > Filesystem Inodes IUsed IFree IUse% Mounted on |
47 |
> > > /dev/sda6 20856832 108698 20748134 1% /home |
48 |
> > > |
49 |
> > > I didn't know that the filesystem could run out of inodes before the |
50 |
> > > disk space itself! thanks for the information :-) |
51 |
> > > |
52 |
> > > On Sat, May 8, 2010 at 4:07 PM, Nikos Chantziaras <realnc@×××××.de> |
53 |
> > |
54 |
> > wrote: |
55 |
> > > > On 05/08/2010 09:21 PM, Crístian Viana wrote: |
56 |
> > > >> hi everyone, |
57 |
> > > >> |
58 |
> > > >> something weird is happening on my system. I can't create new files, |
59 |
> > |
60 |
> > it |
61 |
> > |
62 |
> > > >> says "No space left on device", but the disk has several gigabytes |
63 |
> > > >> of free space! |
64 |
> > > > |
65 |
> > > > The filesystem probably ran out of inodes. "df -i /home" will show |
66 |
> > |
67 |
> > inode |
68 |
> > |
69 |
> > > > usage. This can happen when you have many small files; they eat |
70 |
> > > > inodes but not storage space. |
71 |
> > |
72 |
> > -- |
73 |
> > alan dot mckinnon at gmail dot com |
74 |
|
75 |
-- |
76 |
alan dot mckinnon at gmail dot com |