On Sat, Dec 02, 2017 at 17:28:12 +0100, Tomasz Pala wrote: >> Suppose you start with a 100 MiB file (I'm adjusting the sizes down from > [...] >> Now make various small changes to the file, say under 16 KiB each. These >> will each be COWed elsewhere as one might expect. by default 16 KiB at >> a time I believe (might be 4 KiB, as it was back when the default leaf > > I got ~500 small files (100-500 kB) updated partially in regular > intervals: > > # du -Lc **/*.rrd | tail -n1 > 105M total > >> But here's the kicker. Even without a snapshot locking that original 100 >> MiB extent in place, if even one of the original 16 KiB blocks isn't >> rewritten, that entire 100 MiB extent will remain locked in place, as the >> original 16 KiB blocks that have been changed and thus COWed elsewhere >> aren't freed one at a time, the full 100 MiB extent only gets freed, all >> at once, once no references to it remain, which means once that last >> block of the extent gets rewritten.
OTOH - should this happen with nodatacow files? As I mentioned before, these files are chattred +C (however this was not their initial state due to https://bugzilla.kernel.org/show_bug.cgi?id=189671 ). Am I wrong thinking, that in such case they should occupy twice their size maximum? Or maybe there is some tool that could show me the real space wasted by file, including extents count etc? -- Tomasz Pala <go...@pld-linux.org> -- 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
