From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: find snapshot parent?
Date: Sun, 7 Jul 2019 01:24:44 +0200 [thread overview]
Message-ID: <20190706232444.GA22299@tik.uni-stuttgart.de> (raw)
In-Reply-To: <20190706155353.GA13656@tik.uni-stuttgart.de>
I have now implemented "btrfs_subvolume_list", example:
root@xerus:~# df3 -T
Filesystem Type Mbytes Used Available Use% Mounted on
/dev/sda1 ext4 20,029 4,482 14,507 24% /
/dev/sdd4 btrfs 53,247 101 51,052 1% /test
root@xerus:~# btrfs_subvolume_list
rw /test
ro /test/.snapshot/2019-07-06_2236.test <- /test
ro /test/snapshot_1 <- /test
ro /test/ss1 <- /test
ro /test/ss3 <- -
rw /test/tmp
ro /test/tmp/xx/ss1 <- /test/tmp
ro /test/tmp/xx/ss2 <- /test/tmp
ro /test/tmp/xx/ss3 <- /test/ss3
rw /test/tmp/zz2 <- /test/tux/zz
rw /test/tux/test
ro /test/tux/test/.snapshot/2017-12-02_1341.test <- /test/tux/test
rw /test/tux/test2 <- /test/tux/test
rw /test/tux/test2/test <- /test/tux/test
rw /test/tux/zz
<- means: is snapshot of ...
Note: I have deleted the subvolume parent of /test/ss3
Sourcecode is available under:
https://fex.rus.uni-stuttgart.de/fas/framstag@rus.uni-stuttgart.de/linuxtools/anonymous@fex.rus.uni-stuttgart.de/k5JuaCkGRqGOYeFUHuB47S35rhs3vBZo
--
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:<20190706155353.GA13656@tik.uni-stuttgart.de>
prev parent reply other threads:[~2019-07-06 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 15:53 find snapshot parent? Ulli Horlacher
2019-07-06 16:57 ` Nikolay Borisov
2019-07-06 20:43 ` Ulli Horlacher
2019-07-07 5:27 ` Andrei Borzenkov
2019-07-07 6:43 ` Nikolay Borisov
2019-07-07 7:37 ` Andrei Borzenkov
2019-07-07 9:12 ` Nikolay Borisov
2019-07-07 22:18 ` Ulli Horlacher
2019-07-08 4:05 ` Andrei Borzenkov
2019-07-06 23:24 ` Ulli Horlacher [this message]
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=20190706232444.GA22299@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;
as well as URLs for NNTP newsgroup(s).