public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Paul-Erik Törrönen" <poltsi@poltsi.fi>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS-errors on a 20TB filesystem
Date: Wed, 8 Jul 2020 07:43:06 +0800	[thread overview]
Message-ID: <5ab5584d-abc9-2137-a8ec-1429dbe3b075@gmx.com> (raw)
In-Reply-To: <974197e0-0dc3-e0c4-6c44-b5fe8b6c6f6d@poltsi.fi>


[-- Attachment #1.1: Type: text/plain, Size: 2611 bytes --]



On 2020/7/8 上午2:43, Paul-Erik Törrönen wrote:
> Sorry for the delay :-/
> 
> On 7/7/20 1:58 AM, Qu Wenruo wrote:
>> Although still needs some extra dmesg context for the following bytenr:
>> - 2627928588288
>>    I see no obvious problem around slot 10
> 
> $ dmesg | grep 2627928588288
> [  595.081488] BTRFS critical (device sdc1): corrupt leaf: root=5
> block=2627928588288 slot=10 ino=11274213 file_offset=454656, extent end
> overflow, have file offset 454656 extent num bytes 18446744073709457408
> [  595.081589] BTRFS error (device sdc1): block=2627928588288 read time
> tree block corruption detected
> 
> This is repeated several times later on. The only thing preceeding this is:
> 
> [  243.295071] BTRFS info (device sdc1): disk space caching is enabled
> [  243.295075] BTRFS info (device sdc1): has skinny extents
> 
>> - 3154217795584
> 
> [  602.597770] BTRFS critical (device sdc1): corrupt leaf: root=5
> block=3154217795584 slot=102 ino=12990328 file_offset=184320, extent end
> overflow, have file offset 184320 extent num bytes 18446744073709395968
> [  602.597869] BTRFS error (device sdc1): block=3154217795584 read time
> tree block corruption detected
> 
>> - 3154257952768
>>    Mentioned slot doesn't exist at all, not sure what happened there
> 
> [  603.161394] BTRFS critical (device sdc1): corrupt leaf: root=5
> block=3154257952768 slot=59 ino=13467676 file_offset=262144, extent end
> overflow, have file offset 262144 extent num bytes 18446744073709527040
> [  603.168062] BTRFS error (device sdc1): block=3154257952768 read time
> tree block corruption detected
> 
>> - 3154259034112
>>    The offending slot seems fine
> 
> [  603.316595] BTRFS critical (device sdc1): corrupt leaf: root=5
> block=3154259034112 slot=27 ino=14013491 file_offset=102400, extent end
> overflow, have file offset 102400 extent num bytes 18446744073709514752
> [  603.323174] BTRFS error (device sdc1): block=3154259034112 read time
> tree block corruption detected
> 
>> - 3154291228672
>>    I guess the problem is hash mismatch, but can't confirm.
> 
> [  602.779540] BTRFS critical (device sdc1): corrupt leaf: root=5
> block=3154291228672 slot=9 ino=13286681 file_offset=204800, extent end
> overflow, have file offset 204800 extent num bytes 18446744073709481984
> [  602.786103] BTRFS error (device sdc1): block=3154291228672 read time
> tree block corruption detected
> 
> Does this help any?

OK, then all the same problem.

Thank you very much for all these detailed info!
Qu

> 
> Poltsi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-07 23:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 10:41 BTRFS-errors on a 20TB filesystem Paul-Erik Törrönen
2020-07-06 10:55 ` Qu Wenruo
     [not found]   ` <9a804cbb7406be31f55c68d592fd0bd6@poltsi.fi>
2020-07-06 11:33     ` Paul-Erik Törrönen
2020-07-06 11:51       ` Qu Wenruo
2020-07-06 15:00         ` Paul-Erik Törrönen
2020-07-06 22:58           ` Qu Wenruo
2020-07-07 18:43             ` Paul-Erik Törrönen
2020-07-07 23:43               ` Qu Wenruo [this message]
2020-07-08  6:17                 ` Paul-Erik Törrönen

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=5ab5584d-abc9-2137-a8ec-1429dbe3b075@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=poltsi@poltsi.fi \
    /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