Hi Ciprian, I use ZFS and BTRFS for hosting volume partitions.
The main ingredient on BTRFS is to disable Copy-on-Write for the respective. This also somewhat mitigates surprising out-of-space issues. You need to provide the 'nodatacow' mount option. Additionally, depending on your exact setup, you may want to disable write barriers (e.g. for network attached storage, 'nobarrier') when it is without effect. That's basically it, because, as you pointed out yourself, AFS has only limited expectations from a filesystem. You lose data checksumming and compression on BTRFS. So, reasonable RAID config and scrubbing may be more important, now. Last remark. BTRFS, to my knowledge, does not support reservations. You MUST make sure to use a pre-allocated storage for the /vicepX mountpoint or the ugly day of failing AFS writes will come during your next overseas vacation. ZFS, although you don't want to go that way, works fine as well. Again, make sure to create a filesystem (i.e. subvolume) with a fixed reservation. AFAIK the FS takes care of providing enough space although you cannot disable COW. You keep all the goodies, duplication, deduplication, checksumming. I would suggest reading on ZFS setups for heavy database loads, should I have got you interested. I never used compression. Kind regards, –Michael _______________________________________________ OpenAFS-info mailing list OpenAFS-info@openafs.org http://lists.openafs.org/mailman/listinfo/openafs-info
