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
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@xxxxxxxxx> 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@xxxxxxx> 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!
> > >
> >
