[LU-8981] sanity test_311: objs not destroyed after unlink Created: 29/Dec/16  Updated: 17/Jan/19  Resolved: 18/Mar/17

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.10.0
Fix Version/s: Lustre 2.10.0

Type: Bug Priority: Minor
Reporter: Maloo Assignee: WC Triage
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Related
is related to LU-8523 sanity test_311: objs not destroyed a... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Bob Glossman <bob.glossman@intel.com>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/02b93f90-cdaf-11e6-9f17-5254006e85c2.

The sub-test test_311 failed with the following error:

objs not destroyed after unlink

This looks a lot like LU-8523, but that is closed as Fixed.
Raising this new ticket for a fresh instance on master.
Somebody more expert needs to figure out if this really is a new bug or the old bug coming back.

Info required for matching: sanity 311



 Comments   
Comment by Bob Glossman (Inactive) [ 09/Jan/17 ]

another on master:
https://testing.hpdd.intel.com/test_sets/273e90da-d6bb-11e6-b630-5254006e85c2

Comment by Lai Siyao [ 11/Jan/17 ]
== sanity test 311: disable OSP precreate, and unlink should destroy objs ============================ 14:13:41 (1484000021)
total: 1000 creates in 2.51 seconds: 398.60 creates/second
CMD: onyx-35vm7 lctl get_param -n 			osp.*OST0000*MDT0000.create_count
CMD: onyx-35vm7 lctl get_param -n 				osp.*OST0000*MDT0000.max_create_count
CMD: onyx-35vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
CMD: onyx-35vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
CMD: onyx-35vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
CMD: onyx-35vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
 - unlinked 0 (time 1484000024 ; total 0 ; last 0)
total: 1000 unlinks in 1 seconds: 1000.000000 unlinks/second
CMD: onyx-35vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-35vm7 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=128
CMD: onyx-35vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-35vm3 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=128
CMD: onyx-35vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-35vm7 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=128
CMD: onyx-35vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-35vm3 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=128
waited 120 sec, old Iused 2876, new Iused 2348
 sanity test_311: @@@@@@ FAIL: objs not destroyed after unlink 

It looks like the check is still too strict even with the fix from LU-8523, I'll make a patch later.

Comment by Gerrit Updater [ 11/Jan/17 ]

Lai Siyao (lai.siyao@intel.com) uploaded a new patch: https://review.whamcloud.com/24814
Subject: LU-8981 test: sanity 311 check is too strict
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: fa9e373263cc9efdad298cab0aafb4b20e9eb476

Comment by Gerrit Updater [ 01/Mar/17 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/24814/
Subject: LU-8981 test: sanity 311 check is too strict
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: ea5736257d8968fc22450ef502e14ea6755642f0

Comment by Peter Jones [ 18/Mar/17 ]

Landed for 2.10

Generated at Sat Feb 10 02:22:13 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.