HP-UX/Tru64 UNIX System Administration Interoperability phần 9 docx

Storage and File System Administration Commands and Utilities Chapter 13 289 lvsync Synchronize stale mirrors in LVM logical volumes The mkfdmn command (Tru64 UNIX) The mkfdmn command creates a domain, a logical construct containing both physical volumes (disks or disk partitions) and filesets. You must specify one volume when you create a domain. This can be an LSM volume. The mkfset command (Tru64 UNIX) The mkfset command creates an AdvFS fileset within an existing domain. There can be more than one fileset in a domain unless that fileset is enabled for the data management API (DMAPI). You can mount and unmount each fileset independently of the other filesets in the domain. You can assign fileset quotas (block and file usage limits) to filesets. A domain is not active until it has a mounted fileset. The mkfs command (HP-UX) The HP-UX mkfs command creates a file system; the file system type is specified with the -F option. The mount command (HP-UX and Tru64 UNIX) The mount command is used to mount a file system, that is, to attach a file system to a directory (a mountpoint) so that the files on the mounted file system can be accessed. The file systems are unmounted with the umount command. Using the mount command without any options or arguments displays the currently mounted file systems. The options for this command vary between both operating systems; for example, the -F option under the HP-UX operating system specifies the file system type; under Tru64 UNIX, the option is -t. See the appropriate reference page for more information. The mount_hfs and mount_vxfs commands (HP-UX) The mount_hfs and mount_vxfs commands are wrappers for the HP-UX mount command. They are used to mount an HFS file system and a VxFS file system, respectively. The newfs command (HP-UX and Tru64 UNIX) The newfs command is used to create a new file system on a disk. Specifically, the HP-UX version of this command creates an HFS or VxFS file system, as designated with the -F option, on a disk. The Tru64 UNIX version creates a UFS file system on either a whole disk or a disk partition. The options for this command differ from one operating system to the other. See the corresponding reference page for additional information. The newfs_hfs and newfs_vxfs commands (HP-UX) The newfs_hfs and newfs_vxfs commands are wrappers for the HP-UX newfs command. They create an HFS file system and a VxFS file system, respectively. The pfs_mount command (HP-UX) The pfs_mount command is used to mount a CD-ROM. Storage and File System Administration Commands and Utilities Chapter 13 290 The pv* commands (HP-UX) The following commands are available for LVM operations on physical volumes: pvchange Change characteristics and access path of physical volume in LVM volume group pvck Check or repair a physical volume in LVM volume group pvcreate Create physical volume for use in LVM volume group pvdisplay Display information about LVM physical volumes within LVM volume group pvmove Move allocated physical extents from one LVM physical volume to other physical volumes pvremove Remove LVM data structure from a physical volume The quotacheck command (HP-UX and Tru64 UNIX) The quotacheck command examines each of the specified file systems, building a table of current disk usage, then compares this table against the table stored in the disk quota file for the file system. Both the quota file and the current system copy of the incorrect quotas are updated if any inconsistencies are detected. The available options for this command differ between HP-UX and Tru64 UNIX. For example, the option to specify the file system type under HP-UX is -F; under Tru64 UNIX, the same capability requires the -t option. System Information utility (dxsysinfo) (Tru64 UNIX) Use the System Information graphical user interface, dxsysinfo, for the following tasks: • To obtain general information about the operating system and its version • To display the amount of RAM used, and number of CPUs • To monitor CPU activity, in-use memory, available swap space, and file system usage • To set and modify file system thresholds The swapon command (HP-UX and Tru64 UNIX) Under HP-UX, the swapon command enables devices or file systems on which paging is to take place; swap devices are listed in the /etc/fstab file. Under Tru64 UNIX, the swapon command is used to specify additional disk partitions for paging and swapping; swap partitions are specified in the /etc/sysconfigtab file. The swapinfo command (HP-UX) The swapinfo command displays information about device and file system paging space. The tunefs command (HP-UX and Tru64 UNIX) Use the tunefs command to alter dynamic parameters that affect the file system layout policies under HFS and UFS. The umount command (HP-UX and Tru64 UNIX) The umount command unmounts a file system. Storage and File System Administration Commands and Utilities Chapter 13 291 The vdf command (Tru64 UNIX) The vdf utility displays information about the disk usage of AdvFS file domains and filesets. In addition, the utility computes and displays the sizes of metadata files in a domain or fileset. The vg* commands (HP-UX) The following commands are available for LVM operations on volume groups: vgvcfgbackup Create or update LVM volume group configuration backup file vgvcfgrestore Display or restore LVM volume group configuration from backup file vgchange Set LVM volume group availability vgchgid Modify the Volume Group ID (VGID) on a given set of physical devices vgcreate Create LVM volume group vgdisplay Display information about LVM volume groups vgexport Export an LVM volume group and its associated logical volumes vgextend Extend an LVM volume group by adding physical volumes vgimport Import an LVM volume group onto the system vgreduce Remove physical volumes from an LVM volume group vgremove Remove LVM volume group definition from the system vgscan Scan physical volumes for LVM volume groups vgsync Synchronize stale logical volume mirrors in LVM volume groups The voldiskadm utility (Tru64 UNIX) The voldiskadm utility is an interactive tool that presents a menu of possible operations for LSM disk administration to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The vol* commands (Tru64 UNIX) The following commands are also available for LSM operations: volassist Interface to create, mirror, back up, grow, shrink, and move LSM volumes voldctl Controls the Logical Storage Manager volume configuration daemon voldg Manages Logical Storage Manager disk groups voldisk Defines and manages Logical Storage Manager disks voldiskadd Adds one or more disks for use with the Logical Storage Manager voldisksetup Sets up a disk for use with the Logical Storage Manager (LSM) voledit Creates, removes, and modifies Logical Storage Manager (LSM) records volencap, volreconfig Encapsulates disks, disk partitions, or AdvFS domains on a single system or a cluster, or the swap devices for one or more cluster members volevac Evacuates all volumes from a disk Storage and File System Administration Commands and Utilities Chapter 13 292 volinfo Print accessibility and usability of volumes volinstall Sets up Logical Storage Manager (LSM) environment after LSM installation voliod Starts, stops, and reports on Logical Storage Manager kernel I/O daemons vollogcnvt Logical Storage Manager BCL-to-DRL logging conversion utility volmake Create Logical Storage Manager objects volmend Mends simple problems in configuration records volmigrate, volunmigrate Moves AdvFS domain storage from physical storage to LSM volumes (volmigrate) or from LSM volumes to physical storage (volunmigrate) volmirror Mirrors volumes on a disk or control default mirroring volnotify Displays Logical Storage Manager configuration events volplex Perform Logical Storage Manager operations on plexes volprint Displays records from the Logical Storage Manager configuration volreattach Reattaches disk drives that have once again become accessible volrecover Performs volume recovery operations volrestore Restores a complete or partial Logical Storage Manager (LSM) configuration volrootmir Creates mirror of areas necessary for booting on a new disk volsave Saves a Logical Storage Manager (LSM) configuration volsd Perform Logical Storage Manager operations on subdisks volsetup, lsmsetup Initializes Logical Storage Manager (LSM) by creating the rootdg disk group volstat Logical Storage Manager statistics management utility voltrace Trace operations on volumes volume Performs Logical Storage Manager operations on volumes volunmigrate Moves AdvFS domain storage from LSM volumes to physical storage (volunmigrate) volunroot Remove Logical Storage Manager hooks for rootable volumes volwatch Monitors the Logical Storage Manager (LSM) for failure events and performs hot sparing The vxdiskadm command (HP-UX) The vxdiskadm command provides a menu-driven interface to perform common VxVM disk administration tasks. The vxdiskadm command is an interactive script that prompts you for responses and supplies default values where appropriate. The vxtunefs command (HP-UX) The vxtunefs commands sets or prints tunable I/O parameters of mounted file systems; this command can set parameters describing the I/O properties of the underlying device, the parameters to indicate when to treat an I/O as direct I/O, or the parameters to control the extent allocation policy for the specified file system. Storage and File System Administration Commands and Utilities Chapter 13 293 The vx* commands (HP-UX) The following commands are available for LVM operations: vxdiskusg Generate VxFS disk accounting data by user ID vxdump, rvxdump Incremental VxFS file system dump, local or across network vxenablef Enable VxFS DMAPI or OnLineJFS functionality in the kernel vxfsconvert Convert a file system to a VxFS file system vxlicense VxFS and VxVM licensing key utility vxrestore, rvxrestore Restore file system incrementally, local, or across network vxupgrade Upgrade the disk layout of a VxFS file system Storage and File System Administration Commands and Utilities Chapter 13 294 Chapter 14 295 14 System Startup and Shutdown The most basic operations for the System Administrator are the start up and the shut down of the operating system. This chapter discusses these operations and their associated topics. The processing of booting the operating system, either normally or interactively, differs between the operating systems; however, the run levels and methods for system shutdown are very similar. System Startup and Shutdown Normal Startup Chapter 14 296 Normal Startup This section describes the simplified system start-up procedures for both the HP-UX and Tru64 UNIX operating systems. These procedures differ between the HP-UX and Tru64 UNIX operating systems because they stem from the boot firmware, which was developed independently. HP-UX Automatic boot processes on various HP-UX systems follow a similar, general sequence. The normal start-up process from a cold start executes three software components: the Processor Dependent Code (PDC), which initiates the Initial System Loader (ISL), which in turn starts the hpux secondary system loader for bootstrap. Finally, the loaded image displays numerous configuration and status messages and passes control to the init process. At this point, the HP-UX init process reads the /etc/inittab file to complete initialization. Processor Dependent Code The Processor Dependent Code (PDC) is the firmware that implements all processor dependent functionality, including the initialization and self-test of the processor. The PDC is activated when the HP-UX system processor is powered on or when the system Reset button is pressed. This firmware gives the system administrator the option to override the autoboot sequence by pressing the Esc key. A message resembling the following usually appears on the console. (c) Copyright, Hewlett-Packard Company, All rights reserved. PDC ROM rev. xxx.x xx MB of memory configured and tested. Selecting a system to boot. To stop selection process, press and hold the ESCAPE key On completion, the PDC loads and transfers control to the Initial System Loader utility. See the pdc (1M) reference page for additional information. Initial System Loader utility The Initial System Loader utility (ISL) is the operating system independent portion of the bootstrap process on an HP system. It is loaded and executed after self-test and initialization have completed successfully. When control is transferred to the ISL, an autoboot sequence takes place, which allows a complete bootstrap operation to occur without intervention from the operator. While an auto-boot sequence occurs, ISL finds and executes the autoexecute file that requests that hpux, the next component, be run with the appropriate arguments. The console displays messages like the following: Booting from: scsi.x HP aaaa Hard booted. ISL Revision A.xx.xx date ISL booting hpux boot disk(;0)/stand/vmunix See the isl (1M) reference page for additional information. Secondary System Loader Utility, hpux The Secondary System Loader, hpux, displays the load image’s device file, as well as the TEXT size, DATA size, the BSS size, and start address of the load image before control passes to the image. Here is an example of the hpux output: System Startup and Shutdown Normal Startup Chapter 14 297 Booting disk(scsi.x;0)/stand/vmunix 966616+397312+409688 start 0x6c50 See the hpux (1M) reference page for additional information. The setboot utility The HP-UX operating system offers a utility that enables you to display and modify variables that influence the boot sequence, so that you do not need to bring the system down. These variables reside in an area of high-reliability memory called “stable storage.” This storage contains the boot path information along with other critical file system parameters even if the storage card is removed from the backplane. After the initial memory controller is initialized, the processor-dependent code (PDC) accesses stable storage to determine the boot device and console selection process; this information consists of the following: • the primary boot path • the alternate boot path • whether the autosearch sequence is enabled or disabled • whether the autoboot sequence is enabled or disabled. The setboot utility provides option flags for setting this information. To read the current values, enter the setboot utility without any options or parameters, as shown here: # setboot Primary bootpath : 10/0/15/0.6.0 Alternate bootpath : 10/0/14/0.0.0 Autoboot is ON (enabled) Autosearch is ON (enabled) See the setboot (1M) reference page for more information on this utility. Tru64 UNIX When a Tru64 UNIX system is turned on or restarted, the System Reference Manual (SRM) console is activated; this command interface is the first visible indication after the initial power-on tests complete successfully. The factory default action is to halt the system after the system after the system self-test and leave the console device in SRM console mode. Setting the auto_action SRM environment variable to the value boot allows you to continue booting the operating system using the default SRM parameters. Enter the following command at the SRM console prompt to determine the current setting of the auto_action SRM environment variable: >>> show auto_action The response indicates either halt or boot. Use the set SRM console command to change the setting as needed. You can change these settings with the consvar command after Tru64 UNIX has loaded. Enter the boot command to boot the operating system from the SRM console. The boot command shown in the following example boots the operating system to multi-user mode (using the A flag) from the file /vmunix on the default boot disk. >>>boot -flag A -file vmunix block 0 of dkb400.4.0.1.2 is a valid boot block reading xx blocks from dkb400.4.0.1.2 bootstrap code read in base - xxxxxx, image_start = 0, image_bytes = xxxx initializing HWRPB at xxxx System Startup and Shutdown Normal Startup Chapter 14 298 initializing page table at xxxxxxxx setting affinity to the primary CPU jumpstrap to bootstrap code . . . Tru64 UNIX Version Vx.x (system-name) console login: Using the boot command without any flags or parameters boots the system according to all the default parameters and the current settings of the SRM environment variables. The init process is spawned as the last part of the system boot. At this point, the Tru64 UNIX init process reads the /etc/inittab file to complete initialization. See the Firmware Reference Manual for your processor for more information on the SRM console commands and the boot sequence,. You can also find additional information in the Tru64 UNIX Hardware Management manual (released with Version 5.1B). The consvar utility The Tru64 UNIX consvar utility enables you to manipulate the firmware console environment variables from the operating system level. You can have the option of saving the SRM console environment variables in volatile memory with the -s option or in non-volatile memory with the -a option. The -l option enables you to list the current values of the console environment variables, as shown here; the -d option lists the system and exception database information. # consvar -l auto_action = BOOT boot_dev = dsk0 bootdef_dev = dsk0 booted_dev = dsk0 boot_file = booted_file = boot_osflags = A booted_osflags = A boot_reset = OFF enable_audit = ON license = MU char_set = language = 0x36 tty_dev = 0 com1_baud = 9600 com1_modem = OFF com1_flow = SOFTWARE com2_baud = 9600 com2_modem = OFF com2_flow = SOFTWARE secure = off logfail = 0 srm2dev_id = See the consvar (8) reference page for more information on this utility. [...]... Chapter 14 System Startup and Shutdown System Shutdown 2 Select the System Shutdown icon The System Shutdown dialog box opens 3 Select the appropriate options, then select OK Tru64 UNIX The Tru64 UNIX SysMan Menu also provides a graphical utility for shutting down the system 1 Select General Tasks from the SysMan Menu The General Tasks menu expands Chapter 14 305 System Startup and Shutdown System Shutdown... Definable 7 Definable Definable 8 Definable Definable 9 302 Halt Definable Definable Chapter 14 System Startup and Shutdown System Shutdown System Shutdown With both operating systems, you can use either the shutdown command or a graphical utility to shutdown the system The shutdown command (HP-UX and Tru64 UNIX) The shutdown commands for both operating systems are similar; the most often used options (-h... differences in the options to the command line for system shutdown are HP-UX Tru64 UNIX -h Shut down system and halt -h Shut down the system or cluster and halt -r Shut down the system and reboot -r Shut down the system and reboot -y Do not require any interactive responses -b Send shutdown message to the rwalld daemon on remote client hosts that have mounted NFS file systems -o In a diskless cluster environment,... of essential system processes; the file systems in /etc/fstab are mounted It can also be used to perform system administration tasks N/A 2 The operating mode is typically called "multi-user state" This mode allows all users to access the system Network and NFS client are enabled Multi-User Mode without Network Services 3 Multi-User Mode NFS and X Server enabled In this mode, NFS file systems can be... ISL>hpux -i2 • Booting another kernel, possibly with a modified configuration: ISL>hpux vmunix.trial • Booting from another section of the root disk Chapter 14 299 System Startup and Shutdown Interactive Boot • Booting from another disk ISL>hpux (2.0.0.0)/stand/vmunix • Booting from LAN: ISL>hpux lan(32)/stand/vmunix • Listing the contents of the /stand directory on the root disk: ISL>hpux ll /stand... UNIX system can be booted from a number of devices including a local system disk, a DVD/CD-ROM drive, a disk connected to the system through a CIPCA adapter, by Ethernet from a remote disk on a remote system, or a bootable tape When a Tru64 UNIX system is booted, the SRM console is activated Its factory default setting is to halt the system after its self-test and to remain in SRM console mode, which... to boot the operating system See the Firmware Reference manual for your processor for additional information on the SRM console Chapter 14 301 System Startup and Shutdown Run Levels Run Levels The following table illustrates the similarity of the HP-UX and Tru64 UNIX run levels Both operating systems allow the system administrator to define custom run levels Run Level HP-UX Tru64 UNIX 0 Halt S Single... Tru64 UNIX The HP-UX /sbin/sh is the POSIX shell, while the Tru64 UNIX /bin/sh is the Bourne shell Chapter 15 3 09 User and Group Account Administration User Accounts User Identifiers It is important to note that there are discrepancies between the operating systems in the assignment of user identifiers to group accounts Table 15-2 on page 310 shows the default user identifiers for the HP-UX and Tru64 UNIX. .. and Tru64 UNIX operating systems require information for a user account; Table 15-1 on page 3 09 summarizes this information When using a graphical user interface to create a new user account, the operating system may provide information based on the next available value or according to a default value or the values recorded in a template Table 15-1 User Account Data Data Item HP-UX Tru64 UNIX User... disk(scsi.x;0)/stand/vmunix xxxxxx+yyyyyy+zzzzzz start 0xnnnn Kernel Startup Messages Omitted INIT: Overriding default level with level ‘s’ INIT: SINGLE USER MODE WARNING: YOU ARE SUPERUSER!! # Usually the system administrator invokes the init utility with run level 2 or 3 to start multi-user mode See the Operator’s Guide for your processor for more information Tru64 UNIX A Tru64 UNIX system can be booted . command (HP-UX and Tru64 UNIX) The umount command unmounts a file system. Storage and File System Administration Commands and Utilities Chapter 13 291 The vdf command (Tru64 UNIX) The vdf utility. Here is an example of the hpux output: System Startup and Shutdown Normal Startup Chapter 14 297 Booting disk(scsi.x;0)/stand/vmunix 96 6616+ 397 312+4 096 88 start 0x6c50 See the hpux (1M) reference. /sbin/rc0d/K45syslog. System Startup and Shutdown System Shutdown Chapter 14 304 The Routine Tasks window opens. System Startup and Shutdown System Shutdown Chapter 14 305 2. Select the System Shutdown icon. The System