From: Hugo Mills <hugo@carfax.org.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: finding root filesystem of a subvolume?
Date: Tue, 22 Aug 2017 12:40:36 +0000 [thread overview]
Message-ID: <20170822124036.GA32302@carfax.org.uk> (raw)
In-Reply-To: <20170822122350.GA14804@rus.uni-stuttgart.de>
[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]
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?
> root@fex:~# btrfs subvolume show /local/.backup/home
> /local/.backup/home
> Name: home
> uuid: f86a2db0-6a82-124f-9a71-1cd4c20fd6fb
> Parent uuid: ba4d388f-44bf-7b46-b2b8-00e2a9a87181
> Creation time: 2017-08-10 22:19:15
> Object ID: 383
> Generation (Gen): 148
> Gen at creation: 148
> Parent: 5
> Top Level: 5
> Flags: readonly
> Snapshot(s):
>
>
> I know, the root filesystem is /local, but who can I show it by command?
Probably in /proc/self/mountinfo -- that should give you the full
set of applied mount options, plus the original source for the mount
(which will be a block device for most filesystem mounts, a path for
bind mounts, or something FS-specific for network filesystems).
Hugo.
--
Hugo Mills | And what rough beast, its hour come round at last /
hugo@... carfax.org.uk | slouches towards Bethlehem, to be born?
http://carfax.org.uk/ |
PGP: E2AB1DE4 | W.B. Yeats, The Second Coming
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-08-22 12:40 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 [this message]
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
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=20170822124036.GA32302@carfax.org.uk \
--to=hugo@carfax.org.uk \
--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).