[LU-11803] sanity test 255c fails with 'Ladvise test 12, bad lock count, returned 1, actual 0'

• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Fix Version/s: Lustre 2.14.0
• Affects Version/s: Lustre 2.12.0
• Labels: ubuntu
• Environment: Ubuntu 18.04 clients
• Severity: 3
• Assignee: James A Simmons
• Reporter: James Nunez (Inactive)

Description

sanity test_255c fails with 'Ladvise test 12, bad lock count, returned 1, actual 0'. It looks like this is only impacting Ubuntu 18.04 client testing.

Looking at the client test_log from https://testing.whamcloud.com/test_sets/d1b23f66-fdd4-11e8-a97c-52540065bddc , a problem is that we can’t find lock_unused_count

== sanity test 255c: suite of ladvise lockahead tests ================================================ 19:46:58 (1544471218)
CMD: trevis-19vm3 /usr/sbin/lctl get_param -n version 2>/dev/null ||
				/usr/sbin/lctl lustre_build_version 2>/dev/null ||
				/usr/sbin/lctl --version 2>/dev/null | cut -d' ' -f2
Starting test test10 at 1544471219
Finishing test test10 at 1544471219
CMD: trevis-19vm3 /usr/sbin/lctl get_param -n ost.OSS.ost.stats
Starting test test11 at 1544471219
Finishing test test11 at 1544471219
CMD: trevis-19vm3 /usr/sbin/lctl get_param -n ost.OSS.ost.stats
error: get_param: param_path 'ldlm/namespaces/lustre-OST0000*osc-f*/lock_unused_count': No such file or directory
Starting test test12 at 1544471220
Finishing test test12 at 1544471220
error: get_param: param_path 'ldlm/namespaces/lustre-OST0000*osc-f*/lock_unused_count': No such file or directory

There are several example of this failure all for Ubuntu at
https://testing.whamcloud.com/test_sets/bd048afa-f713-11e8-b67f-52540065bddc
https://testing.whamcloud.com/test_sets/b223ccee-f778-11e8-b67f-52540065bddc
https://testing.whamcloud.com/test_sets/50f5970e-fa16-11e8-8a18-52540065bddc

Issue Links

• is duplicated by: LU-11806 sanity-hsm, sanity-dom, racer fails to run testing due to client mount fails with ‘File exists’
• is duplicated by: LU-11808 sanity-flr test 0b and 0c fails with ‘pool_new failed lustre.test_0b'
• is duplicated by: LU-11823 sanity-flr test 0b and 0c fails with ‘pool_new failed lustre.test_0b' on ARM
• is duplicated by: LU-12247 sanityn test 34 fails with 'test_34 returned 1'
• is related to: LU-13499 client UUID is truncated
• is related to: LU-11809 conf-sanity test 28A hangs on file system mount
• is related to: LU-13118 change client instance to respect ASLR
• is related to: LU-12521 print_instance() incorrect if fsname contains a dash
• is related to: LU-8066 Move lustre procfs handling to sysfs and debugfs.
• is related to: LU-11838 Support linux kernel version 4.18

Comments

[Gerrit Updater]

James Simmons ([e-mail]) uploaded a new patch: https://review.whamcloud.com/33894
Subject: LU-11803 tests: don't assume obd device name
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: ce075a8726fe822803f24d1b336301ad87e9ce12

[James A Simmons]

I see the issue. Its a test problem in this case. The people that wrote these test assume the obd device name is of the format $FSNAME-OST0000-osc-ffff* but that is not always the case. In newer kernels the ffff is filtered out. This also impacts older kernels running on non x86 platforms. For example on Power8 is lustre-OST0000-osc-c000001e4de63000. I will push a patch to fix this.

[James A Simmons]

Its the uuid issue. So newer kernels no long allow you to expose the pointer address to user land. We need to create a new UUID method that is not the pointer of an internal kernel object

[James A Simmons]

Let me look

[Andreas Dilger]

simmonsja this looks like fallout from moving parameters from /proc to /sys? The Ubuntu kernel is 4.15, which is definitely the newest one we have running, so may be more likely to be affected by these changes.

[James Nunez (Inactive)]

Since this is a similar failure, we are also seeing sanity-flr tests 0g and 31 fail with similar issues

== sanity-flr test 0g: lfs mirror create flags support =============================================== 00:45:20 (1544489120)
osc.lustre-OST0000-osc-        (ptrval).stats=clear
osc.lustre-OST0001-osc-        (ptrval).stats=clear
osc.lustre-OST0002-osc-        (ptrval).stats=clear
osc.lustre-OST0003-osc-        (ptrval).stats=clear
osc.lustre-OST0004-osc-        (ptrval).stats=clear
osc.lustre-OST0005-osc-        (ptrval).stats=clear
osc.lustre-OST0006-osc-        (ptrval).stats=clear
error: get_param: param_path 'osc/lustre-OST0000-osc-ffff*/stats': No such file or directory
 sanity-flr test_0g: @@@@@@ FAIL: read was not provided by OST1 

and

== sanity-flr test 31: make sure glimpse request can be retried ====================================== 00:46:46 (1544489206)
fail_loc=0x1A00
CMD: trevis-19vm3 grep -c /mnt/lustre-ost1' ' /proc/mounts || true
Stopping /mnt/lustre-ost1 (opts:) on trevis-19vm3
CMD: trevis-19vm3 umount -d /mnt/lustre-ost1
CMD: trevis-19vm3 lsmod | grep lnet > /dev/null &&
lctl dl | grep ' ST ' || true
CMD: trevis-19vm1.trevis.whamcloud.com lctl get_param -n at_min
can't get osc.lustre-OST0000-osc-ffff*.ost_server_uuid in 40 secs
error: get_param: param_path 'ldlm/namespaces/lustre-OST0000-osc-ffff*/lock_count': No such file or directory
error: get_param: param_path 'ldlm/namespaces/lustre-OST0001-osc-ffff*/lock_count': No such file or directory
 sanity-flr test_31: @@@@@@ FAIL: OST 1: no glimpse request was sent