From: Spencer Collyer <spencer@lasermount.plus.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Write time tree block corruption detected
Date: Thu, 13 Aug 2020 06:53:29 +0100 [thread overview]
Message-ID: <20200813065329.117ef895@lasermount.plus.com> (raw)
In-Reply-To: <b8fefd9f-3f95-1d81-95f6-f1424640052d@gmx.com>
On Wed, 12 Aug 2020 22:15:23 +0800, Qu Wenruo wrote:
> On 2020/8/12 下午9:49, Spencer Collyer wrote:
> > I have just received a 'write time tree block corruption detected'
> > message on a BTRFS fs I use. As per
> > https://btrfs.wiki.kernel.org/index.php/Tree-checker it mentions
> > sending a mail to this mailing list for this case.
> >
> > The dmesg output from the error onwards is as follows:
> >
> > [17434.620469] BTRFS error (device dm-1): block=13642806624256
> > write time tree block corruption detected
>
> What's the line before this line?
>
> That's the most important line, and it's unfortunately not there...
>
> Thanks,
> Qu
Oh, didn't realise that. Unfortunately it has gone from the dmesg ring buffer, so I can't go back to it. If it happens again I'll take a copy of the full dmesg output so I can go back to it.
The page I mentioned previously (https://btrfs.wiki.kernel.org/index.php/Tree-checker) just mentions to report the error to this mailing list. Might be an idea to expand that line to explain what needs reporting.
Rereading the linked page, I notice that it says that if it is a write error that is prevented then the fs should still be OK, and you can run 'btrfs check --readonly' to check that. It is 'btrfs check --repair' that it says to not run unless told to by a developer. So I'm going to run the '--readonly' check and if that looks good I'll try re-running the command that caused the failure - does that seem reasonable?
Thanks for your attention,
Spencer
next prev parent reply other threads:[~2020-08-13 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 13:49 Write time tree block corruption detected Spencer Collyer
2020-08-12 14:15 ` Qu Wenruo
2020-08-13 5:53 ` Spencer Collyer [this message]
2020-08-13 5:58 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2021-05-30 21:30 auxsvr
2021-06-07 11:55 ` auxsvr
2021-06-08 14:45 ` auxsvr
2021-06-08 22:39 ` Qu Wenruo
2021-06-09 1:05 ` Qu Wenruo
2021-06-09 8:04 ` auxsvr
2021-06-09 8:32 ` Qu Wenruo
2021-06-11 19:44 ` auxsvr
2020-01-17 8:21 write " Kenneth Topp
2020-01-17 8:33 ` Qu Wenruo
2020-01-17 8:48 ` Kenneth Topp
2020-01-17 10:09 ` 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=20200813065329.117ef895@lasermount.plus.com \
--to=spencer@lasermount.plus.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.