Hello, inspired by recent discussion on BTRFS vs. databases i wanted to ask on suitability of BTRFS for hosting a Cyrus imap server spool. I haven't found any recent article on this topic.
I'm preparing migration of our mailserver to Debian Stretch, ie. kernel 4.9 for now. We are using XFS for storage now. I will migrate using imapsync to new server. Both are virtual machines running on vmware on Dell hardware. Disks are on battery backed hw raid controllers over vmfs. I'm considering using BTRFS, but I'm little concerned because of reading this mailing list ;) I'm interested in using: - compression (emails should compress well - right?) - maybe deduplication (cyrus does it by hardlinking of same content messages now) later - snapshots for history - send/receive for offisite backup - what about data inlining, should it be turned off? Our Cyrus pool consist of ~520GB of data in ~2,5million files, ~2000 mailboxes. We have message size limit of ~25MB, so emails are not bigger than that. There are however bigger files, these are per mailbox caches/index files of cyrus (some of them are around 300MB) - and these are also files which are most modified. Rest of files (messages) are usualy just writen once. ----------- I started using btrfs on backup server as a storage for 4 backuppc run in containers (backups are then send away with btrbk), year ago. After switching off data inlining i'm satisfied, everything works (send/ receive is sometime slow, but i guess it's because of sata disks on receive side). Thanks for you opinions, Libor -- 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
