From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: "Martin Mlynář" <nextsux@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Root volume (ID 5) in deleting state
Date: Mon, 13 Feb 2017 21:03:18 +0100 [thread overview]
Message-ID: <a103e413-d922-9c79-0075-1ce00a3cd7de@mendix.com> (raw)
In-Reply-To: <ed8d7383-c75c-584e-4722-c889c6f19a46@gmail.com>
On 02/13/2017 12:26 PM, Martin Mlynář wrote:
>
> I've currently run into strange problem with BTRFS. I'm using it as my
> daily driver as root FS. Nothing complicated, just few subvolumes and
> incremental backups using btrbk.
>
> Now I've noticed that my btrfs root volume (absolute top, ID 5) is in
> "deleting" state. As I've done some testing and googling it seems that
> this should not be possible.
>
> [...]
>
> # btrfs sub list -ad /mnt/btrfs_root/
> ID 5 gen 257505 top level 0 path <FS_TREE>/DELETED
I have heard rumours that this is actually a bug in the output of sub
list itself.
What's the version of your btrfs-progs? (output of `btrfs version`)
> # mount | grep btr
> /dev/mapper/vg0-btrfsroot on / type btrfs
> (rw,noatime,nodatasum,nodatacow,ssd,discard,space_cache,subvolid=1339,subvol=/rootfs)
>
> /dev/mapper/vg0-btrfsroot on /mnt/btrfs_root type btrfs
> (rw,noatime,nodatasum,nodatacow,ssd,discard,space_cache,subvolid=5,subvol=/)
The rumour was that it had something to do with using space_cache=v2,
which this example does not confirm.
> # uname -a
> Linux interceptor 4.9.6-1-ARCH #1 SMP PREEMPT Thu Jan 26 09:22:26 CET
> 2017 x86_64 GNU/Linux
>
> # btrfs fi show /
> Label: none uuid: 859dec5c-850c-4660-ad99-bc87456aa309
> Total devices 1 FS bytes used 132.89GiB
> devid 1 size 200.00GiB used 200.00GiB path /dev/mapper/vg0-btrfsroot
As a side note, all of your disk space is allocated (200GiB of 200GiB).
Even while there's still 70GiB of free space scattered around inside,
this might lead to out-of-space issues, depending on how badly
fragmented that free space is.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-02-13 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 11:26 Root volume (ID 5) in deleting state Martin Mlynář
2017-02-13 20:03 ` Hans van Kranenburg [this message]
2017-02-13 20:50 ` Martin Mlynář
2017-02-13 23:04 ` Hans van Kranenburg
2017-02-14 10:58 ` Martin Mlynář
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=a103e413-d922-9c79-0075-1ce00a3cd7de@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nextsux@gmail.com \
/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.