[LU-16039] sanityn test_42b: create must fail Created: 22/Jul/22  Updated: 10/Aug/23

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

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

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for Alexander Boyko <c17825@cray.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/26b9e60e-ba87-432c-a05a-0382ef0ca835

test_42b failed with the following error:

== sanityn test 42b: pdirops: mkdir vs create ======================================================================== 20:11:36 (1657915896)
CMD: onyx-71vm19,onyx-71vm20 /usr/sbin/lctl set_param -n ldlm.namespaces.*mdt*.lru_size=clear
CMD: onyx-71vm19,onyx-71vm20 /usr/sbin/lctl get_param ldlm.namespaces.*mdt*.lock_unused_count ldlm.namespaces.*mdt*.lock_count
ldlm.namespaces.mdt-lustre-MDT0000_UUID.lock_count=11
ldlm.namespaces.mdt-lustre-MDT0002_UUID.lock_count=1
ldlm.namespaces.mdt-lustre-MDT0001_UUID.lock_count=1
ldlm.namespaces.mdt-lustre-MDT0003_UUID.lock_count=1
CMD: onyx-71vm19,onyx-71vm20 lctl set_param -n fail_loc=0x80000145 2>/dev/null || true
CMD: onyx-71vm19,onyx-71vm20 lctl set_param -n fail_loc=0 2>/dev/null || true
mkdir: cannot create directory '/mnt/lustre/f42b.sanityn': File exists
Conflict
 sanityn test_42b: @@@@@@ FAIL: create must fail 
  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:6522:error()
  = /usr/lib64/lustre/tests/sanityn.sh:1975:test_42b()

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanityn test_42b - create must fail



 Comments   
Comment by Arshad Hussain [ 02/Jun/23 ]

+1 on Master https://testing.whamcloud.com/test_sets/00cecaf4-2fbb-4e48-a077-7f1623a96be9

Comment by Arshad Hussain [ 10/Jul/23 ]

+1 on master https://testing.whamcloud.com/sub_tests/b355f4d2-02fe-4474-b171-ff218176d513

Generated at Sat Feb 10 03:23:27 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.