[LU-1765] client LBUGs with ASSERTION(atomic_read(&import->imp_refcount) < 0x5a5a5a) failed

• Type: Bug
• Resolution: Duplicate
• Priority: Minor
• Affects Version/s: Lustre 1.8.8
• Severity: 3
• Assignee: Niu Yawei (Inactive)
• Reporter: Kit Westneat (Inactive)

Description

Sanger has hit an LBUG on its clients:
ASSERTION(atomic_read(&import->imp_refcount) < 0x5a5a5a) failed

This appears to be a dupe of LU-919, but that patch was never landed on b1_8, though the patch was created. Is there any chance to get it landed? It failed the maloo test, but it doesn't look like that failure was investigated:
http://review.whamcloud.com/#change,1954

Issue Links

• duplicates: LU-919 Multiple wrong LBUGs checking cfs_atomic_t vars/fields with inacurate poison value of 0x5a5a5a
• Trackbacks: Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA

Comments

[Andreas Dilger]

Link this to LU-919.

[Peter Jones]

Niu

Could you please confirm whether this issue would indeed be addressed by your earlier patch and if so rebase it to see how it fares on autotest with the latest code.

Thanks

Peter