On Sun, Dec 03, 2017 at 01:45:45AM +0000, Duncan wrote: > Tomasz Pala posted on Sat, 02 Dec 2017 18:18:19 +0100 as excerpted: > >> I got ~500 small files (100-500 kB) updated partially in regular > >> intervals: > >> > >> # du -Lc **/*.rrd | tail -n1 > >> 105M total > > FWIW, I've no idea what rrd files, or rrdcached (from the grandparent post) > are (other than that a quick google suggests that it's... > round-robin-database...
Basically: preallocate a file, its size doesn't change since then. Every a few minutes, write several bytes into the file, slowly advancing. This is indeed the worst possible case for btrfs, and nocow doesn't help the slightest as the database doesn't wrap around before a typical snapshot interval. > Meanwhile, /because/ nocow has these complexities along with others (nocow > automatically turns off data checksumming and compression for the files > too), and the fact that they nullify some of the big reasons people might > choose btrfs in the first place, I actually don't recommend setting > nocow in the first place -- if usage is such than a file needs nocow, > my thinking is that btrfs isn't a particularly good hosting choice for > that file in the first place, a more traditional rewrite-in-place > filesystem is likely to be a better fit. I'd say that the only good use for nocow is "I wish I have placed this file on a non-btrfs, but it'd be too much hassle to repartition". If you snapshot nocow at all, you get the worst of both worlds. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Mozilla's Hippocritic Oath: "Keep trackers off your trail" ⣾⠁⢰⠒⠀⣿⡁ blah blah evading "tracking technology" blah blah ⢿⡄⠘⠷⠚⠋⠀ "https://click.e.mozilla.org/?qs=e7bb0dcf14b1013fca3820..."; ⠈⠳⣄⠀⠀⠀⠀ (same for all links) -- 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
