Peter Grandi wrote:
>>> XFS resists fragmentation better than most other filesystems,
>>> so defragmentation, while possible, is generally not needed.
> That's a common myth. For most file systems and filesystems.
> Also most applications write files really badly.
Do you have any evidence to back this up? The article you quote says
about xfs allocation -- it's talking about Windows systems using FAT or NTFS --
you've ported XFS to Windows? If not, I'm I don't see how your comments are
> Fortunately 'xfs_fsr' is mostly reliable, but in-place
> defragmentation is a risky propostion for several reasons even
> if 'xfs_fsr' is fairly reliable.
How is it risky? Do you have any evidence to back up this claim?
It copies from where it is at, to a pre-reserved, vacant space (which it finds
before it does the copy). When the copy is done successfully, its points the
at the defragmented data, and frees the old copy -- or at least that's my
'not having looked at the code' understanding of it.
This is basically a file copy. So you are saying that file
in place using file copy is risky? Doesn't this imply you are saying
that copying files is risky? How is this meaninful?
> Note also that 'xfs_fsr' uses a terrible "defragmentation"
> strategy (from 'man xfs_fsr'):
> "The reorganization algorithm operates on one file at a time,"
xfs_fsr does a superb job of file defragmenting. It doesn't
do disk defragmenting. But it does defragment single files well, which was
all it was designed to do. We can lament that it hasn't been improved on,
but no one with money or with 'free time' (ha) and the knowledge, has seen it
a problem, so it hasn't been fixed.
> That also should not be the case unless your applications write
> strategy is wrong and you get extremely interleaved streams, in
> which case you get what you paid for the application programmer.
That's a rather naive view. It may not be one application but several
writing to the disk at once. Or it could be one, but recording multiple streams
to disk at the same time -- of course it would have to write them to disk as
come in, as memory is limited -- how else would you prevent interleaving in such
a case? There are too many situations where fragmenting can occur to toss them
all off and say they are the result of not paying an application programmer to
I don't see why you posted -- it wasn't to help anyone nor to offer constructive
criticism. It was a bit harsh on the criticism side, as though something about
was 'personal' for you.... Also sensed a tinge of bitterness in that last bit
criticism about the video stream fragmentation. I'm sorry for your loss, but
try to understand, that this is a forum/list for developers/users to help with
Please rethink your approach here, and I'm apologize in advance if I'm out of
line, but something seemed off-key in this post, but maybe I'm misreading things
completetely... its happened before. :-)