| 1 |
On 05/13/2010 01:56 AM, Willie Wong wrote: |
| 2 |
> On Thu, May 13, 2010 at 12:25:08AM +0200, Alex Schuster wrote: |
| 3 |
>>> The 5% is historical from days when disks are much smaller. If you |
| 4 |
>>> have a sensible partition scheme you only really need to reserve the |
| 5 |
>>> blocks on the $ROOT filesystem. If the partition in question (IIRC) is |
| 6 |
>>> only for /home, then you can just turn off the reserved blocks all |
| 7 |
>>> together. |
| 8 |
>> |
| 9 |
>> Isn't another purpose of those 5% the reduction of fragmentation that |
| 10 |
>> occurs more when there is few free space left? Although I also reduce ift |
| 11 |
>> on very large partitions. But I never set it to exactly zero. |
| 12 |
> |
| 13 |
> Perhaps? I don't know. My ext3 partitions with 0% are all for large |
| 14 |
> files (videos and music) that are more or less static, so I can't say |
| 15 |
> anything about fragmentation on them. My other partitions are all |
| 16 |
> reiser, so can't say anything about fragmentation on them either :) |
| 17 |
|
| 18 |
The tune2fs man page mentions that fragmentation is also a reason: |
| 19 |
|
| 20 |
-m reserved-blocks-percentage |
| 21 |
Set the percentage of the filesystem which may only be allocated |
| 22 |
by privileged processes. Reserving some number of filesystem |
| 23 |
blocks for use by privileged processes is done to avoid |
| 24 |
filesystem fragmentation, and to allow system daemons, such as |
| 25 |
syslogd(8), to continue to function correctly after non- |
| 26 |
privileged processes are prevented from writing to the |
| 27 |
filesystem. Normally, the default percentage of reserved blocks |
| 28 |
is 5%. |
Archives