Commands like df and ls hung on a shared filesystem using VxFS 7.4.2.2100 and RedHat 8
Article ID: 100054378
Updated On:
Description
Error Message
Analysis of resulting forced crash dumps showed commands hung with a stack like below:
PID: 3271950 TASK: ffff9a20f23bbd80 CPU: 24 COMMAND: "ls"
#0 [ffffbc2c22ae79e0] __schedule at ffffffffb80d3416
#1 [ffffbc2c22ae7a78] schedule at ffffffffb80d38a8
#2 [ffffbc2c22ae7a88] vxg_svar_sleep_unlock at ffffffffc12de21c [vxglm]
#3 [ffffbc2c22ae7ae0] vxg_ilock_wait at ffffffffc12f567c [vxglm]
#4 [ffffbc2c22ae7b20] vxg_range_cmn_lock at ffffffffc12f862c [vxglm]
#5 [ffffbc2c22ae7b78] vxg_api_range_lockwf at ffffffffc12fa993 [vxglm]
#6 [ffffbc2c22ae7bf0] vx_irwlock at ffffffffc0e64aa8 [vxfs]
#7 [ffffbc2c22ae7c20] vx_do_access at ffffffffc0eea16d [vxfs]
#8 [ffffbc2c22ae7c48] vx_access at ffffffffc0eea28b [vxfs]
#9 [ffffbc2c22ae7c78] inode_permission at ffffffffb7ae7786
#10 [ffffbc2c22ae7ca0] link_path_walk at ffffffffb7ae7e42
#11 [ffffbc2c22ae7d00] path_openat at ffffffffb7aea29b
#12 [ffffbc2c22ae7dd8] do_filp_open at ffffffffb7aeca93
#13 [ffffbc2c22ae7ee0] do_sys_open at ffffffffb7ad7b24
#14 [ffffbc2c22ae7f38] do_syscall_64 at ffffffffb780419b
#15 [ffffbc2c22ae7f50] entry_SYSCALL_64_after_hwframe at ffffffffb82000ad
.
Cause
The cluster hang was observed due to a deadlock within VxFS within one of the structures used. This was caused by a VxFS code regression related to changes in RedHat 8.
Resolution
VxFS 7.4.2.2201 was supplied to address. Please refer to Veritas Technical Support for the fix. Issue is also addressed in 7.4.2 Update 4, which is available on the Veritas Download Center portal.
Issue/Introduction
Commands like df and ls hung on a shared filesystem using VxFS 7.4.2.2100 and RedHat 8
Error Message
Analysis of resulting forced crash dumps showed commands hung with a stack like below:PID: 3271950 TASK: ffff9a20f23bbd80 CPU: 24 COMMAND: "ls"
#0 [ffffbc2c22ae79e0] __schedule at ffffffffb80d3416
#1 [ffffbc2c22ae7a78] schedule at ffffffffb80d38a8
#2 [ffffbc2c22ae7a88] vxg_svar_sleep_unlock at ffffffffc12de21c [vxglm]
#3 [ffffbc2c22ae7ae0] vxg_ilock_wait at ffffffffc12f567c [vxglm]
#4 [ffffbc2c22ae7b20] vxg_range_cmn_lock at ffffffffc12f862c [vxglm]
#5 [ffffbc2c22ae7b78] vxg_api_range_lockwf at ffffffffc12fa993 [vxglm]
#6 [ffffbc2c22ae7bf0] vx_irwlock at ffffffffc0e64aa8 [vxfs]
#7 [ffffbc2c22ae7c20] vx_do_access at ffffffffc0eea16d [vxfs]
#8 [ffffbc2c22ae7c48] vx_access at ffffffffc0eea28b [vxfs]
#9 [ffffbc2c22ae7c78] inode_permission at ffffffffb7ae7786
#10 [ffffbc2c22ae7ca0] link_path_walk at ffffffffb7ae7e42
#11 [ffffbc2c22ae7d00] path_openat at ffffffffb7aea29b
#12 [ffffbc2c22ae7dd8] do_filp_open at ffffffffb7aeca93
#13 [ffffbc2c22ae7ee0] do_sys_open at ffffffffb7ad7b24
#14 [ffffbc2c22ae7f38] do_syscall_64 at ffffffffb780419b
#15 [ffffbc2c22ae7f50] entry_SYSCALL_64_after_hwframe at ffffffffb82000ad
.
Was this article helpful?
Yes
No
Powered by
