From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-btrfs@vger.kernel.org
Subject: LVM vs btrfs as a "volume manager" for SANs
Date: Wed, 22 Apr 2009 21:20:23 +0200 [thread overview]
Message-ID: <49EF6DF7.9020406@wpkg.org> (raw)
Right now, the majority of Linux users probably have LVM on their SAN
devices (i.e those being iSCSI targets).
Using LVM on a SAN device is easy: just create a new logical volume or
its snapshot, make it a target to iSCSI initiators, done.
I was wondering how btrfs would fit here and if it could replace LVM.
I see the following benefits of using btrfs instead of LVM:
- you can create sparse files which would grow as iSCSI initators use
more space (you can do it with ext3 now as well)
- you can use btrfs compression, to further reduce used space and
perhaps increase speed (SANs are mostly IO bound, not CPU bound)
- LVM has a big performance hit when using snapshots; btrfs doesn't
However, with btrfs, I'm not sure about:
- what happens if SAN machine crashes while the iSCSI file images were
being written to; with LVM and its block devices, I'm somehow more
confident it wouldn't make more data loss than necessary
- taking snapshots of individual files (file images on SAN) is not
possible with btrfs? Probably they would have to be placed in separate
directories first to make snapshots - some minor manageability issue
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2009-04-22 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 19:20 Tomasz Chmielewski [this message]
2009-04-23 0:13 ` LVM vs btrfs as a "volume manager" for SANs Dmitri Nikulin
2009-04-23 18:45 ` Chris Mason
2009-04-23 23:34 ` Tomasz Chmielewski
2009-04-24 12:38 ` Chris Mason
2009-07-02 15:22 ` Tomasz Chmielewski
2009-07-06 18:51 ` Chris Mason
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=49EF6DF7.9020406@wpkg.org \
--to=mangoo@wpkg.org \
--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.