From: CACook@quantum-sci.com
To: ecryptfs@vger.kernel.org
Subject: Re: Encrypting BTRFS Volume
Date: Mon, 3 Dec 2012 09:56:52 -0800 [thread overview]
Message-ID: <201212030956.52866.CACook@quantum-sci.com> (raw)
In-Reply-To: <CACDOv81f5YRbrYCwLOMggoHCz9qy0z41DQEDDEqRQbTRJZ7oPg@mail.gmail.com>
On Monday, December 03, 2012 09:04:38 AM B. J. Potter wrote:
> OK. Here's an option. Rename your mount /media/encrypted. Make the
> ecryptfs directory there. Then mount that through ecryptfs as
> /media/backups. You are necessarily going to lose some btrfs
> features, here you lose subvolumes. You could set it up differently
> depending on what features you care about. You might also consider
> ZFS, which I think is better designed/implemented than BTRFS (but
> comes with other problems).
>
> As far as ecryptfs goes though. You just make a folder on some device
> (be it a subvolume, normal filesystem, whatever) and then mount it.
> Use that wherever you see fit.
OK thanks. But subvolumes are critical because we need backup snapshots. And so I am in this mess I have now.
next prev parent reply other threads:[~2012-12-03 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 21:06 Encrypting BTRFS Volume CACook
2012-12-03 15:01 ` CACook
2012-12-03 15:41 ` B. J. Potter
2012-12-03 16:39 ` CACook
2012-12-03 17:04 ` B. J. Potter
2012-12-03 17:56 ` CACook [this message]
2012-12-04 18:05 ` CACook
2012-12-05 2:46 ` B. J. Potter
2012-12-05 15:48 ` CACook
2012-12-05 23:39 ` Michael Chang
[not found] ` <201212041004.18477.CACook@quantum-sci.com>
2012-12-10 22:23 ` CACook
2012-12-11 1:51 ` Michael Chang
[not found] ` <201212061328.15342.CACook@quantum-sci.com>
[not found] ` <CAHcyQ+7UeWtYmfNFOMp6zuqVN=K2o=ebyhGuOAPDF5-oEBFU+w@mail.gmail.com>
2012-12-06 22:34 ` CACook
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=201212030956.52866.CACook@quantum-sci.com \
--to=cacook@quantum-sci.com \
--cc=ecryptfs@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