From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Marc Lehmann <schmorp@schmorp.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs dev del not transaction protected?
Date: Sat, 21 Dec 2019 09:23:45 +0800 [thread overview]
Message-ID: <dda45fd3-0e77-6cd5-b351-52742dfb4aad@gmx.com> (raw)
In-Reply-To: <20191220170707.GA5577@schmorp.de>
[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]
On 2019/12/21 上午1:07, Marc Lehmann wrote:
>> Just while I was writing this mail, on 5.4.5, the _newly created_ btrfs
>> filesystem I restored to went into readonly mode with ENOSPC. Another
>> hardware problem?
>
> btrfs check gave me a possible hint:
>
> Checking filesystem on /dev/mapper/xmnt-cold15
> UUID: 6e035cfe-5b47-406a-998f-b8ee6567abbc
> [1/7] checking root items
> [2/7] checking extents
> [3/7] checking free space tree
> cache and super generation don't match, space cache will be invalidated
That's common, and not a problem at all.
Btrfs will rebuild the free space tree.
> [4/7] checking fs roots
> [no other errors]
>
> But mounting with clear_cache,space_cache=v2 didn't help, df still shows 0
> bytes free, "btrfs f us" still shows 3tb unallocated. I'll play around with
> it more...
Df reports 0 available is a bug and caused pinned down.
It's btrfs_statfs() can't co-operate with latest over-commit behavior.
This happens when there are some metadata operation queued.
It's completely a runtime false alert, had nothing incorrect on-disk.
I had a fix submitted for it.
https://patchwork.kernel.org/patch/11293419/
Thanks,
Qu
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-21 1:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 4:05 btrfs dev del not transaction protected? Marc Lehmann
2019-12-20 5:24 ` Qu Wenruo
2019-12-20 6:37 ` Marc Lehmann
2019-12-20 7:10 ` Qu Wenruo
2019-12-20 13:27 ` Marc Lehmann
2019-12-20 13:41 ` Qu Wenruo
2019-12-20 16:53 ` Marc Lehmann
2019-12-20 17:24 ` Remi Gauvin
2019-12-20 17:50 ` Marc Lehmann
2019-12-20 18:00 ` Marc Lehmann
2019-12-20 18:28 ` Eli V
2019-12-20 20:24 ` Chris Murphy
2019-12-20 23:30 ` Marc Lehmann
2019-12-21 20:06 ` Zygo Blaxell
2019-12-21 1:32 ` Qu Wenruo
2019-12-20 17:07 ` Marc Lehmann
2019-12-21 1:23 ` Qu Wenruo [this message]
2019-12-20 17:20 ` Marc Lehmann
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=dda45fd3-0e77-6cd5-b351-52742dfb4aad@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=schmorp@schmorp.de \
/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