Peter Ross <petrosssit@gmail.com> writes:

> BTW: I am reducing it to 2% since.. long long time. I haven't seen an issue
> arising from this at all.

Hm, for the purposes of avoiding fragmentation,
I suppose the reserve amount needs to be proportional to
<bytes written per interval> rather than the disk size.

I assume the disk size has grown faster that write speed,
and the 5% default was conservative even when it was introduced.

So your result makes intuitive sense to me.

OOC, Peter, what fragmentation does e2fsck -f report for your
filesystems?  With repeated filling as root or with 0% reserve, I've
seen it go up to 20% or 30% (IIRC).

NB: you can edit mke2fs to make new (ext) fs's default to 2%.

_______________________________________________
luv-main mailing list
luv-main@luv.asn.au
http://lists.luv.asn.au/listinfo/luv-main