From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: test if a subvolume is a snapshot?
Date: Fri, 8 Sep 2017 10:54:46 +0200 [thread overview]
Message-ID: <20170908085446.GA7876@rus.uni-stuttgart.de> (raw)
How can I test if a subvolume is a snapshot?
Example:
/test/.snapshot/2017-09-08_1037.single is a snapshot (of /test)
/test/data is a regular subvolume
I know this, because I have created them with suitable names :-)
But how can I see/test it?
root@fex:~/bin# btrfs subvol show /test/.snapshot/2017-09-08_1037.single
/test/.snapshot/2017-09-08_1037.single
Name: 2017-09-08_1037.single
UUID: eff1cebb-b885-6b47-ae69-36a7c3f266eb
Parent UUID: -
Received UUID: -
Creation time: 2017-09-08 10:37:04 +0200
Subvolume ID: 354
Generation: 237
Gen at creation: 237
Parent ID: 5
Top level ID: 5
Flags: readonly
Snapshot(s):
root@fex:~/bin# btrfs subvol show /test/data
/test/data
Name: data
UUID: b32a5949-dfd6-ef45-8616-34ae4cdf6fb8
Parent UUID: -
Received UUID: -
Creation time: 2017-09-06 18:30:33 +0200
Subvolume ID: 257
Generation: 224
Gen at creation: 8
Parent ID: 5
Top level ID: 5
Flags: -
root@fex:~/bin# btrfs subvol show /test
/test is toplevel subvolume
--
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:<20170908085446.GA7876@rus.uni-stuttgart.de>
next reply other threads:[~2017-09-08 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 8:54 Ulli Horlacher [this message]
2017-09-08 11:37 ` test if a subvolume is a snapshot? Peter Grandi
2017-09-08 13:10 ` David Sterba
2017-09-08 15:25 ` Tomasz Kłoczko
2017-09-08 15:38 ` Hugo Mills
2017-09-08 16:12 ` Tomasz Kłoczko
2017-09-08 16:24 ` Hugo Mills
2017-09-08 16:39 ` David Sterba
2017-09-08 18:09 ` Tomasz Kłoczko
2017-09-08 18:44 ` David Sterba
2017-09-08 19:06 ` Austin S. Hemmelgarn
2017-09-08 20:54 ` Tomasz Kłoczko
2017-09-11 12:44 ` Austin S. Hemmelgarn
2017-09-08 16:27 ` David Sterba
2017-09-08 18:41 ` Ulli Horlacher
2017-09-08 18:53 ` David Sterba
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=20170908085446.GA7876@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