linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Tyler Richmond <t.d.richmond@gmail.com>,
	Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Fwd: Read time tree block corruption detected
Date: Thu, 7 May 2020 13:52:04 +0800	[thread overview]
Message-ID: <bbd08948-6672-4fb1-0e84-802482da7228@gmx.com> (raw)
In-Reply-To: <CAJheHN18TmG7g=-Sgi36hVmWka4z99rQRfaf=3FCRvat07C8pg@mail.gmail.com>


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



On 2020/5/7 下午1:43, Tyler Richmond wrote:
> Well, the repair doesn't look terribly successful.
> 
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4

This means there are more problems, not only the hash name mismatch.

This means the fs is already corrupted, the name hash is just one
unrelated symptom.

The only good news is, btrfs-progs abort the transaction, thus no
further damage to the fs.

Please run a plain btrfs-check to show what's the problem first.

Thanks,
Qu

> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> parent transid verify failed on 218620880703488 wanted 6875841 found 6876224
> Ignoring transid failure
> ERROR: child eb corrupted: parent bytenr=225049956061184 item=84
> parent level=1
>                                             child level=4
> ERROR: failed to zero log tree: -17
> ERROR: attempt to start transaction over already running one
> WARNING: reserved space leaked, flag=0x4 bytes_reserved=4096
> extent buffer leak: start 225049066086400 len 4096
> extent buffer leak: start 225049066086400 len 4096
> WARNING: dirty eb leak (aborted trans): start 225049066086400 len 4096
> extent buffer leak: start 225049066094592 len 4096
> extent buffer leak: start 225049066094592 len 4096
> WARNING: dirty eb leak (aborted trans): start 225049066094592 len 4096
> extent buffer leak: start 225049066102784 len 4096
> extent buffer leak: start 225049066102784 len 4096
> WARNING: dirty eb leak (aborted trans): start 225049066102784 len 4096
> extent buffer leak: start 225049066131456 len 4096
> extent buffer leak: start 225049066131456 len 4096
> WARNING: dirty eb leak (aborted trans): start 225049066131456 len 4096
> 
> What is going on?
> 
> On Wed, May 6, 2020 at 9:30 PM Tyler Richmond <t.d.richmond@gmail.com> wrote:
>>
>> Chris, I had used the correct mountpoint in the command. I just edited
>> it in the email to be /mountpoint for consistency.
>>
>> Qu, I'll try the repair. Fingers crossed!
>>
>> On Wed, May 6, 2020 at 9:13 PM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>>
>>>
>>>
>>> On 2020/5/7 上午5:54, Tyler Richmond wrote:
>>>> Hello,
>>>>
>>>> I looked up this error and it basically says ask a developer to
>>>> determine if it's a false error or not. I just started getting some
>>>> slow response times, and looked at the dmesg log to find a ton of
>>>> these errors.
>>>>
>>>> [192088.446299] BTRFS critical (device sdh): corrupt leaf: root=5
>>>> block=203510940835840 slot=4 ino=1311670, invalid inode generation:
>>>> has 18446744073709551492 expect [0, 6875827]
>>>> [192088.449823] BTRFS error (device sdh): block=203510940835840 read
>>>> time tree block corruption detected
>>>> [192088.459238] BTRFS critical (device sdh): corrupt leaf: root=5
>>>> block=203510940835840 slot=4 ino=1311670, invalid inode generation:
>>>> has 18446744073709551492 expect [0, 6875827]
>>>> [192088.462773] BTRFS error (device sdh): block=203510940835840 read
>>>> time tree block corruption detected
>>>> [192088.464711] BTRFS critical (device sdh): corrupt leaf: root=5
>>>> block=203510940835840 slot=4 ino=1311670, invalid inode generation:
>>>> has 18446744073709551492 expect [0, 6875827]
>>>> [192088.468457] BTRFS error (device sdh): block=203510940835840 read
>>>> time tree block corruption detected
>>>>
>>>> btrfs device stats, however, doesn't show any errors.
>>>>
>>>> Is there anything I should do about this, or should I just continue
>>>> using my array as normal?
>>>
>>> This is caused by older kernel underflow inode generation.
>>>
>>> Latest btrfs-progs can fix it, using btrfs check --repair.
>>>
>>> Or you can go safer, by manually locating the inode using its inode
>>> number (1311670), and copy it to some new location using previous
>>> working kernel, then delete the old file, copy the new one back to fix it.
>>>
>>> Thanks,
>>> Qu
>>>
>>>>
>>>> Thank you!
>>>>
>>>


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

  reply	other threads:[~2020-05-07  5:52 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJheHN0FUe-ijMco1ZOc6iKF2zbPocOw+iiVNeTT1r-JuXOJww@mail.gmail.com>
2020-05-06 21:54 ` Fwd: Read time tree block corruption detected Tyler Richmond
2020-05-06 23:55   ` Chris Murphy
2020-05-07  0:51     ` Tyler Richmond
2020-05-07  1:06       ` Chris Murphy
2020-05-07  1:13   ` Fwd: " Qu Wenruo
2020-05-07  1:30     ` Tyler Richmond
2020-05-07  5:43       ` Tyler Richmond
2020-05-07  5:52         ` Qu Wenruo [this message]
2020-05-07 15:52           ` Tyler Richmond
2020-05-08  0:11             ` Qu Wenruo
2020-05-08  4:23               ` Tyler Richmond
2020-05-08  5:07                 ` Qu Wenruo
2020-05-08  5:12                   ` Tyler Richmond
2020-05-08  5:47                     ` Qu Wenruo
2020-05-08 13:52                       ` Tyler Richmond
2020-08-18  3:36                         ` Tyler Richmond
     [not found]                         ` <CAJheHN3qwDAGY=z14zfO4LBrxNJZZ_rvAMsWLwe-k+4+t3zLog@mail.gmail.com>
2020-08-18  6:07                           ` Qu Wenruo
2020-08-18 12:18                             ` Tyler Richmond
2020-08-23  1:15                               ` Tyler Richmond
2020-08-23  1:51                                 ` Qu Wenruo
2020-08-23  2:31                                   ` Qu Wenruo
2020-08-23  2:49                                     ` Tyler Richmond
2020-08-23  4:28                                       ` Qu Wenruo
2020-08-24  2:47                                         ` Tyler Richmond
2020-08-24  8:26                                           ` Qu Wenruo
2020-08-25  5:25                                             ` Tyler Richmond
2020-08-25  6:37                                               ` Qu Wenruo
2020-08-25 13:30                                                 ` Tyler Richmond
2020-08-25 13:38                                                   ` Qu Wenruo
2020-08-25 13:43                                                     ` Tyler Richmond
2020-11-05  7:01                                                       ` Tyler Richmond
2020-11-05  7:19                                                         ` Qu Wenruo
2020-11-05 20:08                                                           ` Ferry Toth
2020-11-05 23:00                                                             ` Qu Wenruo
2020-11-05 23:12                                                               ` Ferry Toth
2020-11-05 23:32                                                                 ` Qu Wenruo
2020-11-05 23:37                                                                   ` Ferry Toth
2020-11-05 23:40                                                                     ` Qu Wenruo
2020-11-06 10:09                                                                       ` Ferry Toth
2020-11-06 10:24                                                                         ` Qu Wenruo
2020-11-06 10:27                                                                           ` Qu Wenruo
2020-11-06 10:32                                                                             ` Ferry Toth
2020-11-06 10:30                                                                           ` Ferry Toth
2020-11-06 10:32                                                                             ` Qu Wenruo
2020-11-07 11:18                                                                               ` Ferry Toth
2020-11-07 11:35                                                                                 ` Qu Wenruo
2020-11-07 13:19                                                                                   ` Ferry Toth
2020-11-07 13:28                                                                                     ` Qu Wenruo
2020-11-07 19:50                                                                                       ` Ferry Toth
2020-11-07 19:50                                                                                         ` Ferry Toth
2020-11-16 10:41                                                                                       ` Ferry Toth
2020-11-16 10:52                                                                                         ` Andrei Borzenkov
2020-11-16 10:57                                                                                           ` Ferry Toth
2020-11-16 16:35                                                                                             ` Tyler Richmond
2020-11-06 11:28                                                                             ` Ferry Toth
2020-08-23  2:32                                   ` Tyler Richmond

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=bbd08948-6672-4fb1-0e84-802482da7228@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=t.d.richmond@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).