> On Mar 5, 2020, at 2:48 AM, Torsten Harenberg
> wrote:
>
> [QUOTA WARNING] Usage inconsistent for ID 2901:actual (757747712, 217)
> != expected (664182784, 215)
I assume you are running ldiskfs as the backend? If so, have you tried
regenerating the quota info for the OST? I believe the c
I understand you want to avoid deploying kdump, but you should focus on saving
your console history somewhere. It will be difficult to help without the panic
message.
For 2.10, maybe I was a bit optimistic. I think you should be able to build the
RPMs from sources, but pre-build packages are no
Hi Aurélien,
thanks for your quick reply, really appreciate it.
Am 05.03.20 um 10:20 schrieb Degremont, Aurelien:
> - What is the exact error message when the panic happens? Could you
> copy/paste few log messages from this panic message?
a running ssh shell only shows
kernel panic - not synce
Hello Torsten,
- What is the exact error message when the panic happens? Could you copy/paste
few log messages from this panic message?
- Did you try searching for this pattern onto jira.whamcloud.com, to see if
this is an already known bug.
- It seems related to quota. Is disabling quota an opt
