HOW TO: Device Tree clenup on Solaris

Article:TECH167584  |  Created: 2011-08-19  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH167584
Article Type
Technical Solution


Environment

Issue



Multiple entried of same disk.


Solution




# powercf -q
# powermt config
(Only if Powerpath is configured)
These two steps focus on cleaning up the Powerpath configuration -- claiming newly added devices and eliminating outdated entries from the PP configuration, as well as updating current entries to reflect updated information.

# mv /etc/vx/array.info /etc/vx/array.info.old
# mv /etc/vx/disk.info /etc/vx/disk.info.old
# rm /dev/vx/dmp/*
# rm /dev/vx/rdmp/*

These steps focus on clearing Volume Manager device knowledge. Array.info and disk.info retain flat information regarding observed devices and arrays, and will match them up with preconfigured names based on their serial numbers.

Removing the /dev/vx/*dmp/* entries clears the on-disk record of Volume Manager devices. This is essential when rebuilding the VM in-core DMP tree as vxconfigd will attempt to base it's performance off this information if it exists, instead of a cold-query rebuild.

This procedure is incomplete though because erroneous entries can be locked into the kernel portion of the VM DMP tree, in which case the above steps + a reboot are required.


# rm /dev/dsk/*
# rm /dev/rdsk/*
# devfsadm -Cv

These commands then clear the OS level device tree and force Solaris to rebuild its own device tree. This resets the foundation for VM to scan and query on rebuild.

# vxdctl enable
# vxconfigd -k

These commands are duplicative to a degree and I would have preferred to simply do a vxconfigd restart. The vxdctl enable forces a device scan, while vxconfigd restart will also do a device scan (unloading and loading back into memory in the process).




Article URL http://www.symantec.com/docs/TECH167584


Terms of use for this information are found in Legal Notices