From: "Piotr Pawłow" <pp@siedziba.pl>
To: Hugo Mills <hugo@carfax.org.uk>,
sri <toyours_sridhar@yahoo.co.in>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs freeze/thaw when using with LVM2
Date: Mon, 27 Apr 2015 17:58:04 +0200 [thread overview]
Message-ID: <553E5C8C.4070202@siedziba.pl> (raw)
In-Reply-To: <20150427121521.GB18187@carfax.org.uk>
On 27.04.2015 o 14:15, Hugo Mills wrote:
> HOWEVER, you shouldn't take LVM snapshots of a btrfs filesystem AT ALL
I'd like to add, that generally when working with LVM and BTRFS, it's
probably a good idea to always use "device=" mount option to make it
scan only specified devices instead of all. I'd learned that the hard
way, when I enabled SSD caching, and got massive corruption, because
BTRFS mixed up cached devices with cache-origin devices. Now I have
"device=/dev/mapper/vg-home1,device=/dev/mapper/vg-home2" in mount
options in my fstab, and I can use LVM cache without worrying that
things will get mixed up again.
prev parent reply other threads:[~2015-04-27 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 12:05 btrfs freeze/thaw when using with LVM2 sri
2015-04-27 12:15 ` Hugo Mills
2015-04-27 14:41 ` sri
2015-04-27 14:55 ` Hugo Mills
2015-04-27 17:34 ` Roman Mamedov
2015-04-27 17:37 ` Hugo Mills
2015-04-27 17:56 ` sri
2015-04-27 15:58 ` Piotr Pawłow [this message]
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=553E5C8C.4070202@siedziba.pl \
--to=pp@siedziba.pl \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=toyours_sridhar@yahoo.co.in \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox