From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: finding root filesystem of a subvolume?
Date: Tue, 22 Aug 2017 09:27:14 -0400 [thread overview]
Message-ID: <16778020-9167-b7cc-4768-ee33dca2bbb7@gmail.com> (raw)
In-Reply-To: <20170822125030.GB14804@rus.uni-stuttgart.de>
On 2017-08-22 08:50, Ulli Horlacher wrote:
> On Tue 2017-08-22 (12:40), Hugo Mills wrote:
>> On Tue, Aug 22, 2017 at 02:23:50PM +0200, Ulli Horlacher wrote:
>>
>>> How do I find the root filesystem of a subvolume?
>>> Example:
>>>
>>> root@fex:~# df -T
>>> Filesystem Type 1K-blocks Used Available Use% Mounted on
>>> - - 1073740800 104244552 967773976 10% /local/.backup/home
>>
>> I've never seen the "- -" output from df before. Is this a bind
>> mount or something?
>
> No, /local/.backup/home is just a btrfs subvolume
It arguably shouldn't be showing up here then if it's not been
explicitly mounted. I'm betting you're running OpenSUSE or SLES and
they finally got their df integration done, as that df output absolutely
matches the type of brain-dead handling of BTRFS I'm coming to expect
out of them.
Note to SUSE people reading this: You should be including actual
information for at least the Type field, and ideally the Filesystem
field too. People expect this to behave reasonably, and not listing any
info about where the 'mount' originated or what it is is not reasonable.
next prev parent reply other threads:[~2017-08-22 13:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 12:23 finding root filesystem of a subvolume? Ulli Horlacher
2017-08-22 12:40 ` Hugo Mills
2017-08-22 12:50 ` Ulli Horlacher
2017-08-22 12:58 ` Marat Khalili
2017-08-22 13:12 ` Ulli Horlacher
2017-08-22 13:41 ` Marat Khalili
2017-08-22 13:27 ` Austin S. Hemmelgarn [this message]
2017-08-22 13:30 ` Ulli Horlacher
2017-08-22 13:37 ` Austin S. Hemmelgarn
2017-08-22 13:45 ` Marat Khalili
2017-08-22 13:53 ` Ulli Horlacher
2017-08-22 14:12 ` Austin S. Hemmelgarn
2017-08-22 14:23 ` Hugo Mills
2017-08-22 14:37 ` Austin S. Hemmelgarn
2017-08-22 14:43 ` Peter Grandi
2017-08-22 15:03 ` Austin S. Hemmelgarn
2017-08-22 15:45 ` Ulli Horlacher
2017-08-22 16:48 ` Roman Mamedov
2017-08-22 17:41 ` Peter Grandi
2017-08-23 12:07 ` Austin S. Hemmelgarn
2017-08-23 13:14 ` Axel Burri
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=16778020-9167-b7cc-4768-ee33dca2bbb7@gmail.com \
--to=ahferroin7@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;
as well as URLs for NNTP newsgroup(s).