From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: snapshots of encrypted directories?
Date: Fri, 15 Sep 2017 18:28:25 +0200 [thread overview]
Message-ID: <20170915162825.GC32347@rus.uni-stuttgart.de> (raw)
In-Reply-To: <CAEtw4r1KUQJGZkKEA+e3J=3+4a9hW+-ZBRBfTXhwYn4Ae30CCw@mail.gmail.com>
On Fri 2017-09-15 (12:15), Peter Becker wrote:
> 2017-09-15 12:01 GMT+02:00 Ulli Horlacher <framstag@rus.uni-stuttgart.de>:
>
> > On Fri 2017-09-15 (06:45), Andrei Borzenkov wrote:
> >
> >> The actual question is - do you need to mount each individual btrfs
> >> subvolume when using encfs?
> >
> > And even worse it goes with ecryptfs: I do not know at all how to mount a
> > snapshot, so that the user has access to it.
>
> A snapshot is simply a subvolume.
>
> Get the ID of the snapshot and mount it:
>
> btrfs subvolume list /btrfs
> mount -o subvolid=<ID> /dev/<DISK> /<MOUNTPOINT_ENCRYPTED>
>
> Or mount the snapshot directly by path:
>
> mount -o subvol=/snapshots/home/2015-12-01 /<MOUNTPOINT_ENCRYPTED>
>
> And then mount enryptfs:
>
> mount.ecryptfs /<MOUNTPOINT_ENCRYPTED> /<MOUNTPOINT_DECRYPTED>
This only possible by root.
For a user it is not possible to have access for his own snapshots.
Bad.
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<CAEtw4r1KUQJGZkKEA+e3J=3+4a9hW+-ZBRBfTXhwYn4Ae30CCw@mail.gmail.com>
next prev parent reply other threads:[~2017-09-15 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 14:57 snapshots of encrypted directories? Ulli Horlacher
2017-09-14 15:32 ` Hugo Mills
2017-09-15 3:45 ` Andrei Borzenkov
2017-09-15 10:01 ` Ulli Horlacher
2017-09-15 10:15 ` Peter Becker
2017-09-15 16:28 ` Ulli Horlacher [this message]
2017-09-15 17:16 ` Austin S. Hemmelgarn
2017-09-15 19:41 ` Ulli Horlacher
2017-09-18 11:45 ` Austin S. Hemmelgarn
2017-09-19 18:22 ` Dave
2017-09-15 12:35 ` Austin S. Hemmelgarn
2017-09-15 17:25 ` Andrei Borzenkov
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=20170915162825.GC32347@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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;
as well as URLs for NNTP newsgroup(s).