Brian Ruthven - Sun UK wrote: > > Some thoughts (mostly nits): > > What happens if /usr is mounted from a separate device, and this > device is inaccesible until device_remap is run (i.e. chicken/egg > problem)? Or does this simply fall into the "boot the failsafe > archive" procedure you mention? > When a cpu node fails for some reason, the system will power off. When the system is powered back up, you have a system with fewer CPU nodes and the IO path of the devices on the failed CPU node would have reconfigured to a different path. If you boot up with the previous /dev links and /etc/path_to_inst files, those IO devices will not be accessible. So, boot the system in failsafe mode and run device_remap script which will update /dev and /etc/path_to_inst to match the new the path. > Is this specific to the T5440, or more general to the sun4v > architecture? i.e. should it go in > /usr/platform/SUNW,SPARC-Enterprise-T5440/sbin (or similar) rather > than /usr/platform/sun4v/sbin? > This script is not specific to T5440, it will be used by Rock. It can be used on a system which supports plx reconfig and the FW supports the ioalias MD property (FWARC 2008/349). It can be used on Maramba. Will remove T5440 from the description. > The man page seems to indicate this is specific to the T5440: > > DESCRIPTION > ... > The Device Remapping Script for SPARC Enterprise T5440 > servers remaps the device paths in /etc/path_to_inst > file and the symlinks under /dev. > > [ nit: remaps them to what? to "match the hardware" I suspect. Same at > the top of the usage section. ] > Yes, it remaps to match the hardware. Will make the change. Thanks. > What happens if I run this on a non-T5440 system, e.g. T2000? You will see the error message which is explained in the man page. "missing ioaliases node" > > Also in the USAGE section: > > 1. Boot an install miniroot, either with "boot net -s" or > "boot -F failsafe". > > > I don't think the failsafe is an install miniroot is it? Does that > matter? Would this be better as something like: > > 1. Boot either the failsafe miniroot using "boot -F failsafe", or an > install miniroot using "boot net -s" or similar. > > Will make this change. > Why is step 3 necessary - "cd /mnt" when the script is run from /mnt > anyway. Is the cwd significant? [ This picks up on Pete's comments > about the -d option ] > You do not have to specify -d option if step 3 is followed. > In step 5, does it matter how the system is rebooted? Must init be > used, or is "reboot" sufficient? I've even come across sysadmins who > think reboot == pull the power, but that's a different problem, and > not one PSARC can solve ;-) > No. You can use any boot command as long as you are booting from the disk you have run the script on.
-thanks sree
