Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

metaroot(1m) [debian man page]

metaroot(1M)															      metaroot(1M)

NAME
metaroot - setup system files for root (/) metadevice SYNOPSIS
/usr/sbin/metaroot -h /usr/sbin/metaroot [-n] [-k system-name] [-v vfstab-name] [-c mddb.cf-name] [-m md.conf-name] [-R root-path] device The metaroot command edits the /etc/vfstab and /etc/system files so that the system may be booted with the root file system (/) on an appropriate metadevice. The only metadevices that support the root file system are a stripe with only a single slice or a mirror on a sin- gle-slice stripe. If necessary, the metaroot command can reset a system that has been configured to boot the root file system (/) on a metadevice so that it uses a physical slice. Root privileges are required for all of the following options except -h. The following options are supported: -c mddb.cf-name Use mddb.cf-name instead of the default /etc/lvm/mddb.cf file as a source of metadevice database locations. -h Display a usage message. -k system-name Edit a user-supplied system-name instead of the default /etc/system system configuration information file. -m md.conf-name Edit the configuration file specified by md.conf-name rather than the default, /kernel/drv/md.conf. -n Print what would be done without actually doing it. -R root-path When metaroot modifies system files, it accesses them in their relative location under root-path. The -R option cannot be used in combination with the -c, -k,-m, or -v options. Note - The root file system of any non-global zones must not be referenced with the -R option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -v vfstab-name Edit vfstab-name instead of the default /etc/vfstab table of file system defaults. The following operands are supported: device Specifies either the metadevice or the conventional disk device (slice) used for the root file system (/). Example 1: Specifying Root File System on Metadevice The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on metadevice d0. # metaroot d0 Example 2: Specifying Root File System on SCSI Disk The following command edits /etc/system and /etc/vfstab to specify that the root file system is now on the SCSI disk device /dev/dsk/c0t3d0s0. # metaroot /dev/dsk/c0t3d0s0 /etc/system System configuration information file. See system(4). /etc/vfstab File system defaults. /etc/lvm/mddb.cf Metadevice state database locations. /kernel/drv/md.conf Configuration file for the metadevice driver, md. The following exit values are returned: 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) 6 Apr 2005 metaroot(1M)

Check Out this Related Man Page

mddb.cf(4)							   File Formats 							mddb.cf(4)

NAME
mddb.cf - metadevice state database replica locations SYNOPSIS
/etc/lvm/mddb.cf DESCRIPTION
The /etc/lvm/mddb.cf file is created when the metadb(1M) command is invoked. You should never directly edit this file. The file /etc/lvm/mddb.cf is used by the metainit(1M) command to find the locations of the metadevice state databases replicas. The metadb command creates the file and updates it each time it is run. Similar information is entered in the /kernel/drv/md.conf file. Each metadevice state database replica has a unique entry in the /etc/lvm/mddb.cf file. Each entry contains the driver and minor unit num- bers associated with the block physical device where a replica is stored. Each entry also contains the block number of the master block, which contains a list of all other blocks in the replica. Entries in the /etc/lvm/mddb.cf file are of the form: driver_name minor_t daddr_t checksum where driver_name and minor_t represent the device number of the physical device storing this replica. daddr_t is the disk block address. checksum is used to make certain the entry has not been corrupted. A pound sign (#) introduces a comment. EXAMPLES
Example 1: Sample File The following example shows a mddb.cf file. #metadevice database location file do not hand edit #driver minor_t daddr_t device id checksum sd 152 16 id1,sd@SSEAGATE_JDD288110MC9LH/a -2613 In the example above, the value for daddr_t indicates that the offset from the start of a given partition is 16 disk blocks from the start of that partition. FILES
/etc/lvm/mddb.cf /kernel/drv/md.conf SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metassist(1M), metaset(1M), metastat(1M), metasync(1M), metattach(1M), md.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide SunOS 5.10 8 Aug 2003 mddb.cf(4)
Man Page