Hello Nikolay,
thank you.
echo w > /proc/sysrq-trigger
I assume, I need to do that soon after the problem occured? Is there a
way to automate it? Otherwise, I will most likely only notice days after
the occurence.
Regarding the Kernel Version:
I am using Debian, which usually delivers rather old kernels -but of
course possibly with backports of bug-fixes.
I am not sure, what the better option is:
1) to use the Kernel, Debian delivers
2) to build the latest Kernel every 3-6 months
3) to build the latest stable kernels
any advice welcome!
Regards,
Hendrik
------ Originalnachricht ------
Von: "Nikolay Borisov" <nbori...@suse.com>
An: "Hendrik Friedel" <hend...@friedels.name>;
linux-btrfs@vger.kernel.org
Gesendet: 06.03.2021 09:00:30
Betreff: Re: Code: Bad RIP value.
On 5.03.21 г. 21:57 ч., Hendrik Friedel wrote:
Hello,
I am using linux 5.9.1 and have experienced tracebacks in conjunction
with btrfs and several filesystems:
btrfs fi show
Label: 'Daten' uuid: c217331c-cf0c-49ae-86c7-48a67d1c346b
Total devices 1 FS bytes used 54.69GiB
devid 1 size 81.79GiB used 57.02GiB path /dev/sde2
Label: 'DockerImages' uuid: 9b327a02-606e-4f2d-a137-27f53a5bcb03
Total devices 1 FS bytes used 19.36GiB
devid 1 size 29.62GiB used 19.52GiB path /dev/sdd2
Label: 'DataPool1' uuid: c4a6a2c9-5cf0-49b8-812a-0784953f9ba3
Total devices 2 FS bytes used 6.87TiB
devid 1 size 7.28TiB used 6.92TiB path /dev/sda1
devid 2 size 7.28TiB used 6.92TiB path /dev/sdi1
I have this bug several times now:
This is not a bug per-se. It tells you that those 2 processes have been
blocked for more than 2 minutes. Are you using qgroups? 5.9 is not a
stable kernel so you are not going to receive updates for bugs which
might be fixed/backported to stable kernels/upstream releases. 5.9.1 is
not even the latest version for 5.9 branch. Next time this issue appears
show us the output of :
echo w > /proc/sysrq-trigger
