4 ms·
snapshots are writable Isn't that an oxymoron? I thought the entire point of a snapshot was that it's an immutable record of the filesystem at a moment in time
by chongli 9y ago
snapshots are writable
Isn't that an oxymoron? I thought the entire point of a snapshot was that it's an immutable record of the filesystem at a moment in time.
extra care to reduce RAM needs, in contrast to ZFS
ZFS utilizes a lot of RAM for caching. That's not the same thing as needing a lot of RAM. I've seen this same complaint about modern operating systems. People will buy a lot of RAM and then get annoyed when they see the OS making use of it. As long as the memory is available to be allocated to applications, why should we care whether or not the operating system makes use of it?
- tedunangst 9y agoIs it better if we call a snapshot a branch point? I believe the complaint about ZFS and RAM is that the caching cannot be considered optional. Performance is substantially worse than other filesystems with more modestly sized caches, so the memory isn't really available to applications.
- chongli 9y agoPerformance is substantially worse than other filesystems with more modestly sized caches, so the memory isn't really available to applications. Is that in comparison to other filesystems that provide the same level of data integrity as ZFS? Otherwise you're comparing apples and oranges.
- tedunangst 9y agoYou didn't say the memory use was justified by providing better integrity. You said it was optional.
- chongli 9y agoYes, the memory use is optional. Pick two: 1) data integrity 2) low memory use 3) performance
- dozzie 9y agoWith ZFS I hear it's "pick one, and you cannot pick `low memory'".
- aidenn0 9y agoYou can run ZFS with megabytes of ram, it's just slow, so it is pick 2. That being said, ZFS metadata is much bigger than it needs to be (most infamously dedupe has this issue).
- chongli 9y agoRight, but to then compare the memory use of ZFS with dedupe turned on against another fs without that feature would be disingenuous since dedupe is optional in ZFS. That was the whole point of my original comment.
- mrighele 9y agodeduplication doesn't have necessarily to be expensive; HAMMER (the first version, not HAMMER2) has offline deduplication that is usually scheduled to run at night. This allows regular use to be quite performant and with a low memory footprint. Of course there are tradeoffs, in particular heavy disk usage at certain hours (which can be an issue depending on the workload) and the fact that space is reclaimed only after some time that it has been wasted.
- aidenn0 9y agoI did say that ZFS metadata in general, and dedupe especially is much bigger than it needs to be. Even live dedupe can be done much more cheaply than how ZFS does it.
- gigatexal 9y agoLol this is FUD. ZFS is easily tunable to not blow up and use all your ram.
- binarycrusader 9y agoThe caching can be considered optional and (in Oracle Solaris) there is a tunable user_reserve_hint_pct: https://docs.oracle.com/cd/E53394_01/html/E54818/chapterzfs-3.html https://docs.oracle.com/cd/E53394_01/html/E54818/chapterzfs-...
- cmurf 9y ago'btrfs subvolume snapshot <src> <dest>' is a writable snapshot; with -r flag it's read only. A Btrfs snapshot is a subvolume with stuff already in it, basically. In fact, all the inode numbers are initially identical in the original subvolume and the snapshot, and initially the snapshot is just a pointer. That's why they're cheap to create.