On Tue, Feb 13, 2018 at 4:46 AM, Qu Wenruo <quwenruo.bt...@gmx.com> wrote:
> On 2018年02月13日 20:06, John Ettedgui wrote:
>>>> That's fairly straightforward to do, though it should be quite slow so
>>>> I'd hope not to have to do that too often.
>>> Then it could be tried on the most frequently updated files then.
>> That's an interesting idea.
>> More than 3/4 of the data is just storage, so that should be very ok.
> BTW, how the initial data is created?
> If the initial data is all written once and doesn't get modified later,
> then the problem may not be fragments.
Mostly at once when I recreated the FS a few years ago, and then
adding on to it slowly.
Though I do try to somewhat balance the free space on all partitions
of similar drives, so it may be a tad further more from its original
>>> And since you don't use snapshot, locate such files and then "chattr +C"
>>> would make them nodatacow, reducing later fragments.
>> I don't understand, why would that reduce later fragments?
> Later overwrite will not create new extent, but overwrite existing extents.
> Other than CoW and cause new extents (fragments)
> Although expand write will still cause new extent, but that's
> unavoidable anyway.
That's why I didn't understand.
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html