From: Ian Kelling <iank@fsf.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: I got a write time tree block corruption detected
Date: Sun, 10 Oct 2021 10:14:01 -0400 [thread overview]
Message-ID: <87k0ilj6lb.fsf@fsf.org> (raw)
In-Reply-To: <871r4wr1t3.fsf@fsf.org>
Update: btrfs check found no problem. I would really appreciate any
suggestions for next steps. Perhaps I should try a newer kernel and
btrfs-progs?
This reply took a few days because I got ooms and had to add ram. The
btrfs check was run on the disk that had the error reported, but I'm
going to run btrfs check on the other 3 disks now.
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
Opening filesystem to check...
Checking filesystem on /dev/mapper/btrfs0
UUID: cdbab81e-20ec-49e6-904c-649f6096b112
found 16065287630848 bytes used, no error found
total csum bytes: 15558808924
total tree bytes: 130372911104
total fs tree bytes: 106602610688
total extent tree bytes: 5744771072
btree space waste bytes: 21717413011
file data blocks allocated: 15935065186304
referenced 17934646562816
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
next prev parent reply other threads:[~2021-10-10 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 18:32 I got a write time tree block corruption detected Ian Kelling
2021-10-07 20:54 ` Ian Kelling
2021-10-10 14:14 ` Ian Kelling [this message]
2021-10-10 18:00 ` Zygo Blaxell
2021-10-10 20:52 ` Ian Kelling
2021-10-10 23:57 ` 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=87k0ilj6lb.fsf@fsf.org \
--to=iank@fsf.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