Atime and btrfs: a bad combination?
Posted Jun 2, 2012 13:03 UTC (Sat) by Ringding (subscriber, #34316)
Posted Jun 7, 2012 16:18 UTC (Thu) by quanstro (guest, #77996)
it would seem to me that this could be fixed
without de-dup by simply making the copy into
the live file system rather than all the snapshots.
that would be O(1) for a block not O(snapshots).
(it must be doing that right, otherwise how would
we generate 10x the original metadata)
one would think that this is a general problem with
btrfs snapshots, and not specific to atime.
Posted Jun 7, 2012 23:23 UTC (Thu) by HenrikH (subscriber, #31152)
Posted Jun 10, 2012 16:52 UTC (Sun) by quanstro (guest, #77996)
it still makes more sense to me to copy into the
working tree rather than the snap. that way all
snaps can continue to share blocks as best they can.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds