From: "Libor Klepáč" <libor.klepac@bcom.cz>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: BTRFS and cyrus mail server
Date: Wed, 08 Feb 2017 19:38:06 +0100 [thread overview]
Message-ID: <24389268.gAX5gEpECb@libor-nb> (raw)
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
next reply other threads:[~2017-02-08 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 18:38 Libor Klepáč [this message]
2017-02-08 19:21 ` BTRFS and cyrus mail server Austin S. Hemmelgarn
2017-02-09 11:49 ` Adam Borowski
2017-02-09 12:53 ` Austin S. Hemmelgarn
2017-02-08 19:59 ` Kai Krakow
2017-02-08 23:19 ` Graham Cobb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24389268.gAX5gEpECb@libor-nb \
--to=libor.klepac@bcom.cz \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.