How should I build the filesystems for dirvish?
Dirvish can back up almost any filesystem. Only the vaults on the backup server have any specific requirements. Only regular files will be shared between images. Device nodes, symlinks, directories and other file types will be recreated for each image. This means that there will be a lot more inodes used in a vault than the source filesystem. The best filesystem type for dirvish would be one that doesn’t set a fixed number of inodes at build time. The vaults will also need to be built with a filesystem type that supports hard links. While a journaling filesystem is a recommended the journals can have an adverse affect on performance. Dirvish and dirvish-expire do a lot of filesystem meta-data changes. This will stress the journal which in some cases is not as well optimized as one would like. Experience has shown that some journaling filesystems perform extremely poorly under dirvish. While no benchmarks have been made the difference in speed has been as high as 10:1. I would not recom
