Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: badara+ml@gmail.com, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Snapper & apt-btrfs-snapshot on Ubuntu
Date: Wed, 2 Nov 2016 01:19:36 +0100	[thread overview]
Message-ID: <7d615bfc-b7f0-dd01-6cff-61d0f978fc53@mendix.com> (raw)
In-Reply-To: <CAN5=xXnZmaqApRds3w=AKLAvfk=+dEPNazEb+Tzym_=2OdnfzA@mail.gmail.com>

On 11/02/2016 01:00 AM, Ahmed Badr wrote:
> 
> Btrfs newbie here

Congrats!

> trying to figure out how to use it properly on Ubuntu
> 16.04 server.
> 
> I have root formated using Btrfs, and installed Snapper and everything
> seems to works fine. I installed apt-btrfs-snapshot which takes snapshot
> before and after apt-get just like OpenSUSE/Zypper and that seems to work
> fine too.
> 
> The problem is, unlike OpenSUSE/Zypper, on Ubuntu neither Snapper nor
> apt-btrfs-snapshot see the snapshots made by the other program. So I cannot
> list, compare or manage the apt-btrfs snapshots using snapper. Any way to
> fix this?

To get more info, try 'btrfs sub list -q /mountpoint'. This will show
you in where both tools create their snapshots, and it will show
(parent_uuid field) which subvolume they're taken from.

While all of the snapshots with a matching parent_uuid are snapshots of
the same thing in linear time for btrfs, the tools may have their own
added administration on top (like snapshot names, or directories they're
placed in), which prevents them from being able to do something with the
other ones. This is not the fault of btrfs, it's because those tools
probably are designed to ignore anything they didn't cause to happen
themselves.

-- 
Hans van Kranenburg

  reply	other threads:[~2016-11-02  0:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02  0:00 Snapper & apt-btrfs-snapshot on Ubuntu Ahmed Badr
2016-11-02  0:19 ` Hans van Kranenburg [this message]
2016-11-02 11:25   ` Ahmed Badr
2016-11-02 11:44     ` Austin S. Hemmelgarn
2016-11-02  6:03 ` Duncan
2016-11-02  6:31   ` Alex Powell
2016-11-02 11:18     ` Ahmed Badr
2016-11-02 11:56       ` Austin S. Hemmelgarn
2016-11-02 11:09   ` Ahmed Badr

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=7d615bfc-b7f0-dd01-6cff-61d0f978fc53@mendix.com \
    --to=hans.van.kranenburg@mendix.com \
    --cc=badara+ml@gmail.com \
    --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