On 02/10/2018 05:05 PM, Tomasz Pala wrote:
You won't have anything close to "accurate" in btrfs - quotas don't
include space wasted by fragmentation, which happens to allocate from tens
to thousands times (sic!) more space than the files itself.
Not in some worst-case scenarios, but in real life situations...
I got 10 MB db-file which was eating 10 GB of space after a week of
regular updates - withOUT snapshotting it. All described here.
The underlying filesystem this is replacing was an in-house developed
COW filesystem, so we're aware of the difficulties of fragmentation.
I'm more interested in an approximate space consumed across snapshots
when considering CoW. I realize it will be approximate. Approximate is
ok for us -- no accounting for snapshot space consumed is not.
Also, I don't see the thread you mentioned. Perhaps you forgot to
mention it, or an html link didn't come through properly?
course) or how many subvolumes/snapshots there are. If I know that
above N snapshots per subvolume performance tanks by M%, I can apply
limits on the use-case in the field, but I am not aware of those kinds
of performance implications yet.
This doesn't work like this. It all depends on data that are subject of
snapshots, especially how they are updated. How exactly, including write
I think you expect answers that can't be formulated - with fs architecture so
advanced as ZFS or btrfs it's behavior can't be analyzed for simple
answers like 'keep less than N snapshots'.
I was using an extremely simple heuristic to drive at what I was looking
to get out of this. I should have been more explicit that the example
was not to be taken literally.
This is an exception of easy-answer: btrfs doesn't handle databases with
CoW. Period. Doesn't matter if snapshotted or not, ANY database files
(systemd-journal, PostgreSQL, sqlite, db) are not handled at all. They
slow down entire system to the speed of cheap SD card.
I will keep this in mind, thank you. We do have a higher level above
BTRFS that stages data. I will consider implementing an algorithm to
add the nocow flag to the file if it has been written to sufficiently to
indicate it will be a bad fit for the BTRFS COW algorithm.
Actually, if you do not use compression and don't need checksums of data
blocks, you may want to mount all the btrfs with nocow by default.
This way the quotas would be more accurate (no fragmentation _between_
snapshots) and you'll have some decent performance with snapshots.
If that is all you care.
CoW is still valuable for us as we're shooting to support on the order
of hundreds of snapshots per subvolume, and without it (if BTRFS COW
works the same as our old COW FS) that's going to be quite expensive to
keep snapshots around. So some hybrid solution is required here.
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