From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: how do I know a subvolume is a snapshot?
Date: Wed, 17 Jul 2019 11:06:38 +0200 [thread overview]
Message-ID: <20190717090638.GB3462@tik.uni-stuttgart.de> (raw)
In-Reply-To: <TYAPR01MB33604A6035BF09518027AE12E5C90@TYAPR01MB3360.jpnprd01.prod.outlook.com>
On Wed 2019-07-17 (08:57), misono.tomohiro@fujitsu.com wrote:
> FYI, this problem should be fixed in mkfs.btrfs >= v4.16 since the top-level
> subvolume also gets non-empty UUID at mkfs time.
root@fex:~# lsb_release -d
Description: Ubuntu 18.04.2 LTS
root@fex:~# btrfs version
btrfs-progs v4.15.1
*sigh*
root@fex:~# uname -a
Linux fex 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Can I use/install a newer mkfs.btrfs or do I also have to install a newer
kernel version?
--
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:<TYAPR01MB33604A6035BF09518027AE12E5C90@TYAPR01MB3360.jpnprd01.prod.outlook.com>
next prev parent reply other threads:[~2019-07-17 9:06 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 [this message]
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=20190717090638.GB3462@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 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.