From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs@vger.kernel.org
Subject: Using noCow with snapshots ?
Date: Wed, 09 Apr 2014 13:15:24 +0200 [thread overview]
Message-ID: <1541415.olHfkWYf4R@zafu> (raw)
Hi,
In the quest for BTRFS and performance, and having received the advice to
"chattr +C" my akonadi DB directory to make it noCow, I would like to be sure
about what will happen when I take a snapshot of the concerned BTRFS
subvolume.
1/ Being noCow, will the database be modified in the snapshot as well,
efectively defeating the snapshot ?
2/ Being snapshotted, will the database be COWed even though it's supposed to
be noCow ?
3/ Are both options mutually incompatible in some more osbcure ways ?
I'd like to know where I'm going with this ;-)
TIA and kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
next reply other threads:[~2014-04-09 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 11:15 Swâmi Petaramesh [this message]
2014-04-09 11:41 ` Using noCow with snapshots ? Hugo Mills
2014-04-09 11:56 ` Duncan
2014-04-10 8:22 ` Swâmi Petaramesh
2014-04-10 13:19 ` George Eleftheriou
2014-04-10 14:58 ` Duncan
2014-05-07 5:36 ` Russell Coker
2014-05-07 11:09 ` Duncan
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=1541415.olHfkWYf4R@zafu \
--to=swami@petaramesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox