From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mia <9speysdx24@kr33.de>, linux-btrfs@vger.kernel.org
Subject: Re: filesystem corrupt - error -117
Date: Mon, 25 Oct 2021 18:55:46 +0800 [thread overview]
Message-ID: <69109d24-efa7-b9d1-e1df-c79b3989e7bf@gmx.com> (raw)
In-Reply-To: <c2941415-e32f-b31d-0bc2-911ede3717b7@gmx.com>
On 2021/10/25 18:53, Qu Wenruo wrote:
>
>
> On 2021/10/25 16:46, Mia wrote:
>> Hello,
>> I need support since my root filesystem just went readonly :(
>>
>> [641955.981560] BTRFS error (device sda3): tree block 342685007872 owner
>> 7 already locked by pid=8099, extent tree corruption detected
>
> This line explains itself.
>
> Your extent tree is no corrupted, thus it allocated a new tree block
I missed the "w" for the word "now"...
> which is in fact already hold by other tree.
>
> This means your metadata is no longer protected properly by COW.
>
> "btrfs check" is highly recommended to expose the root cause.
>
>>
>> root@rx1 ~ # btrfs fi show
>> Label: none uuid: 21306973-6bf3-4877-9543-633d472dcb46
>> Total devices 1 FS bytes used 189.12GiB
>> devid 1 size 319.00GiB used 199.08GiB path /dev/sda3
>>
>> root@rx1 ~ # btrfs fi df /
>> Data, single: total=194.89GiB, used=187.46GiB
>> System, single: total=32.00MiB, used=48.00KiB
>> Metadata, single: total=4.16GiB, used=1.65GiB
>> GlobalReserve, single: total=380.45MiB, used=0.00B
>>
>> root@rx1 ~ # btrfs --version
>> :(
>> btrfs-progs v4.20.1
>>
>>
>> root@rx1 ~ # uname -a
>> Linux rx1 4.19.0-17-amd64 #1 SMP Debian 4.19.194-3 (2021-07-18) x86_64
>> GNU/Linux
>
> This is a little old for btrfs, but I don't think that's the cause.
>
> Thanks,
> Qu
>
>>
>> Hope someone can help.
>> Regrads
>> Mia
>>
next prev parent reply other threads:[~2021-10-25 10:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <em969af203-04e6-4eff-a115-1129ae853867@frystation>
2021-10-25 8:46 ` filesystem corrupt - error -117 Mia
2021-10-25 10:53 ` Qu Wenruo
2021-10-25 10:55 ` Qu Wenruo [this message]
[not found] ` <69109d24-efa7-b9d1-e1df-c79b3989e7bf@rx2.rx-server.de>
2021-10-25 11:13 ` Mia
2021-10-25 11:14 ` Qu Wenruo
2021-10-25 11:18 ` Qu Wenruo
[not found] ` <884d76d1-5836-9a91-a39b-41c37441e020@rx2.rx-server.de>
2021-10-25 17:09 ` Mia
2021-10-25 22:45 ` Qu Wenruo
[not found] ` <3ce1dd17-b574-abe3-d6cc-eb16f00117cc@rx2.rx-server.de>
2021-10-26 6:03 ` Mia
2021-10-26 7:24 ` Qu Wenruo
2021-10-26 11:18 ` Robert Krig
2021-10-26 14:12 ` Patrik Lundquist
[not found] ` <CAA7pwKOrgt6syr5C3X1+bC14QXZEJ+8HTMZruBBPBT574zNkkQ@rx2.rx-server.de>
2021-10-26 17:28 ` Mia
2021-10-27 2:49 ` Qu Wenruo
[not found] ` <emb611c0ff-705d-4c01-b50f-320f962f39fb@frystation>
2021-12-11 8:20 ` Mia
[not found] ` <embddc7343-8fdf-4be8-87d8-644e20ea86c0@frystation>
2021-12-11 8:28 ` Mia
2021-12-11 8:39 ` Qu Wenruo
[not found] ` <29fcb603-506f-d721-5214-2870ce2f8773@rx2.rx-server.de>
2021-12-11 9:10 ` Mia
[not found] ` <em7854e1bc-eb3d-43a3-abc7-c6ed3e1a167a@frystation>
2021-12-11 9:12 ` Mia
2021-12-11 9:19 ` Qu Wenruo
[not found] ` <114dbcbb-c0ad-6ffd-f9ff-7aff031d03b5@rx2.rx-server.de>
2021-12-11 9:34 ` Mia
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=69109d24-efa7-b9d1-e1df-c79b3989e7bf@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=9speysdx24@kr33.de \
--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).