[LU-3195] Interop 2.3.0<->2.3.63 sanity-quota test_6:

• Status: Resolved
• Project: Lustre
• Fix Version/s: Lustre 2.5.0
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: James Nunez (Inactive)
• Resolution: Fixed
• Severity: 3

Description

This issue was created by maloo for sarah <[e-mail]>

This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/e2a22f56-a90d-11e2-85b9-52540035b04c.

The sub-test test_6 failed with the following error:

LNet: Service thread pid 21586 was inactive for 40.00s. The thread might be hung, or it might only be slow and will resume later. Dumping the stack trace for debugging purposes:

The client is running 2.3.0 with test-framework.sh and sanity-quota.sh from lustre-master

Info required for matching: sanity-quota 6

Issue Links

• is related to: LU-2541 Interop 2.1.3<->2.4 failure on test s...
• is related to: LU-3304 Test failure on sanity-quota test_18:...

Comments

[Oleg Drokin]

https://maloo.whamcloud.com/test_logs/ebe6ed72-a90d-11e2-85b9-52540035b04c/show_text has the story
the test picked up watchdog trigger from a previous run and so we need to clear the dmesg buffer at the start of the test.

[Peter Jones]

James

Could you please look into this one?

Thanks

Peter

[James Nunez (Inactive)]

Oleg,

The dmesg log you point to is from the OSS. Do we need to clear dmesg from all servers; OSS, MDS and MGS?

Thanks,
James

Update: Please ignore this questions. Looking at test 18, it's clear what server's dmesg is being queried.

[James Nunez (Inactive)]

The proposed patch is at:

http://review.whamcloud.com/#change,6313

An explanation of the problem is located in the comment section for LU-3304.

[James Nunez (Inactive)]

Patch landed for 2.5