linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 10:12:25 -0400	[thread overview]
Message-ID: <ebb608fe-15f3-3b51-b06f-28c1dcfb6612@gmail.com> (raw)
In-Reply-To: <20170822135301.GF14804@rus.uni-stuttgart.de>

On 2017-08-22 09:53, Ulli Horlacher wrote:
> On Tue 2017-08-22 (09:37), Austin S. Hemmelgarn wrote:
> 
>>> root@fex:~# df -T /local/.backup/home
>>> Filesystem     Type  1K-blocks      Used Available Use% Mounted on
>>> -              -    1073740800 104252160 967766336  10% /local/.backup/home
>>
>> Hmm, now I'm really confused, I just checked on the Ubuntu 17.04 and
>> 16.04.3 VM's I have (I only run current and the most recent LTS
>> version), and neither of them behave like this.
> 
> I have this kind of output on all of my Ubuntu hosts:
> 
> root@moep:~# grep PRETTY_NAME /etc/os-release
> PRETTY_NAME="Ubuntu 16.04.3 LTS"
> 
> root@moep:~# df -T /usb/UF/tmp/blubb
> Filesystem     Type 1K-blocks    Used Available Use% Mounted on
> -              -     12581888 3690524   7253700  34% /usb/UF/tmp/blubb
> 
> root@moep:~# btrfs subvolume show /usb/UF/tmp/blubb
> /usb/UF/tmp/blubb
>          Name:                   blubb
>          UUID:                   ecf8c804-d4a3-9948-89fe-b0c1971c25cb
>          Parent UUID:            -
>          Received UUID:          -
>          Creation time:          2017-08-22 12:54:16 +0200
>          Subvolume ID:           262
>          Generation:             23
>          Gen at creation:        22
>          Parent ID:              5
>          Top level ID:           5
>          Flags:                  -
>          Snapshot(s):
> 
> root@moep:~# dpkg -l | grep btrfs
> ii  btrfs-tools                                 4.4-1ubuntu1                                 amd64        Checksumming Copy on Write Filesystem utilities
> 
Hmm, interesting.  Are you using qgroups by chance?


  reply	other threads:[~2017-08-22 14:12 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
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 [this message]
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=ebb608fe-15f3-3b51-b06f-28c1dcfb6612@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).