From: Michael Schuerig <michael.lists@schuerig.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Snapper on Ubuntu
Date: Sat, 15 Mar 2014 15:42:02 +0100 [thread overview]
Message-ID: <12151050.DOANbtdZpp@fuchsia> (raw)
In-Reply-To: <53245E22.1060407@friedels.name>
On Saturday 15 March 2014 15:05:22 Hendrik Friedel wrote:
> Hello,
>
> I am not sure, whether this is the right place to ask this question
> -if not, please advise.
>
> Ubuntu installs on btrfs, creating subvolumes for the homes (/home),
> the root home (/root) and the root (/) named @home, @root and @
> respectively.
>
> When I install snapper I configure it like this
> snapper -c rt create-config /
> snapper -c home create-config /home
> snapper -c root create-config /root
> snapper -c Video create-config /mnt/BTRFS/Video/
>
> After executing snapper create several times, this results in
>
> #btrfs subvolume list /
> ID 258 gen 2615 top level 5 path @
> ID 259 gen 2611 top level 5 path @root
> ID 260 gen 2555 top level 5 path @home
> ID 281 gen 2555 top level 5 path @home/.snapshots
> ID 282 gen 2606 top level 5 path @root/.snapshots
> ID 283 gen 2562 top level 5 path @root/.snapshots/1/snapshot
> ID 284 gen 2563 top level 5 path @root/.snapshots/2/snapshot
> ID 285 gen 2573 top level 5 path @root/.snapshots/3/snapshot
[...]
> So, this all works for @root only, not for the other subvolumes.
>
> Do you have any suggestions, how to find the cause?
I think you may have forgotten to specify the config snapper is supposed
to use. Try
# snapper -c home create
# snapper -c Video create
Michael
--
Michael Schuerig
mailto:michael@schuerig.de
http://www.schuerig.de/michael/
next prev parent reply other threads:[~2014-03-15 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 14:05 Snapper on Ubuntu Hendrik Friedel
2014-03-15 14:42 ` Michael Schuerig [this message]
2014-03-15 17:47 ` Hendrik Friedel
2014-03-15 18:21 ` David Disseldorp
2014-03-16 10:27 ` Hendrik Friedel
2014-03-16 12:12 ` Arvin Schnell
2014-03-16 16:58 ` Hendrik Friedel
2014-03-16 17:45 ` Arvin Schnell
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=12151050.DOANbtdZpp@fuchsia \
--to=michael.lists@schuerig.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