1 |
On Sun, May 09, 2010 at 07:39:01PM -0300, Crístian Viana wrote: |
2 |
> what exactly is this reserved block count? is it about the number of inodes? |
3 |
> does that mean that, by default, regular users can only use 95% of the |
4 |
> inodes? and why did I use all these inodes? I don't think I have that many |
5 |
> small files on this partition... |
6 |
|
7 |
When the filesystem fills up, services can start failing left and |
8 |
right because they cannot write logs, cannot write temp files, etc. At |
9 |
this point human intervention is necessary: root has to log in and |
10 |
clear out the disk. But if the $ROOT filesystem is completely full, |
11 |
one may not even be able to log in and/or that one cannot do any sort |
12 |
of maintenance that is needed. So you have some sort of circularity. |
13 |
(In which case you have to reboot, perhaps using another medium...) |
14 |
|
15 |
The way out is to reserve some breathing room for root so that when |
16 |
everybody else is having problems he can still get in and fix the |
17 |
problem. |
18 |
|
19 |
The 5% is historical from days when disks are much smaller. If you |
20 |
have a sensible partition scheme you only really need to reserve the |
21 |
blocks on the $ROOT filesystem. If the partition in question (IIRC) is |
22 |
only for /home, then you can just turn off the reserved blocks all |
23 |
together. |
24 |
|
25 |
Cheers, |
26 |
|
27 |
W |
28 |
-- |
29 |
Willie W. Wong wwong@××××××××××××××.edu |
30 |
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire |
31 |
et vice versa ~~~ I. Newton |