Re: read time tree block corruption detected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: read time tree block corruption detected
From: Nikolay Borisov <nborisov@xxxxxxxx>
Date: Fri, 17 Jan 2020 10:14:23 +0200
Cc: linux-btrfs <linux-btrfs@xxxxxxxxxxxxxxx>
In-reply-to: <CA+ZCqs5hLS3ekUpU8TTJq6UP9rjPYZjBwVYcC4xJcaMXuvSudQ@mail.gmail.com>
References: <CA+ZCqs6w2Nucbght9cax9+SQ1bHitdgDtLKPA973ES8PXh1EqQ@mail.gmail.com> <6ba43f60-22d1-52da-0e9a-8561b9560481@suse.com> <CA+ZCqs5=N5Hdf3NxZAmPCnA8wbcJPrcH8zM-fRbt-w8tL+TjUQ@mail.gmail.com> <53da4b02-6532-5bb9-391c-720947bac7f1@suse.com> <CA+ZCqs4pTKePM4NaStAs=CWYBZbA_btqip1WiU8DC6DL13Eh_Q@mail.gmail.com> <CA+ZCqs5hLS3ekUpU8TTJq6UP9rjPYZjBwVYcC4xJcaMXuvSudQ@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2


On 17.01.20 г. 9:54 ч., Peter Luladjiev wrote:
> Should I run with repair flag?
> 


Which version of progs do you have ? Because it seems original mode
(Default) finds the corrupted backref but lowmem doesn't ?

Follow-Ups:
- Re: read time tree block corruption detected
  - From: Peter Luladjiev

References:
- read time tree block corruption detected
  - From: Peter Luladjiev
- Re: read time tree block corruption detected
  - From: Nikolay Borisov
- Re: read time tree block corruption detected
  - From: Nikolay Borisov
- Re: read time tree block corruption detected
  - From: Peter Luladjiev
- Re: read time tree block corruption detected
  - From: Peter Luladjiev

Prev by Date: Re: read time tree block corruption detected
Next by Date: write time tree block corruption detected
Previous by thread: Re: read time tree block corruption detected
Next by thread: Re: read time tree block corruption detected
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]