public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: how do I know a subvolume is a snapshot?
Date: Wed, 17 Jul 2019 01:24:56 +0200	[thread overview]
Message-ID: <20190716232456.GA26411@tik.uni-stuttgart.de> (raw)


I thought, I can recognize a snapshot when it has a Parent UUID, but this
is not true for snapshots of toplevel subvolumes: 

root@trulla:/# btrfs version
btrfs-progs v4.5.3+20160729

root@trulla:/# btrfs subvolume show /mnt/tmp
/mnt/tmp is toplevel subvolume

root@trulla:/# btrfs subvolume snapshot /mnt/tmp /mnt/tmp/ss
Create a snapshot of '/mnt/tmp' in '/mnt/tmp/ss'

root@trulla:/# btrfs subvolume create /mnt/tmp/xx
Create subvolume '/mnt/tmp/xx'

root@trulla:/# btrfs subvolume show /mnt/tmp/ss
/mnt/tmp/ss
        Name:                   ss
        UUID:                   7732bdde-0485-204e-b41b-833376e791da
        Parent UUID:            -
        Received UUID:          -
        Creation time:          2019-07-17 01:02:48 +0200
        Subvolume ID:           270
        Generation:             60
        Gen at creation:        60
        Parent ID:              5
        Top level ID:           5
        Flags:                  -
        Snapshot(s):

root@trulla:/# btrfs subvolume show /mnt/tmp/xx
/mnt/tmp/xx
        Name:                   xx
        UUID:                   342b2065-1679-8245-bd76-8da598cc33d8
        Parent UUID:            -
        Received UUID:          -
        Creation time:          2019-07-17 01:03:02 +0200
        Subvolume ID:           271
        Generation:             61
        Gen at creation:        61
        Parent ID:              5
        Top level ID:           5
        Flags:                  -
        Snapshot(s):

How do I know that /mnt/tmp/ss is a snapshot?
I cannot see a snapshot identifier.

-- 
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:<20190716232456.GA26411@tik.uni-stuttgart.de>

             reply	other threads:[~2019-07-16 23:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 23:24 Ulli Horlacher [this message]
2019-07-17  7:45 ` how do I know a subvolume is a snapshot? 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
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=20190716232456.GA26411@tik.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