From: Andrei Borzenkov <arvidjaar@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: find snapshot parent?
Date: Sun, 7 Jul 2019 08:27:06 +0300 [thread overview]
Message-ID: <8a75b6b5-1eba-b3ef-99f5-849f40e65d12@gmail.com> (raw)
In-Reply-To: <20190706204339.GB13656@tik.uni-stuttgart.de>
06.07.2019 23:43, Ulli Horlacher пишет:
> On Sat 2019-07-06 (19:57), Nikolay Borisov wrote:
>
>>> And how can I see whether /test/tmp/xx/ss1 is a snapshot at all?
>>> Do all snapshots have a "Parent UUID" and regular subvolumes not?
>>
>> Indeed, only snapshots have a Parent UUID.
>
> Not all:
>
> root@xerus:/test# btrfs subvolume snapshot -r /test /test/ss1
> Create a readonly snapshot of '/test' in '/test/ss1'
>
> root@xerus:/test# btrfs subvolume show /test/ss1
> /test/ss1
> Name: ss1
> UUID: 02bd07bc-0bab-3442-96be-40790e1ba9be
> Parent UUID: -
> Received UUID: -
> Creation time: 2019-07-06 22:37:37 +0200
> Subvolume ID: 1036
> Generation: 9824
> Gen at creation: 9824
> Parent ID: 5
> Top level ID: 5
> Flags: readonly
> Snapshot(s):
>
> root@xerus:/test# btrfs subvolume show /test
> /test is toplevel subvolume
>
Which is one more reason to not use btrfs top level directly.
next prev parent reply other threads:[~2019-07-07 5:28 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 [this message]
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
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=8a75b6b5-1eba-b3ef-99f5-849f40e65d12@gmail.com \
--to=arvidjaar@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