[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
to answer to the mailing
>>> list since yesterday, but my mails seem to get dropped. So please see
>>> my answer to your mail enclosed.
>>>
>>> Thorsten
>>>
>>>
>>> -- Forwarded message -
>>> From: Thorsten Hirs
ying to answer to the mailing
> > list since yesterday, but my mails seem to get dropped. So please see
> > my answer to your mail enclosed.
> >
> > Thorsten
> >
> >
> > ------ Forwarded message -
> > From: Thorsten Hirsch
> > Dat
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 these commands.
Thorsten
[1] https://gist.github.com/thorstenhirsch/6
On 2019/3/22 上午7:23, Thorsten Hirsch wrote:
> Meanwhile I upgraded to kernel 5.0, but the problem remained the same. So I
> zeroed the log with btrfs rescue zero-log. The command was successful,
> however the problem still remains more or less the same, which means:
>
> - I still get a kernel
Meanwhile I upgraded to kernel 5.0, but the problem remained the same. So I
zeroed the log with btrfs rescue zero-log. The command was successful, however
the problem still remains more or less the same, which means:
- I still get a kernel oops when mounting.
- The stack trace looks a bit differ
