Error Message

stack from crash dump below was extracted:

crash> bt
PID: 10252 TASK: ffff8a81429584c0 CPU: 15 COMMAND: "rpm"
#0 [ffffa39e33b0ba68] machine_kexec at ffffffff9d05dd02
#1 [ffffa39e33b0bab8] __crash_kexec at ffffffff9d12107a
#2 [ffffa39e33b0bb78] crash_kexec at ffffffff9d122069
#3 [ffffa39e33b0bb90] oops_end at ffffffff9d02e091
#4 [ffffa39e33b0bbb0] no_context at ffffffff9d06dc7b
#5 [ffffa39e33b0bc00] __do_page_fault at ffffffff9d06e15c
#6 [ffffa39e33b0bc68] do_page_fault at ffffffff9d06e5bb
#7 [ffffa39e33b0bc90] page_fault at ffffffff9d801665
[exception RIP: vx_get_eatype+20]
RIP: ffffffffc0e65244 RSP: ffffa39e33b0bd40 RFLAGS: 00010246
RAX: ffff8a81a9933000 RBX: ffff8ac96d396c00 RCX: 0000000000000014
RDX: 0000000000000000 RSI: ffffffffc0f43f32 RDI: 0000000000000000
RBP: ffff8a81a9933558 R8: 0000000000000002 R9: 0000000000000000
R10: ffff8ab1cb5dea80 R11: 0000000000000000 R12: ffff8a81a9933600
R13: ffff8ab1cb5dea80 R14: 0000000000000000 R15: 0000000100048fb2
ORIG_RAX: ffffffffffffffff CS: 0010 SS: 0018
#8 [ffffa39e33b0bd40] vx_linux_removexattr at ffffffffc0e67526 [vxfs]
#9 [ffffa39e33b0bd78] __vfs_removexattr at ffffffff9d273145
#10 [ffffa39e33b0bda0] vfs_removexattr at ffffffff9d273967
#11 [ffffa39e33b0bdd8] removexattr at ffffffff9d273a1d
#12 [ffffa39e33b0bef0] path_removexattr at ffffffff9d273ac1
#13 [ffffa39e33b0bf28] sys_removexattr at ffffffff9d2742bf
#14 [ffffa39e33b0bf30] do_syscall_64 at ffffffff9d003934
#15 [ffffa39e33b0bf50] entry_SYSCALL_64_after_hwframe at ffffffff9d80009a
RIP: 00007fb95f231dc7 RSP: 00007ffc2607cb18 RFLAGS: 00000206
RAX: ffffffffffffffda RBX: 0000000001ab9100 RCX: 00007fb95f231dc7
RDX: 00007ffc2607cb50 RSI: 00007fb95eb161f4 RDI: 0000000001ab9100
RBP: 0000000000000000 R8: 0000000000000004 R9: 0000000000000000
R10: 000000006008de66 R11: 0000000000000206 R12: 0000000001a9dc50
R13: 0000000000000002 R14: 0000000001ae2b60 R15: 0000000001b225d0
ORIG_RAX: 00000000000000c5 CS: 0033 SS: 002b

The cause of the panic could be attributed to a known issue - namely a null pointer dereference panic when VxFS was setting an attribute in the user namespace.

A supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix. This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.

Veritas Technologies LLC currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.