[LU-12794] sanity test_133c: FAIL: The counter for destroy on ost1 was not incremented Created: 21/Sep/19  Updated: 21/Sep/19

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

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

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for jianyu <yujian@whamcloud.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/e91e8a18-dc38-11e9-add9-52540065bddc

test_133c failed with the following error:

== sanity test 133c: Verifying OST stats ============================================================= 05:24:56 (1569043496)
Waiting for local destroys to complete
CMD: trevis-66vm4 /usr/sbin/lctl set_param mdt.*.md_stats=clear
mdt.lustre-MDT0000.md_stats=clear
CMD: trevis-66vm3 /usr/sbin/lctl set_param obdfilter.*.stats=clear
obdfilter.lustre-OST0000.stats=clear
obdfilter.lustre-OST0001.stats=clear
obdfilter.lustre-OST0002.stats=clear
obdfilter.lustre-OST0003.stats=clear
obdfilter.lustre-OST0004.stats=clear
obdfilter.lustre-OST0005.stats=clear
obdfilter.lustre-OST0006.stats=clear
1+0 records in
1+0 records out
524288 bytes (524 kB) copied, 0.0046811 s, 112 MB/s
CMD: trevis-66vm3 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 0.00229545 s, 446 kB/s
CMD: trevis-66vm3 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats
CMD: trevis-66vm3 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats
Waiting for local destroys to complete
CMD: trevis-66vm3 /usr/sbin/lctl get_param obdfilter.lustre-OST0000.stats
 sanity test_133c: @@@@@@ FAIL: The counter for destroy on ost1 was not incremented

<<Please provide additional information about the failure here>>

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_133c - The counter for destroy on ost1 was not incremented


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