Unix Administration

If you are facing below errors please follow the below steps to solve the issue. unix: [ID 286029 kern.notice] relocation error: R_SPARC_WDISP30: unix: [ID 720415 kern.notice] file /kernel/sys/sparcv9/nfs: unix: [ID 370954 kern.notice] symbol nfs_perror: unix: [ID 780480 kern.notice] value 0x1f9c400000004e49 does not fit unix: [ID 399259 kern.notice] do_relocations: /kernel/sys/sparcv9/nfs do_relocate failed unix: [ID 603676 kern.notice] nfs error doing relocations unix: [ID 286029 kern.notice] relocation error: R_SPARC_WDISP30: unix: [ID 720415 kern.notice] file /kernel/sys/sparcv9/nfs: unix: [ID 370954 kern.notice] symbol nfs_perror: unix: [ID 780480 kern.notice] value 0xe41c400000004e49 does not fit unix: [ID 399259 kern.notice] do_relocations: /kernel/sys/sparcv9/nfs do_relocate failed unix: [ID 603676 kern.notice] nfs error doing relocations genunix: [ID 603404 kern.notice] NOTICE: core_log: sshd[23915] core dumped: /var/cores/s root# cksum /kernel/fs/sparcv9/nfs 2123707346...

Using Extended Accounting Functionality Users can manage extended accounting (start accounting, stop accounting, and change accounting configuration parameters) if they have the appropriate rights profile for the extended accounting type to be managed: Flow Management Process Management Task Management How to Activate Extended Accounting for Processes, Tasks, and Flows To activate the extended accounting facility for tasks, processes, and flows, use the acctadm command. The optional final parameter to acctadm indicates whether the command should act on the process, system task, or flow accounting components of the extended accounting facility. Become superuser or assume an equivalent role. Roles contain authorizations and privileged commands. Activate extended accounting for processes. # acctadm -e extended -f /var/adm/exacct/proc process Activate extended accounting for tasks. # acctadm -e extended,mstate -f /var/adm/e...

Cleaning up the Operating System device tree after removing LUNs - Solaris 10 example You must clean up the device tree after removing LUNs. The OS commands may vary for Solaris versions. This procedure uses Solaris 10 with Leadville stack as an example. Contact Sun Support if any of the steps in this section fail to produce the wanted results. To clean up the device tree after you remove LUNs The removed devices show up as drive not available in the output of the format command: 413. c3t5006048ACAFE4A7Cd252 <drive not available> /pci@1d,700000/SUNW,qlc@1,1/fp@0,0/ssd@w5006048acafe4a7c,fc After the LUNs are unmapped using Array management or the command line, Solaris also displays the devices as either unusable or failing . bash-3.00# cfgadm -al -o show_SCSI_LUN | grep -i unusable c2::5006048acafe4a73,256 disk connected configured unusable c3::5006048acafe4a7c,255 disk connected configured unusable bash-3.00# cfgadm -al -o show_SCS...

Issue Vxconfigd daemon logs error during system boot or during vxconfigd restart. Error vxvm:vxconfigd: [ID 567584 daemon.error] V-5-1-8645 Error in claiming /dev/rdsk/emcpower0c by NR list: No such device or address vxvm:vxconfigd: [ID 278821 daemon.error] V-5-1-8645 Error in claiming /dev/rdsk/emcpower1c by NR list: No such device or address   Cause These messages are logged due to stale device entries in Solaris device directory /dev/dsk and /dev/rdsk. The device listed in the error message no longer exists,  which can be confirmed through Solaris format command. # echo | format Solution To prevent these messages, remove the stale device entries in the Solaris device directories /dev/dsk and /dev/rdsk. This can typically be accomplished with the command: # devfsadm -C or a reconfiguration reboot.

Issue Duplicate devices visible in "vxdisk list", getting error V-5-1-8645 Solution In case of some of Sun servers, the internal hard disks are fibre channel drives. In occurance of any failure to these drives, some steps should be followed as explained in bottom. Explanation: If disk is directly removed from the server, that might leave the stale wwn number into configuration of operating system because of which Veritas is not able to correctly determine the device. As a result of this, you might see duplicate entries in "vxdisk list" output. In this case even device tree cleaning doesn't helps rather you see error in the last step: here is the procedure to clean device tree: # mv /etc/vx/disk.info /etc/vx/disk.info.old # rm /dev/vx/rdmp/* # rm /dev/vx/dmp/* # rm /dev/rdsk/* # rm /dev/dsk/* # devfsadm -Cv # vxconfigd -k In last step above, When you do "vxconfigd -k" to rebuild the DMP device tree structure, you get following e...