summaryrefslogtreecommitdiffstats
path: root/sbin/geom/class/multipath
Commit message (Collapse)AuthorAgeFilesLines
* Some improvements to GEOM MULTIPATH:mav2012-04-182-8/+45
| | | | | | | | | | | | | | | | - Implement "configure" command to allow switching operation mode of running device on-fly without destroying and recreation. - Implement Active/Read mode as hybrid of Active/Active and Active/Passive. In this mode all paths not marked FAIL may handle reads same time, but unlike Active/Active only one path handles write requests at any point in time. It allows to closer follow original write request order if above layers need it for data consistency (not waiting for requisite write completion before sending dependent write). - Hide duplicate messages about device status change. - Remove periodic thread wake up with 10Hz rate. MFC after: 2 weeks Sponsored by: iXsystems, Inc.
* Remove superfluous paragraph macro.joel2012-03-251-2/+0
|
* Fix build on some archs after r227464.mav2011-11-121-3/+4
|
* Fix buildworld breakage due after r227464.dim2011-11-121-1/+1
| | | | Pointy hat to: mav
* Major GEOM MULTIPATH class rewrite:mav2011-11-122-98/+194
| | | | | | | | | | | | | | | | | | | | | | | | | - Improved locking and destruction process to fix crashes. - Improved "automatic" configuration method to make it consistent and safe by reading metadata back from all specified paths after writing to one. - Added provider size check to reduce chance of ordering conflict with other GEOM classes. - Added "manual" configuration method without using on-disk metadata. - Added "add" and "remove" commands to allow manage paths manually. - Failed paths are no longer dropped from geom, but only marked as FAIL and excluded from I/O operations. - Automatically restore failed paths when all others paths are marked as failed, for example, because of device-caused (not transport) errors. - Added "fail" and "restore" commands to manually control FAIL flag. - geom is now destroyed on last path disconnection. - Added optional Active/Active mode support. Unlike Active/Passive mode, load evenly distributed between all working paths. If supported by the device, it allows to significantly improve performance, utilizing bandwidth of all paths. It is controlled by -A option during creation. Disabled by default now. - Improved `status` and `list` commands output. Sponsored by: iXsystems, inc. MFC after: 1 month
* Rename the generic "CLASS" to the more specific "GEOM_CLASS".obrien2010-12-151-2/+3
| | | | | | While I'm here remove redundancy and inconsistencies. Obtained from: Juniper Networks
* - Remove gc_argname field. It was introduced for gpart(8), but if Ipjd2010-09-131-6/+6
| | | | | | | understand everything correctly, we don't really need it. - Provide default numeric value as strings. This allows to simplify a lot of code. - Bump version number.
* Avoid a memory leak.mjacob2010-08-131-10/+10
| | | | | Submitted by: Dmitry Luhtionov via Alexander Motin MFC after: 1 week
* Fix the clear function which has been broken for a bit.mjacob2010-07-041-6/+17
| | | | MFC after: 1 week
* Change how multipath labels are created and managed. This makes it easiermjacob2010-03-291-45/+51
| | | | | | | | | | | | | | | | | to support various storage boxes which really aren't active-active. We only write the label on the *first* provider. For all other providers we just "add" the disk. This also allows for an "add" verb. A usage implication is that you should specificy the currently active storage path as the first provider. Note that this does not add RDAC-like functionality, but better allows for autovolumefailover configurations (additional checkins elsewhere will support this). Sponsored by: Panasas MFC after: 1 month
* Add 'rotate' and 'getactive' verbs to provide some control and informationmjacob2010-03-211-0/+8
| | | | | | | about what the currently active path is. Sponsored by: Panasas MFC after: 1 month
* Add the long missing "destroy" option.mjacob2010-02-041-0/+4
| | | | MFC after: 2 weeks
* - Use an uppercase provider name in the example, to make the name changebrueffer2008-03-131-7/+7
| | | | | | | | | after labeling the provider more obvious. (1) - Correct nomenclature usage PR: 121487 (1) Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com> MFC after: 3 days
* Fix typos.brueffer2008-03-081-2/+2
| | | | | | PR: 121486 Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com> MFC after: 3 days
* Add gpart(8).marcel2007-05-151-2/+2
| | | | | | | In order to support gpart(8), geom(8) needs to support a named argument. Also, optional string parameters are a requirement. Both have been added to the infrastructure. The former required all existing classes to be adjusted.
* Fix mdoc warnings.pjd2007-05-061-3/+1
|
* Call the multipath device with its real name.ale2007-02-271-1/+1
|
* First cleanup pass: new sentence -> new line, typos fixed, some markupbrueffer2007-02-271-26/+41
| | | | errors fixed.
* Add a man page.mjacob2007-02-272-2/+250
|
* First cut at GEOM based multipath. This is an active/passive{/passive...}mjacob2007-02-272-0/+240
arrangement that has no intrinsic internal knowledge of whether devices it is given are truly multipath devices. As such, this is a simplistic approach, but still a useful one. The basic approach is to (at present- this will change soon) use camcontrol to find likely identical devices and and label the trailing sector of the first one. This label contains both a full UUID and a name. The name is what is presented in /dev/multipath, but the UUID is used as a true distinguishor at g_taste time, thus making sure we don't have chaos on a shared SAN where everyone names their data multipath as "Fred". The first of N identical devices (and N *may* be 1!) becomes the active path until a BIO request is failed with EIO or ENXIO. When this occurs, the active disk is ripped away and the next in a list is picked to (retry and) continue with. During g_taste events new disks that meet the match criteria for existing multipath geoms get added to the tail end of the list. Thus, this active/passive setup actually does work for devices which go away and come back, as do (now) mpt(4) and isp(4) SAN based disks. There is still a lot to do to improve this- like about 5 of the 12 recommendations I've received about it, but it's been functional enough for a while that it deserves a broader test base. Reviewed by: pjd Sponsored by: IronPort Systems MFC: 2 months
OpenPOWER on IntegriCloud