1 |
root can create new files! I created a big file with the remaining 17 GB |
2 |
logged in with root. I'll run this tune2fs later, before shutting down the |
3 |
machine. |
4 |
|
5 |
what exactly is this reserved block count? is it about the number of inodes? |
6 |
does that mean that, by default, regular users can only use 95% of the |
7 |
inodes? and why did I use all these inodes? I don't think I have that many |
8 |
small files on this partition... |
9 |
|
10 |
On Sat, May 8, 2010 at 10:48 PM, Nikos Chantziaras <realnc@×××××.de> wrote: |
11 |
|
12 |
> On 05/09/2010 01:46 AM, Crístian Viana wrote: |
13 |
> |
14 |
>> it doesn't seem so :-( |
15 |
>> |
16 |
>> Filesystem Inodes IUsed IFree IUse% Mounted on |
17 |
>> /dev/sda6 20856832 108698 20748134 1% /home |
18 |
>> |
19 |
>> I didn't know that the filesystem could run out of inodes before the |
20 |
>> disk space itself! thanks for the information :-) |
21 |
>> |
22 |
> |
23 |
> Long shot, but check if root can write files. If yes, it probably means |
24 |
> your reserved block count is a bit high (default is 5% I believe). The |
25 |
> reserved block count is a mechanism that disallows further writes to the |
26 |
> filesystem if it gets too full, and only root can keep writing. |
27 |
> |
28 |
> If that's your problem, the reserved block count can be changed with the |
29 |
> tune2fs tool. To set it to, say 2%, you would run: |
30 |
> |
31 |
> tune2fs -m 2 /dev/sda6 |
32 |
> |
33 |
> I don't know if it's safe to do this while the filesystem is mounted. To |
34 |
> play it safe, go to single user mode, umount /home, and only then run the |
35 |
> above command. |
36 |
> |
37 |
> |
38 |
> |