diff options
Diffstat (limited to 'usr/src/man/man7d')
| -rw-r--r-- | usr/src/man/man7d/Makefile | 5 | ||||
| -rw-r--r-- | usr/src/man/man7d/md.7d | 417 | ||||
| -rw-r--r-- | usr/src/man/man7d/mediator.7d | 253 |
3 files changed, 1 insertions, 674 deletions
diff --git a/usr/src/man/man7d/Makefile b/usr/src/man/man7d/Makefile index b7ded478a7..5e2b0dc5ad 100644 --- a/usr/src/man/man7d/Makefile +++ b/usr/src/man/man7d/Makefile @@ -11,11 +11,10 @@ # # Copyright 2011, Richard Lowe -# Copyright 2015 Nexenta Systems, Inc. All rights reserved. -# Copyright 2016 Joyent, Inc. # Copyright 2016 Garrett D'Amore <garrett@damore.org> # Copyright 2016 Joyent, Inc. # Copyright 2016 Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org> +# Copyright 2016 Nexenta Systems, Inc. # include $(SRC)/Makefile.master @@ -82,8 +81,6 @@ _MANFILES= aac.7d \ lockstat.7d \ lofi.7d \ log.7d \ - md.7d \ - mediator.7d \ mem.7d \ mpt_sas.7d \ mr_sas.7d \ diff --git a/usr/src/man/man7d/md.7d b/usr/src/man/man7d/md.7d deleted file mode 100644 index ecf4977ed4..0000000000 --- a/usr/src/man/man7d/md.7d +++ /dev/null @@ -1,417 +0,0 @@ -'\" te -.\" Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved -.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. -.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. -.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH MD 7D "Aug 29, 2003" -.SH NAME -md \- user configurable pseudo device driver -.SH DESCRIPTION -.sp -.LP -\fBmd\fR is a user configurable pseudo device driver that provides disk -concatenation, striping, mirroring, RAID5 metadevices, trans metadevices, and -hot spare utilities. Trans devices are no longer supported and have been -replaced by UFS logging. See \fBmount_ufs\fR(1M). -.sp -.LP -The block devices access the disk using the system's normal buffering mechanism -and are read and written without regard to physical disk records. There is also -a ``raw'' device which provides for direct transmission between the disk and -the user's read or write buffer. A single read or write call usually results in -one I/O operation; raw I/O is therefore considerably more efficient when many -bytes are transmitted. The names of the block devices are found in -\fB/dev/md/dsk\fR; the names of the raw devices are found in -\fB/dev/md/rdsk\fR. Metadevices have the appearance of whole disks; there are -no slices (partitions). -.sp -.LP -I/O requests (such as \fBlseek\fR(2)) to the metadevices must have an offset -that is a multiple of 512 bytes (DEV_BSIZE), or the driver returns an EINVAL -error. If the transfer length is not a multiple of 512 bytes, the tranfer count -is rounded up by the driver. -.sp -.LP -The \fBmd\fR pseudo device drivers support all disk devices on all Solaris 2.4 -or later Solaris systems. -.SH IOCTLS -.sp -.LP -This section provides a list of the ioctls supported by the metadisk driver. -.sp -.LP -The following ioctls are valid when issued to the raw metadevice, such as -\fB/dev/md/rdsk/d0\fR. See \fBdkio\fR(7I) for additional information. -.sp -.ne 2 -.na -\fB\fBDKIOCGGEOM\fR\fR -.ad -.RS 14n -This ioctl is used to get the disk geometry. The metadisk driver fills in the -\fBdkg_nhead\fR, \fBdkg_nsect\fR, \fBdkg_rpm\fR, \fBdkg_write_reinstruct\fR and -\fBdkg_read_reinstruct\fR from the first component of the metadevice (at -\fBmetainit\fR time). \fBdkg_ncyl\fR is calculated using the size of the -metadevice (reported by \fBmetastat\fR) divided by (dkg_nhead * dkg_nsect). The -total size is always a multiple of (dkg_nhead * dkg_nsect). If the first -component of a metadevice \fIdoes not\fR start on cylinder number 0, then the -dkg_ncyl is increased by one cylinder; because DKIOCGVTOC reports the -metadevice as starting on cylinder 1. The side effect here is that it looks -like cylinder 0 is not being used, but all the arithmetic works out correctly. -If the metadevice is not set up, then ENXIO is returned. -.RE - -.sp -.ne 2 -.na -\fB\fBDKIOCINFO\fR\fR -.ad -.RS 14n -When issued to the administrative device or metadevice, this ioctl sets -\fBdki_unit\fR to the unit number of the metadevice, \fBdki_ctype\fR to a value -of DKC_MD, and \fBdki_partition\fR to 0, because there are no slices. -.RE - -.sp -.ne 2 -.na -\fB\fBDKIOCGVTOC\fR\fR -.ad -.RS 14n -This ioctl returns the current vtoc. If one has not been written, then a -default vtoc is returned. \fBv_nparts\fR is always 1. \fBv_part[0].p_start\fR -is 0 if the first component of the metadevice starts on cylinder 0. Otherwise, -the \fBp_start\fR field is the starting sector of cylinder 1. -\fBv_part[0].p_size\fR is the same as the total size reported by -\fBmetastat\fR. -.RE - -.sp -.ne 2 -.na -\fB\fBDKIOCSVTOC\fR\fR -.ad -.RS 14n -This ioctl stores the vtoc in the metadevice state database so it is persistent -across reboots. -.RE - -.SH DIAGNOSTICS -.SS "Notice Log Messages" -.sp -.LP -The informative log messages include: -.sp -.in +2 -.nf -md: d\fInum\fR: Hotspared device \fIdev\fR with \fIdev\fR -.fi -.in -2 - -.sp -.LP -The first device name listed has been hot spare replaced with the second device -name listed. -.sp -.in +2 -.nf -md: d\fInum\fR: Hotspared device dev(\fInum\fR,\fInum\fR) with dev(\fInum\fR,\fInum\fR) -.fi -.in -2 - -.sp -.LP -The first device number listed has been hot spare replaced with the second -device number listed. -.sp -.in +2 -.nf -md: Could not load misc /\fIdev\fR -.fi -.in -2 - -.sp -.LP -The named \fBmisc\fR module is not loadable. It is possibly missing, or -something else has been copied over it. -.sp -.in +2 -.nf -md: d\fInum\fR: no mem for property \fIdev\fR -.fi -.in -2 - -.sp -.LP -Memory could not be allocated in the \fBprop_op\fR entry point. -.sp -.in +2 -.nf -md: db: Parsing error on '\fIdev\fR' - -.fi -.in -2 -.sp - -.sp -.LP -Set command in \fB/kernel/drv/md.conf\fR for the \fBmddb.bootlist\fR -\fI<number>\fR is not in the correct format. \fBmetadb\fR \fB-p\fR can be run -to put the correct set commands into the \fB/kernel/drv/md.conf\fR file. -.sp -.in +2 -.nf -md: d\fInum\fR: \fIdev\fR(\fInum\fR,\fInum\fR) needs maintenance -md: d\fInum\fR: \fIdev\fR needs maintenance -.fi -.in -2 - -.sp -.LP -An I/O or open error has occurred on a device within a mirror causing a -component in the mirror to change to the Maintenance state. -.sp -.LP -\fBmd: d\fR\fInum\fR\fB: \fR\fIdev\fR\fB(\fR\fInum\fR\fB,\fR\fInum\fR\fB) last -erred\fR \fBmd: d\fR\fInum\fR\fB: \fR\fIdev\fR\fB last erred\fR -.sp -.LP -An I/O or open error has occurred on a device within a mirror and the data is -not replicated elsewhere in the mirror. This is causing the component in the -mirror to change to the Last Erred state. -.SS "Warning Log Messages" -.sp -.LP -The warning log messages include: -.sp -.in +2 -.nf -md: State database is stale -.fi -.in -2 - -.sp -.LP -This error message comes when there are not enough usable replicas for the -state database to be able to update records in the database. All accesses to -the metadevice driver will fail. To fix this problem, more replicas need to be -added or inaccessible replicas need to be deleted. -.sp -.in +2 -.nf -md: d\fInum\fR: read error on \fIdev\fRmd: d\fInum\fR: write error on \fIdev\fR -.fi -.in -2 - -.sp -.LP -A read or write error has occurred on the specified submirror, at the specified -device name. This happens if any read or write errors occur on a submirror. -.sp -.in +2 -.nf -md: d\fInum\fR: read error on dev(\fInum\fR,\fInum\fR)md: d\fInum\fR: write error on dev( -\fInum\fR,\fInum\fR) -.fi -.in -2 - -.sp -.LP -A read or write error has occurred on the specified submirror, at the specified -device number. This happens if any read or write errors occur on a submirror. -.sp -.in +2 -.nf -md: State database commit failed -md: State database delete failed -.fi -.in -2 - -.sp -.LP -These messages occur when there have been device errors on components where the -state database replicas reside. These errors only occur when more than half of -the replicas have had device errors returned to them. For instance, if you have -three components with state database replicas and two of the components report -errors, then these errors may occur. The state database commit or delete is -retried periodically. If a replica is added, then the commit or delete will -finish and the system will be operational. Otherwise the system will timeout -and panic. -.sp -.in +2 -.nf -md: d\fInum\fR: Cannot load \fIdev\fR driver -.fi -.in -2 -.sp - -.sp -.LP -Underlying named driver module is not loadable (for example, \fBsd\fR, -\fBid\fR, \fBxy\fR, or a third-party driver). This could indicate that the -driver module has been removed. -.sp -.in +2 -.nf -md: Open error of hotspare \fIdev\fRmd: Open error of hotspare dev(\fInum\fR,\fInum\fR) -.fi -.in -2 - -.sp -.LP -Named hotspare is not openable, or underlying driver is not loadable. -.SS "Panic Log Messages" -.sp -.LP -The panic log messages include: -.sp -.in +2 -.nf -md: d\fInum\fR: Unknown close typemd: d\fInum\fR: Unknown open type -.fi -.in -2 - -.sp -.LP -Metadevice is being opened/closed with an unknown open type (OTYP). -.sp -.in +2 -.nf -md: State database problem -.fi -.in -2 - -.sp -.LP -Failed metadevice state database commit or delete has been retried the default -100 times. -.SH FILES -.sp -.ne 2 -.na -\fB\fB/dev/md/dsk/\fR\fBd\fIn\fR\fR \fR -.ad -.RS 30n -block device (where \fIn\fR is the device number) -.RE - -.sp -.ne 2 -.na -\fB\fB/dev/md/rdsk/\fR\fBd\fIn\fR\fR \fR -.ad -.RS 30n -raw device (where \fIn\fR is the device number) -.RE - -.sp -.ne 2 -.na -\fB\fB/dev/md/\fIsetname\fR/dsk/\fR\fBd\fIn\fR\fR \fR -.ad -.RS 30n -block device (where \fIsetname\fR is the name of the diskset and \fIn\fR is the -device number) -.RE - -.sp -.ne 2 -.na -\fB\fB/dev/md/\fIsetname\fR/rdsk/\fR\fBd\fIn\fR\fR \fR -.ad -.RS 30n -raw device (where \fIsetname\fR is the name of the diskset and \fIn\fR is the -device number) -.RE - -.sp -.ne 2 -.na -\fB\fB/dev/md/admin\fR \fR -.ad -.RS 30n -administrative device -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/drv/md\fR \fR -.ad -.RS 30n -driver module -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/drv/md.conf\fR \fR -.ad -.RS 30n -driver configuration file -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/misc/md_stripe\fR \fR -.ad -.RS 30n -stripe driver misc module -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/misc/md_mirror\fR \fR -.ad -.RS 30n -mirror driver misc module -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/misc/md_hotspares\fR \fR -.ad -.RS 30n -hotspares driver misc module -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/misc/md_trans\fR \fR -.ad -.RS 30n -metatrans driver for UFS logging -.RE - -.sp -.ne 2 -.na -\fB\fB/kernel/misc/md_raid\fR \fR -.ad -.RS 30n -RAID5 driver misc module -.RE - -.SH SEE ALSO -.sp -.LP -\fBmdmonitord\fR(1M), \fBmetaclear\fR(1M), \fBmetadb\fR(1M), -\fBmetadetach\fR(1M), \fBmetahs\fR(1M), \fBmetainit\fR(1M), -\fBmetaoffline\fR(1M), \fBmetaonline\fR(1M), \fBmetaparam\fR(1M), -\fBmetarecover\fR(1M), \fBmetarename\fR(1M), \fBmetareplace\fR(1M), -\fBmetaroot\fR(1M), \fBmetassist\fR(1M), \fBmetaset\fR(1M), \fBmetastat\fR(1M), -\fBmetasync\fR(1M), \fBmetattach\fR(1M), \fBmd.cf\fR(4), \fBmd.tab\fR(4), -\fBattributes\fR(5), -.sp -.LP -\fISolaris Volume Manager Administration Guide\fR -.SH NOTES -.sp -.LP -Trans metadevices have been replaced by UFS logging. Existing trans devices are -\fBnot\fR logging--they pass data directly through to the underlying device. -See \fBmount_ufs\fR(1M) for more information about UFS logging. diff --git a/usr/src/man/man7d/mediator.7d b/usr/src/man/man7d/mediator.7d deleted file mode 100644 index 5d2dcbbfd6..0000000000 --- a/usr/src/man/man7d/mediator.7d +++ /dev/null @@ -1,253 +0,0 @@ -'\" te -.\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved -.\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. -.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License. -.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner] -.TH MEDIATOR 7D "Jun 20, 2008" -.SH NAME -mediator \- support for HA configurations consisting of two strings of drives -.SH DESCRIPTION -.sp -.LP -Beginning with a prior version, Solaris Volume Manager provided support for -high-availability (HA) configurations consisting of two hosts that share at -least three strings of drives and that run software enabling exclusive access -to the data on those drives from one host. (Note: Volume Manager, by itself, -does not actually provide a high-availability environment. The diskset feature -is an enabler for HA configurations.) -.sp -.LP -Volume Manager provides support for a low-end HA solution consisting of two -hosts that share only two strings of drives. The hosts in this type of -configuration, referred to as \fImediators\fR, run a special daemon, -\fBrpc.metamedd\fR(1M). The mediator hosts take on additional responsibilities -to ensure that data is available in the case of host or drive failures. -.sp -.LP -In a mediator configuration, two hosts are physically connected to two strings -of drives. This configuration can survive the failure of a single host or a -single string of drives, without administrative intervention. If both a host -and a string of drives fail (multiple failures), the integrity of the data -cannot be guaranteed. At this point, administrative intervention is required to -make the data accessible. -.sp -.LP -The following definitions pertain to a mediator configuration: -.sp -.ne 2 -.na -\fB\fBdiskset\fR\fR -.ad -.sp .6 -.RS 4n -A set of drives containing metadevices and hot spares that can be shared -exclusively (but not concurrently) by two hosts. -.RE - -.sp -.ne 2 -.na -\fB\fBVolume Manager\fR \fBstate\fR \fBdatabase\fR\fR -.ad -.sp .6 -.RS 4n -A replicated database that stores metadevice configuration and state -information. -.RE - -.sp -.ne 2 -.na -\fB\fBmediator\fR \fBhost\fR\fR -.ad -.sp .6 -.RS 4n -A host that runs the \fBrpc.metamedd(1M)\fR daemon and that has been added to a -diskset. The mediator host participates in checking the state database and the -mediator quorum. -.RE - -.sp -.ne 2 -.na -\fB\fBmediator\fR \fBquorum\fR\fR -.ad -.sp .6 -.RS 4n -The condition achieved when the number of accessible mediator hosts is equal to -half+1 the total number of configured mediator hosts. Because it is expected -that there will be two mediator hosts, this number will normally be 2 ([(2/2) + -1] = 2.) -.RE - -.sp -.ne 2 -.na -\fB\fBreplica\fR\fR -.ad -.sp .6 -.RS 4n -A single copy of the Volume Manager metadevice state database. -.RE - -.sp -.ne 2 -.na -\fB\fBreplica\fR \fBquorum\fR\fR -.ad -.sp .6 -.RS 4n -The condition achieved when the number of accessible replicas is equal to -half+1 the total number of configured replicas. For example, if a system is -configured with ten replicas, the quorum is met when six are accessible -([(10/2) + 1 = 6]). -.RE - -.sp -.LP -A mediator host running the \fBrpc.metamedd(1M)\fR daemon keeps track of -replica updates. As long as the following conditions are met, access to data -occurs without any administrative intervention: -.RS +4 -.TP -.ie t \(bu -.el o -The replica quorum is not met. -.RE -.RS +4 -.TP -.ie t \(bu -.el o -Half of the replicas are still accessible. -.RE -.RS +4 -.TP -.ie t \(bu -.el o -The mediator quorum is met. -.RE -.sp -.LP -The following conditions describe the operation of mediator hosts: -.RS +4 -.TP -1. -If the is met, access to the diskset is granted. At this point no mediator -host is involved. -.RE -.RS +4 -.TP -2. -If the replica quorum is not met, half of the replicas are accessible, the -mediator quorum is met, and the replica and mediator data match, access to the -diskset is granted. The mediator host contributes the deciding vote. -.RE -.RS +4 -.TP -3. -If the replica quorum is not met, half of the replicas are accessible, the -mediator quorum is not met, half of the mediator hosts is accessible, and the -replica and mediator data match, the system prompts you to grant or deny access -to the diskset. -.RE -.RS +4 -.TP -4. -If the replica quorum is not met, half of the replicas are accessible, the -mediator quorum is met, and the replica and mediator data do not match, access -to the diskset is read-only. You can delete replicas, release the diskset, and -retake the diskset to gain read-write access to the data in the diskset. -.RE -.RS +4 -.TP -5. -In all other cases, the diskset access is read-only. You can delete -replicas, release the diskset, and retake the diskset to gain read-write access -to the data in the diskset. -.RE -.sp -.LP -The \fBmetaset\fR(1M) command administers disksets and mediator hosts. The -following options to the \fBmetaset\fR command pertain only to administering -mediator hosts. -.sp -.ne 2 -.na -\fB\fB-a\fR \fB-m\fR \fB\fImediator_host_list\fR\fR\fR -.ad -.RS 28n -Adds mediator hosts to the named set. A \fImediator_host_list\fR is the -nodename of the mediator host to be added and up to 2 other aliases for the -mediator host. The nodename and aliases for each mediator host are separated by -commas. Up to 3 mediator hosts can be specified for the named diskset. -.RE - -.sp -.ne 2 -.na -\fB\fB-d\fR \fB-m\fR \fB\fImediator_host_list\fR\fR\fR -.ad -.RS 28n -Deletes mediator hosts from the named diskset. Mediator hosts are deleted from -the diskset by specifying the nodename of mediator host to delete. -.RE - -.sp -.ne 2 -.na -\fB\fB-q\fR\fR -.ad -.RS 28n -Displays an enumerated list of tags pertaining to ``tagged data'' that may be -encountered during a take of the ownership of a diskset. -.RE - -.sp -.ne 2 -.na -\fB\fB-t\fR [\fB-f\fR] \fB-y\fR\fR -.ad -.RS 28n -Takes ownership of a diskset safely, unless \fB-f\fR is used, in which case the -take is unconditional. If \fBmetaset\fR finds that another host owns the set, -this host will not be allowed to take ownership of the set. If the set is not -owned by any other host, all the disks within the set will be owned by the -host on which \fBmetaset\fR was executed. The metadevice state database is -read in and the shared metadevices contained in the set become accessible. The -\fB-t\fR option will take a diskset that has stale databases. When the -databases are stale, \fBmetaset\fR will exit with code 66, and a message will -be printed. At that point, the only operations permitted are the addition and -deletion of replicas. Once the addition or deletion of the replicas has been -completed, the diskset should be released and retaken to gain full access to -the data. If mediator hosts have been configured, some additional exit codes -are possible. If half of the replicas and half of the mediator hosts are -operating properly, the take will exit with code 3. At this point, you can add -or delete replicas, or use the \fB-y\fR option on a subsequent take. If the -take operation encounters ``tagged data,'' the take operation will exit with -code 2. You can then run the \fBmetaset\fR command with the \fB-q\fR option to -see an enumerated list of tags. -.RE - -.sp -.ne 2 -.na -\fB\fB-t\fR [\fB-f\fR] \fB-u\fR \fItagnumber\fR\fR -.ad -.RS 28n -Once a tag has been selected, a subsequent take with \fB-u\fR -\fB\fItagnumber\fR\fR can be executed to select the data associated with the -given \fItagnumber\fR. -.RE - -.SH SEE ALSO -.sp -.LP -\fBmetaset\fR(1M), \fBmd\fR(7D), \fBrpc.metamedd\fR(1M), \fBrpc.metad\fR(1M) -.sp -.LP -Sun Cluster documentation, \fISolaris Volume Manager Administration Guide\fR -.SH NOTES -.sp -.LP -Diskset administration, including the addition and deletion of hosts and -drives, requires all hosts in the set to be accessible from the network. |