Hi,
thank you all for your helpful comments.
From what I've read, I forged the following guidelines (for myself;
ymmv):
- Use btrfs for generic data storage on spinning disks and for
everything on ssds.
- Use zfs for spinning disks that may be used for cow-unfriendly
workloads, like vm images (if they are too big and/or too fast-changing
for a scheduled defrag to make sense).
For now I'm going with the following setup: a Debian system with root on
btrfs/raid1 on two ssds, and a raidz1 pool for storage and vm images.
However, those few vms that really should be fast would also fit on the
SSDs, so I might move them there and switch from ZFS to btrfs on the
storage pool at some point in the future.
Some of the ideas presented here sound really interesting - for example
I think that improving the Linux page cache to be more "arc-like" will
probably benefit not only btrfs. Having both the page cache and the arc
in parallel when using ZoL does not feel like an elegant solution, so
maybe there's hope for that. (But I don't know if it is feasible for ZoL
to abandon the arc in favor of an improved Linux page cache; I imagine
it might be much work for little benefit.)
Thanks again
Gert
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
