From: Ian Kelling <iank@fsf.org>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: I got a write time tree block corruption detected
Date: Sun, 10 Oct 2021 16:52:12 -0400 [thread overview]
Message-ID: <87o87w8pdj.fsf@fsf.org> (raw)
In-Reply-To: <20211010180055.GR29026@hungrycats.org>
Zygo Blaxell <ce3g8jdj@umail.furryterror.org> writes:
> This is a failure in log tree replay. 'btrfs rescue zero-log' should
> resolve it, though it will wipe out the last few seconds of writes to
> the filesystem.
That worked. The filesystem is mounted and working fine.
>
> I'd upgrade to at least a current LTS kernel (5.10). 5.8 is a year old
> and no longer maintained. The bug you have found may be fixed already.
Ok. Fyi, I upgraded to a 5.11 kernel & 5.14 btrfs-progs.
Thanks for the help and keep up the good work on btrfs!
--
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 22:51 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
2021-10-10 18:00 ` Zygo Blaxell
2021-10-10 20:52 ` Ian Kelling [this message]
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=87o87w8pdj.fsf@fsf.org \
--to=iank@fsf.org \
--cc=ce3g8jdj@umail.furryterror.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