[LU-19130] conf-sanity test_32d: timeout due to zfs rmmod hang

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Fix Version/s: Lustre 2.18.0
• Affects Version/s: Lustre 2.17.0
• Severity: 3
• Assignee: WC Triage
• Reporter: Maloo

Description

This issue was created by maloo for Andreas Dilger <[e-mail]>

This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/087b40a3-8b7f-448a-afcd-9a09f9cceb07

test_32d failed with the following error:

Timeout occurred after 184 minutes, last suite running was conf-sanity

Test session details:
clients: https://build.whamcloud.com/job/lustre-reviews/114563 - 4.18.0-553.53.1.el8_10.x86_64
servers: https://build.whamcloud.com/job/lustre-reviews/114563 - 4.18.0-553.53.1.el8_lustre.x86_64

Lustre: DEBUG MARKER: trevis-65vm6.trevis.whamcloud.com: executing /usr/sbin/lustre_rmmod zfs
 Autotest: Test running for 95 minutes (lustre-reviews_review-dne-zfs-part-3_114563.37)
 INFO: task rmmod:429367 blocked for more than 120 seconds 4.18.0-553.53.1.el8_lustre.x86_64 #1
 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
 task:rmmod           state:D stack:0     pid:429367 ppid:429347 flags:0x00004080
 Call Trace:
  __schedule+0x2d1/0x870
  schedule+0x55/0xf0
  taskq_wait+0x7e/0xc0 [spl]
  zfs_fini+0x11/0x40 [zfs]
  zfs_kmod_fini+0x66/0xc0 [zfs]
  openzfs_fini+0xa/0xe97 [zfs]

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
conf-sanity test_32d - Timeout occurred after 184 minutes, last suite running was conf-sanity