On 2019/3/23 上午1:52, David Sterba wrote:
> On Fri, Mar 22, 2019 at 07:56:37AM +0800, Qu Wenruo wrote:
btrfs: Do mandatory tree block check before submitting bio
>>>
>>> All except 9 and 11 are going to misc-next after a final test. The two
>>> patches are only postponed, one for review and
On 2019/3/20 下午2:37, Qu Wenruo wrote:
> There is a report in kernel bugzilla about mismatch file type in dir
> item and inode item.
>
> This inspires us to check inode mode in inode item.
>
> This patch will check the following members:
> - inode key objectid
> Should be ROOT_DIR_DIR or [256,
[snip]
>
> This looks like the same problem I reported earlier this month, and
> also filed a bug for at
> https://bugzilla.kernel.org/show_bug.cgi?id=202717
>
> In my case I did a scrub and check before clearing space cache v1. No
> problems reported. And then clearing space cache v1 crashed.
On Sat, Mar 23, 2019 at 2:30 AM Thorsten Hirsch wrote:
>
> Hi Qu,
>
> thank you, but unfortunately that didn't work out so well. The tree
> dump was no problem [1], but clearing the space cache resulted in a
> core dump. Now btrfs check --readonly reports some errors. I attached
> the output of th
On 2019/3/24 下午6:49, Thorsten Hirsch wrote:
> Hi Qu,
>
> thank you once again for your advice. I could indeed recover all my
> data, even the snapshots docker had created. Everything's working as
> if nothing had ever happened. Here's what I've did in the end:
>
> btrfs recover worked flawles
Hi Qu,
thank you once again for your advice. I could indeed recover all my
data, even the snapshots docker had created. Everything's working as
if nothing had ever happened. Here's what I've did in the end:
btrfs recover worked flawless, but only recovered some data.
mount -o ro,notreelog,nolog
