Error Unknown parameter `vxfs_max_scopes_possible' seen on boot-up after VxFS upgrade on RHEL 7/Infoscale 7.x versions
book
Article ID: 100049341
calendar_today
Updated On:
Cause
Few patches had not been built with the parameter "vxfs_max_scopes_possible", which had been introduced in earlier patches to fix a memory-related issue..
Resolution
If affected by this issue, please raise a call to Veritas Technical Support and request the following private hotfixes:
Issue/Introduction
After the upgrade, VxFS kernel modules failed to load.
And all the vxfs kernel libraries seem to be missing from the below location.
/lib/modules/<kernel version>/veritas/vxfs/
Error Message:
Below errors could be seen in system message logs:
Dec 2 13:15:49 xxxxxx systemd[1]: Starting Systemd Veritas vxfs-boot service...
Dec 2 13:15:56 xxxxxx kernel: vxfs: Unknown parameter `vxfs_max_scopes_possible'
Dec 2 13:15:56 xxxxxx kernel: vxfs: Unknown parameter `vxfs_max_scopes_possible'
Dec 2 13:15:56 xxxxxx vxfs[6245]: modprobe: ERROR: could not insert 'vxfs': Unknown symbol in module, or unknown parameter (see dmesg)
Dmesg:
Was this article helpful?
thumb_up
Yes
thumb_down
No