On Tue, Oct 19, 2010 at 06:04:35PM -0500, Stan Hoeppner wrote:
> In an effort to maximize mbox performance and minimize fragmentation I'm
> using these mount options in fstab. This is on a Debian Lenny box but
> with vanilla 126.96.36.199 rolled from kernel.org source (Lenny ships with
> 2.6.26). xfsprogs is 2.9.8.
> I've recently run xfs_fsr thus the low 7% figure. Every couple of weeks
> the fragmentation reaches ~30%. I save a lot of list mail, dozens to
> hundreds per day for each of about 7 foss mailing lists. As I say, in
> just a couple of weeks, these mbox files become fragmented, on the order
> of a dozen to a few dozen extents per mbox file. With so much free
> space available on this filesystem, why aren't/weren't these files being
> spread out with sufficient space between them to prevent fragmentation?
I've explained how allocsize works, and that speculative allocation
gets truncated away whenteh file is closed. Hence is the application
allocsize does not help you because the specualtive prealloc done in
write() is truncated away in close().
What you want is _physical_ preallocation, not speculative
preallocation. i.e. look up XFS_IOC_RESVSP or FIEMAP so your
application does _permanent_ preallocate past EOF. Alteratively, the
filesystem will avoid the truncation on close() is the file has the
APPEND attribute set and the application is writing via O_APPEND...
The filesystem cannot do everything for you. Sometimes the
application has to help....
> (Dave or someone has suggested on list that with newer kernels the
> defaults for these two (and other) mount options do not match those
> suggested in the man pages. I requested a feature some time ago that
> would actually put these default values in /proc files to eliminate any
> doubt as to what the actual defaults being used are. I don't recall if
> anything came of this.
/proc/mounts displays some default options.
> I've seen many an OP get "scolded" on list for
> manually specifying values that were apparently equal to the "default"
> values as stated by the responding dev. This problem would never exist
> if the documentation was complete and consistent.
As I say to _everyone_ who complains about this: Patches
to correct documentation issues are greatly appreciated. You don't
need to be a coding export to send a patch correcting a man page....