[LU-13624] conf-sanity test_23a: MOUNT_PID and MOUNT_LUSTRE_PID still not killed in 30 secs Created: 02/Jun/20  Updated: 19/Jul/21

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:
Duplicate
duplicates LU-13702 conf-sanity test_23a: FAIL: MOUNT_PID... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

This issue was created by maloo for S Buisson <sbuisson@ddn.com>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/6470bbf2-c1ce-4bd5-b1d0-690bec039a08

test_23a failed with the following error:

MOUNT_PID 26863 and  MOUNT_LUSTRE_PID 26864 still not killed in 30 secs

I think problem is that client fails to mount because MDS returns -EBUSY:

[ 3169.883883] Lustre: DEBUG MARKER: mount -t lustre -o user_xattr,flock trevis-65vm9@tcp:/lustre /mnt/lustre
[ 3169.938706] LustreError: 11-0: lustre-MDT0000-mdc-ffff97eb3a132000: operation mds_connect to node 10.9.6.63@tcp failed: rc = -16
[ 3174.953634] LustreError: 11-0: lustre-MDT0000-mdc-ffff97eb3a132000: operation mds_connect to node 10.9.6.63@tcp failed: rc = -16
[ 3174.955577] LustreError: Skipped 1 previous similar message
[ 3179.960277] LustreError: 11-0: lustre-MDT0000-mdc-ffff97eb3a132000: operation mds_connect to node 10.9.6.63@tcp failed: rc = -16
[ 3184.968338] LustreError: 11-0: lustre-MDT0000-mdc-ffff97eb3a132000: operation mds_connect to node 10.9.6.63@tcp failed: rc = -16
[ 3189.976513] LustreError: 11-0: lustre-MDT0000-mdc-ffff97eb3a132000: operation mds_connect to node 10.9.6.63@tcp failed: rc = -16
[ 3199.988494] LustreError: 11-0: lustre-MDT0000-mdc-ffff97eb3a132000: operation mds_connect to node 10.9.6.63@tcp failed: rc = -16

And on MDS side:

[ 3037.361893] Lustre: lustre-MDT0000: Denying connection for new client 7cbdf2cb-8da2-414d-8fee-141ab3f5b83f (at 10.9.6.204@tcp), waiting for 4 known clients (2 recovered, 0 in progress, and 0 evicted) to recover in 1:00
[ 3042.376786] Lustre: lustre-MDT0000: Denying connection for new client 7cbdf2cb-8da2-414d-8fee-141ab3f5b83f (at 10.9.6.204@tcp), waiting for 4 known clients (3 recovered, 0 in progress, and 0 evicted) to recover in 0:55
[ 3042.380154] Lustre: Skipped 1 previous similar message
[ 3047.384352] Lustre: lustre-MDT0000: Denying connection for new client 7cbdf2cb-8da2-414d-8fee-141ab3f5b83f (at 10.9.6.204@tcp), waiting for 4 known clients (3 recovered, 0 in progress, and 0 evicted) to recover in 0:50
[ 3052.392329] Lustre: lustre-MDT0000: Denying connection for new client 7cbdf2cb-8da2-414d-8fee-141ab3f5b83f (at 10.9.6.204@tcp), waiting for 4 known clients (3 recovered, 0 in progress, and 0 evicted) to recover in 0:45
[ 3057.400614] Lustre: lustre-MDT0000: Denying connection for new client 7cbdf2cb-8da2-414d-8fee-141ab3f5b83f (at 10.9.6.204@tcp), waiting for 4 known clients (3 recovered, 0 in progress, and 0 evicted) to recover in 0:40
[ 3067.415696] Lustre: lustre-MDT0002: haven't heard from client 866b971a-9ba8-4886-8081-42f773ebd8f4 (at 10.9.6.204@tcp) in 49 seconds. I think it's dead, and I am evicting it. exp ffff8d1e1578ac00, cur 1590861392 expire 1590861362 last 1590861343
[ 3067.415735] Lustre: lustre-MDT0000: Denying connection for new client 7cbdf2cb-8da2-414d-8fee-141ab3f5b83f (at 10.9.6.204@tcp), waiting for 4 known clients (3 recovered, 0 in progress, and 0 evicted) to recover in 0:30

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
conf-sanity test_23a - MOUNT_PID 26863 and MOUNT_LUSTRE_PID 26864 still not killed in 30 secs



 Comments   
Comment by Chris Horn [ 05/Jun/20 ]

+1 on master: https://testing.whamcloud.com/test_sessions/8100bdf2-6e89-492a-8746-2a20d6719c7b

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