Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Archange <archange@archlinux.org>
To: linux-btrfs@vger.kernel.org
Subject: Critical error from Tree-checker
Date: Wed, 11 Sep 2024 01:05:17 +0400	[thread overview]
Message-ID: <9541deea-9056-406e-be16-a996b549614d@archlinux.org> (raw)

Hi there,

Since today, my system started randomly becoming read-only. At that 
point I can still run dmesg in an open terminal, so I’ve seen it was 
related to a btrfs error, but did not try anything since I could not 
open a web browser anymore. But I’ve seen the error to be “BTRFS 
critical” and related to a “corrupt leaf”.

I’ve tried to run `btrfs scrub` on the device after rebooting, and in 
fact it aborted almost right away triggering the same error in dmesg 
(but not turning the system read-only, so I can copy paste it here):

[  365.268769] BTRFS info (device dm-0): scrub: started on devid 1
[  385.788000] page: refcount:3 mapcount:0 mapping:00000000d0054cae 
index:0x9678888 pfn:0x11ce15
[  385.788015] memcg:ffff9fc94db8f000
[  385.788021] aops:btree_aops [btrfs] ino:1
[  385.788235] flags: 
0x2ffffa000004020(lru|private|node=0|zone=2|lastcpupid=0x1ffff)
[  385.788248] raw: 02ffffa000004020 ffffea9a8574ff88 ffffea9a847385c8 
ffff9fc95b8365b0
[  385.788255] raw: 0000000009678888 ffff9fc9ae554000 00000003ffffffff 
ffff9fc94db8f000
[  385.788259] page dumped because: eb page dump
[  385.788264] BTRFS critical (device dm-0): corrupt leaf: 
block=646267305984 slot=92 extent bytenr=1182031872 len=106496 invalid 
data ref objectid value 257
[  385.788283] BTRFS error (device dm-0): read time tree block 
corruption detected on logical 646267305984 mirror 1
[  385.796803] BTRFS info (device dm-0): scrub: not finished on devid 1 
with status: -5

According to https://btrfs.readthedocs.io/en/latest/Tree-checker.html 
this is not really expected, and the last paragraph says to report 
troubles here. So here I am, in the search for advice about this error 
(web searches returned nothing with this specific error except the 
commit/ml messages that added the code for it) and how to fix my random 
lockups.

Regards.

P.S.: I’m not subscribed to the list, so please keep me in copy when 
answering.


             reply	other threads:[~2024-09-10 21:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 21:05 Archange [this message]
2024-09-10 21:28 ` Critical error from Tree-checker Qu Wenruo
2024-09-10 21:37   ` Qu Wenruo
2024-09-11 19:55     ` Archange
2024-09-11 20:54       ` Qu Wenruo
2024-09-11 21:20         ` Archange
2024-09-11 21:23           ` Qu Wenruo
2024-09-11 21:42             ` Qu Wenruo
2024-09-11 22:06               ` Archange
2024-09-11 22:05             ` Archange
2024-09-11 22:34               ` Qu Wenruo
2024-09-12  8:21                 ` Archange
2024-09-12  8:25                   ` Qu Wenruo
2024-09-12  9:57                     ` Archange
2024-09-12 10:01                       ` Qu Wenruo
2024-09-12 10:04                         ` Archange
2024-09-12 10:23                           ` Qu Wenruo
2024-09-12 12:13                             ` Archange
2024-09-12 21:42                               ` Qu Wenruo
2024-09-13  5:25                                 ` Archange
2024-09-13  5:29                                   ` Qu Wenruo
2024-09-13  5:54                                     ` Archange
2024-09-13  6:12                                       ` Archange
2024-09-13  6:41                                       ` Qu Wenruo

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=9541deea-9056-406e-be16-a996b549614d@archlinux.org \
    --to=archange@archlinux.org \
    --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