On 2018-05-18 12:36, Niccolò Belli wrote:
On venerdì 18 maggio 2018 18:20:51 CEST, David Sterba wrote:
Josef started working on that in 2014 and did not finish it. The patches
can be still found in his tree. The problem is in excessive memory
consumption when there are many snapshots that need to be tracked during
the defragmentation, so there are measures to avoid OOM. There's
infrastructure ready for use (shrinkers), there are maybe some problems
but fundamentally is should work.
I'd like to get the snapshot-aware working again too, we'd need to find
a volunteer to resume the work on the patchset.
Yeah I know of Josef's work, but 4 years had passed since then without
any news on this front.
What I would really like to know is why nobody resumed his work: is it
because it's impossible to implement snapshot-aware degram without
excessive ram usage or is it simply because nobody is interested?
I think it's because nobody who is interested has both the time and the
coding skills to tackle it.
Personally though, I think the biggest issue with what was done was not
the memory consumption, but the fact that there was no switch to turn it
on or off. Making defrag unconditionally snapshot aware removes one of
the easiest ways to forcibly unshare data without otherwise altering the
files (which, as stupid as it sounds, is actually really useful for some
storage setups), and also forces the people who have ridiculous numbers
of snapshots to deal with the memory usage or never defrag.
--
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
