partmgr(1M)
partmgr - Partition Configuration Tool for Origin
As shipped in IRIX 6.5.30. Added in IRIX 6.5.15.
NAME partmgr - Partition Configuration Tool for Origin SYNOPSIS partmgr [-h] partmgr [-l] partmgr [-a] partmgr [-n] partmgr [-v] partmgr -c [-m modename] partmgr -x modename [-F] partmgr -s modename [-F] partmgr -i [-F] partmgr -d [-F] -f file partmgr -d [-F] -m modename -u [-e var=value]... partmgr -d [-F] -m modename [-p part -b bricks [-e var=value]...]... partmgr -d [-F] -m modename [-p part -r racks [-e var=value]...]... DESCRIPTION partmgr is the partitioning administration tool for the Origin 3000 series of servers. It provides the System Administrator with capabilities to define and store partition definitions, including partition id information for bricks and racks, and associated prom environment variables. You must have superuser privilege to use this command. If the system is configured as CAP_NO_SUPERUSER, you must have effective capabilities of CAP_SHUTDOWN, CAP_DEVICE_MGT and CAP_SYSINFO_MGT. All the affected partitions have to be rebooted in order to change the system to the new partition scheme. A multi brick Origin 3000 system can be divided into multiple independent units for the purposes of booting different kernels on them. These systems can be power cycled independently even though they are connected by the NUMAlink interconnect. The kernels can detect the presence of other partitions by using low level hardware support. A partition is identified by its partition id, part, a brick is identified by its brick id, brick, and a rack is identified by its rack id, rack. For more information on valid partitioning configurations, see the SGI Origin 3000 Partitioning Document. The partmgr command line options are: -h Help. Print a usage message. -l List brick ids of all known system bricks to standard out. -a List all currently defined modes. -n Display the current partition id. -v Display the environment variables for the current partition. -c Display mode configuration. If no mode is specified (-m modename), the current mode is displayed. -x modename Delete a mode. -s modename Set a mode to be the current mode. This may require some partitions to be rebooted. -i Same as "-s Unpartitioned". Initializes the system to the default unpartitioned state. -d Define a new mode. -m modename Specifies a mode name. This option is used with the -c and -d options. -u When defining a new mode, used to specify an unpartitioned system. -p part Specifies a partition id. A partition id is a number between 1 and 63, inclusive. The order of the -p, -b, -r and -e options is significant (see the EXAMPLES section below). -b bricks Specifies brick ids (example: 001c13). -r racks Specifies rack ids (example: 001). -e var=value Specifies an environment variable name/value pair. -f file When defining a new mode, used to specify an input file. -F Forces override of some sanity checks. This option should be used with caution. The user of partmgr should understand the consequences of using this option. EXAMPLES To define a mode for an 8 brick system with 2 partitions of 4 bricks each: partmgr -d -m modename -p 1 -b 001c10,001c13,001c16,001c21 \ -p 2 -b 001c24,001c29,001c32,001c35 To define a mode for an unpartitioned system with the prom environment variable AutoBoot set to No: partmgr -d -m modename -u -e AutoBoot=No Here are some examples of input files (-f option). The leading spaces are allowed, but not required; they are only added for readability. EXAMPLE 1: MODE modename1 PARTITION 1 BRICKS 001c10 001c13 001c16 001c21 ENVIRON AutoBoot=No PARTITION 2 BRICKS 002c10 002c13 002c16 002c21 ENVIRON AutoBoot=No OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0) SystemPartition=scsi(0)disk(1)rdisk(0)partition(8) EXAMPLE 2: MODE modename2 PARTITION 1 RACKS 001 002 PARTITION 2 RACKS 003 004 EXAMPLE 3: MODE modename3 UNPARTITIONED ENVIRON AutoBoot=No OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0) SystemPartition=scsi(0)disk(1)rdisk(0)partition(8) netaddr=128.162.192.65 NOTES For the partmgr command to function, all of the following requirements must be met: 1. The eoe.sw.partition software package must be installed. 2. The L1 and L2 firmware must be current. 3. Partitioning administration must be enabled in all L1s (using the partdb enable L1 command). 4. The mkpd daemon must be running on all partitions for partmgr to work. If this is not the case, the partmgr command may not be able to shutdown remote partitions. 5. For the prom to use the environment variables defined in the mode definition, the prom environment variable AutoPROMVars must be set to 1. The term brick in this document refers to a C-brick. The partition id of 0 has a special meaning in the OS and cannot be used on a partitioned system. Valid partition ids can be any number between 1 and 63, both included. DIAGNOSTICS The partmgr command does not respond to the interrupt key. This is because the partitioning information may be in an inconsistent state which may cause problems on a reboot. The partmgr command performs certain sanity checks on the partition config required by the user. It uses the partitioning information currently available to do this. Under certain conditions, these checks cannot proceed without input from the user. Partition ids must be unique and a brick can be included in 1 partition only. WARNINGS The partmgr command is not intended for casual use. If used incorrectly, it can completely freeze all partitions in the system and prevent it from even booting the PROM. It is strongly recommended that this command be used with the co-ordination of the System Administrators of all the current partitions.