[LU-5599] Lustre Error: Impossible state: 4

• Type: Bug
• Resolution: Cannot Reproduce
• Priority: Major
• Affects Version/s: Lustre 2.4.3
• Environment: Fedora 19 x86_64 on Washington Pass nodes, 1GbE & FDR IB

Epic/Theme

Kernel Lustre-2.4 Panic

• Severity: 3
• Project: Fast Forward
• Assignee: Bob Glossman (Inactive)
• Reporter: Brian Bernel (Inactive)

Description

Lustre Version: 2.4.52
Kernel: patchless_client
Build: v2_4_52 0-gfdd4844-CHANGED-3.9.9-302.fc19.x86_64

2nd Instance:
-----------------
From: Cledat, Romain E
Sent: Monday, September 08, 2014 4:34 PM
To: Bernel, BrianX D
Subject: Error

Message from syslogd@bar1 at Sep 8 16:08:51 ...
kernel:[1235195.162972] LustreError: 85031:0:(osc_lock.c:1129:osc_lock_enqueue()) ASSERTION( ols->ols_state == OLS_NEW ) failed: Impossible state: 4 r
Message from syslogd@bar1 at Sep 8 16:08:51 ...
kernel:[1235195.193211] LustreError: 85031:0:(osc_lock.c:1129:osc_lock_enqueue()) LBUG

1st Instance:
-----------------
From: Nickerson, Brian R
Sent: Thursday, August 14, 2014 3:44 PM
To: Bernel, BrianX D; Cledat, Romain E
Subject: Kernel crash details

Message from syslogd@bar4 at Aug 14 15:34:57 ...
kernel:[1216856.270451] LustreError: 42598:0:(osc_lock.c:1129:osc_lock_enqueue()) ASSERTION( ols->ols_state == OLS_NEW ) failed: Impossible state: 4

Message from syslogd@bar4 at Aug 14 15:34:57 ...
kernel:[1216856.271008] LustreError: 42598:0:(osc_lock.c:1129:osc_lock_enqueue()) LBUG

Message from syslogd@bar4 at Aug 14 15:34:57 ...
kernel:[1216856.271830] Kernel panic - not syncing: LBUG

Issue Links

• is related to: LU-5910 LustreError: osc_lock_enqueue() Impossible state: 4
• is related to: LU-5492 osc_lock.c:1165:osc_lock_enqueue()) ASSERTION( ols->ols_state == OLS_NEW ) failed: Impossible state: 6

Comments

[Peter Jones]

Out of date ticket

[Brian Bernel (Inactive)]

Is there set of instructions somewhere on how to apply these patches?

[Jay Lan (Inactive)]

Peter,

Will do.

Jay

[Peter Jones]

Jay

I think that it makes sense to open a separate ticket for the NASA issue because the environments are really quite different and the root cause could be different

Peter

[Zhenyu Xu]

Can you try apply these patches?

http://review.whamcloud.com/#/c/8530/
http://review.whamcloud.com/#/c/9783/
http://review.whamcloud.com/#/c/9194/
http://review.whamcloud.com/#/c/9876/

[Jay Lan (Inactive)]

We had both of them in our 2.4.3-7nasC.