All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: how do I know a subvolume is a snapshot?
Date: Wed, 17 Jul 2019 13:29:00 +0300	[thread overview]
Message-ID: <CAA91j0U1QBruk+JPE4+FZwuKNOz+YeiQOaeM58Viu6iSCYc99g@mail.gmail.com> (raw)
In-Reply-To: <b2410ac6-34f9-f459-8301-c70fcbe6159e@suse.com>

On Wed, Jul 17, 2019 at 1:14 PM Nikolay Borisov <nborisov@suse.com> wrote:
>
>
>
> On 17.07.19 г. 12:11 ч., Ulli Horlacher wrote:
> > On Wed 2019-07-17 (11:24), Nikolay Borisov wrote:
> >>
> >>
> >> On 17.07.19 3. 2:24 G., Ulli Horlacher wrote:
> >>
> >>> I thought, I can recognize a snapshot when it has a Parent UUID, but this
> >>> is not true for snapshots of toplevel subvolumes:
> >>
> >> As you have asked this before - in my testing this is not true.
> >
> > It is true on all my SUSE and Ubuntu systems, for all versions.
>
> That's strange, as I've shown in the previous thread, using the latest
> master doesn't exhibit this behavior.

I doubt you are not aware that distributions rarely use latest master.

Actually I have here openSUSE Tumbleweed; root top level subvolume
does not have UUID but if I create new filesystem *now* it does. btrfs
tools have been updated since initial installation.

Better question would be - is it possible to fix it for existing
filesystems that had been created using old tools?

  reply	other threads:[~2019-07-17 10:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 23:24 how do I know a subvolume is a snapshot? Ulli Horlacher
2019-07-17  7:45 ` Bernhard Kühnel
2019-07-17  8:05   ` Ulli Horlacher
2019-07-17 10:33   ` Remi Gauvin
2019-07-17  8:23 ` Hans van Kranenburg
2019-07-17  8:57   ` misono.tomohiro
2019-07-17  9:06     ` Ulli Horlacher
2019-07-17  9:24       ` misono.tomohiro
2019-07-17  8:24 ` Nikolay Borisov
2019-07-17  9:11   ` Ulli Horlacher
2019-07-17 10:11     ` Nikolay Borisov
2019-07-17 10:29       ` Andrei Borzenkov [this message]
2019-07-17 11:19         ` Nikolay Borisov
2019-07-17 17:39           ` Andrei Borzenkov
2019-07-17 18:16             ` Nikolay Borisov

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=CAA91j0U1QBruk+JPE4+FZwuKNOz+YeiQOaeM58Viu6iSCYc99g@mail.gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.