![]() ![]() ![]() Once complete, modules should be loaded as shown below:Ĥ6 fffffffff02be000 44518 221 1 vxdmp (VxVM 5.0MP3: DMP Driver)Ĥ8 fffffffff0ba8000 2427b8 222 1 vxio (VxVM 5.0MP3 I/O driver)ĥ0 fffffffff0188348 e50 223 1 vxspec (VxVM 5.Multi-node configuration with Docker-Composeĭistributed Replicated Block Device (DRBD)Ĭonfiguring storage in the server installer Guided options Note that the add_drv command will also attempt to load corresponding kernel modules for device drivers being added to the system.Īfter checking the above points, if Volume Manager kernel modules are still not loaded, they should be manually loaded either by rebooting the machine and allowing normal startup, or via the modload command. If these entries are missing they should be replaced by using the add_drv command which can be used to add an undefined device driver to the system: # cat /etc/name_to_major | egrep "vxdmp|vxio|vxspec" ![]() As such /etc/name_to_major should contain a valid entry for each Volume Manager kernel module. As such if entries for Volume Manager kernel modules are missing from /etc/name_to_major, Volume Manager kernel modules may be unable to load. The Solaris operating system uses entries in /etc/name_to_major to bind device drivers such as Volume Manager kernel modules to major numbers. Check for valid driver to major number bindings in /etc/name_to_major: If the above entries are missing from /etc/system, or the modules are 'excluded' by use of the 'exclude' keyword, they should be manually added or modified to match the above.Ģ. Volume Manager kernel modules are loaded from /etc/system at boot time, and as such the /etc/system file should contain the following entries: Check for required entries in /etc/system to allow modules to load at boot time: If the modules are not loaded, the machine should be inspected to check that it is configured correctly to allow modules to be loaded during boot time or subsequent reboots.ġ. NOTE: vxdmp, vxio and vxspec are missing in the above output and as such are not loaded. To confirm whether modules are loaded using the applicable OS commands, such as lsmod, modinfo and so on:ġ61 fffffffff009b540 ca0 219 1 vxportal (VxFS 5.0_REV-5.0MP3A25_sol port)ġ62 fffffffff06e1000 1f49f0 21 1 vxfs (VxFS 5.0_REV-5.0MP3A25_sol SunO) This situation normally arises due to one or more of the Volume Manager kernel modules (vxio, vxspec, vxdmp), not being loaded. VxVM vxconfigd ERROR V-5-1-7840 cannot open /dev/vx/config: No such file or directory VxVM vxconfigd ERROR V-5-1-8726 /dev/vx/info: No such file or directory If Volume Manager kernel modules are not loaded, this can fail with an error indicating that '/dev/vx/info' does not exist. If the daemon is not running (as in this case), it can usually be restarted by running 'vxconfigd -k'. Vxconfigd is a user land process, so should be seen in the output of 'ps -ef' or similar. VxVM vxdisk ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible Under certain circumstances Volume Manager commands may report that the Volume Manager configuration daemon (vxconfigd) is not accessible, for example: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |