[LU-8523] sanity test_311: objs not destroyed after unlink Created: 22/Aug/16  Updated: 30/Dec/16  Resolved: 30/Aug/16

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

Type: Bug Priority: Minor
Reporter: Maloo Assignee: Lai Siyao
Resolution: Fixed Votes: 0
Labels: None
Environment:

Client/ Server: master, build# 41095 , RHEL 7.2


Issue Links:
Duplicate
Related
is related to LU-4825 lfs migrate not freeing space on OST Resolved
is related to LU-8981 sanity test_311: objs not destroyed a... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Saurabh Tandan <saurabh.tandan@intel.com>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/7359c424-6700-11e6-906c-5254006e85c2.

The sub-test test_311 failed with the following error:

objs not destroyed after unlink

Test log:

== sanity test 311: disable OSP precreate, and unlink should destroy objs ============================ 04:03:47 (1471691027)
total: 1000 creates in 2.76 seconds: 362.85 creates/second
CMD: onyx-30vm7 lctl get_param -n 			osp.*OST0000*MDT0000.create_count
CMD: onyx-30vm7 lctl get_param -n 				osp.*OST0000*MDT0000.max_create_count
CMD: onyx-30vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
CMD: onyx-30vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
CMD: onyx-30vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
CMD: onyx-30vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=0
 - unlinked 0 (time 1471691032 ; total 0 ; last 0)
total: 1000 unlinks in 3 seconds: 333.333344 unlinks/second
CMD: onyx-30vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-30vm7 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=64
CMD: onyx-30vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-30vm3 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=64
CMD: onyx-30vm7 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-30vm7 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=64
CMD: onyx-30vm3 lctl set_param -n 			osp.*OST0000*MDT000?.max_create_count=20000
CMD: onyx-30vm3 lctl set_param -n 			osp.*OST0000*MDT000?.create_count=64
waited 120 sec, old Iused 2891, new Iused 2011
 sanity test_311: @@@@@@ FAIL: objs not destroyed after unlink 


 Comments   
Comment by Andreas Dilger [ 26/Aug/16 ]

This was introduced by the patch http://review.whamcloud.com/16105 :

LU-4825 osp: check max_create_count before use OSP
    
    in OSP precreate, if max_create_count is 0, return error directly
    to use next OST, this can be used in OST migration.
    
    add sanity.sh 311 for this.
Comment by Lai Siyao [ 29/Aug/16 ]
old Iused 2891, new Iused 2011

it shows 880 object destroyed, while the script requires 900, maybe it's a bit too strict, I'll decrease it to 800 to see whether it still happens.

Comment by Gerrit Updater [ 29/Aug/16 ]

Lai Siyao (lai.siyao@intel.com) uploaded a new patch: http://review.whamcloud.com/22210
Subject: LU-8523 test: sanity 311 is too strict
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 95f8d0219c6b7fd444bd0a59490c67e46e3d7083

Comment by Gerrit Updater [ 30/Aug/16 ]

Andreas Dilger (andreas.dilger@intel.com) merged in patch http://review.whamcloud.com/22210/
Subject: LU-8523 test: sanity 311 is too strict
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: d4a4c0795b3befb87d47a5bf441adeba3b1c36f8

Comment by Andreas Dilger [ 30/Aug/16 ]

Patch landed to master.

Please remember that patches which only affect tests can use
Test-Parameters: trivial, and if it is some test other than sanity and lnet-selftest then it should also include testlist=modified_test_name to test the modified test script. That reduces testing time, as well as reducing the risk of hitting unrelated test failures.

Comment by Bob Glossman (Inactive) [ 14/Nov/16 ]

another on b2_7_fe:
https://testing.hpdd.intel.com/test_sets/a4eb950c-aabd-11e6-a095-5254006e85c2

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