summaryrefslogtreecommitdiffstats
path: root/sys/geom/mirror/g_mirror_ctl.c
Commit message (Collapse)AuthorAgeFilesLines
* Now, that we have gjournal in the tree add possibility to configurepjd2006-11-011-2/+30
| | | | | | gmirror and graid3 in a way that it is not resynchronized after a power failure or system crash. It is safe when gjournal is running on top of gmirror/graid3.
* Always allow to specify components with /dev/ prefix.pjd2006-07-131-2/+4
| | | | MFC after: 3 days
* Introduce and use delayed-destruction functionality from a pre-sync hook,pjd2006-04-101-1/+7
| | | | | | | | | | which means that devices will be destroyed on last close. This fixes destruction order problems when, eg. RAID3 array is build on top of RAID1 arrays. Requested, reviewed and tested by: ru MFC after: 2 weeks
* Update copyright for 2006.pjd2006-03-191-1/+1
|
* - Speed up synchronization process by using configurable number of I/Opjd2006-03-131-49/+69
| | | | | | | | | | | | | | | requests in parallel. + Add kern.geom.mirror.sync_requests tunable which defines how many parallel I/O requests should be used. + Retire kern.geom.mirror.reqs_per_sync and kern.geom.mirror.syncs_per_sec sysctls. - Fix race between regular and synchronization requests. - Reimplement mirror's data synchronization - do not use the topology lock for this purpose, as it may case deadlocks. - Stop synchronization from pre-sync hook. - Fix some other minor issues. MFC after: 3 days
* When inserting a new component md_provsize metadata field wasn't set, whichpjd2006-03-101-0/+1
| | | | | | | | means that old problem was triggered (when two providers end at the same offset, eg. ad0 and ad0s1 and the wrong was is picked up by gmirror/graid3). Reported by: Michal Suszko <dry@dry.pl> MFC after: 3 days
* Remove trailing spaces.pjd2006-02-011-1/+1
|
* Fix provider's size check for 'insert' command.pjd2005-04-251-1/+2
| | | | | | Before this fix one was able to insert one sector too small provider. MFC after: 3 days
* Check for return values.pjd2005-03-261-0/+12
| | | | | Submitted by: sam Found by: Coverity Prevent analysis tool
* Update copyright in files changed this year.pjd2005-02-161-1/+1
|
* Spoiling is now not possible, because we keep consumers open for writingpjd2005-01-041-1/+1
| | | | | | all the time. Remove unused code then. MFC after: 4 days
* Fix 'rebuild' command (we ignore retaste event now, so don't relay on it).pjd2005-01-031-9/+18
|
* - Add genid field to the metadata which will allow to improve reliability a bit.pjd2004-12-221-1/+1
| | | | | | | | | | | | | | | | After this change, when component is disconnected because of an I/O error, it will not be connected and synchronized automatically, it will be logged as broken and skipped. Autosynchronization can occur, when component is disconnected (on orphan event) and connected again - there were no I/O error, so there is no need to not connected the component, but when there were writes while it wasn't connected, it will be synchronized. This fix cases, when component is disconnected because of I/O error and can be connected again and again. - Bump version number. - Add version change history. - Implement backward compatibility mechanism. After this change when metadata in old version is detected, it is automatically upgraded to the new (current) version.
* Don't quit on first failure, just skip failures.pjd2004-12-191-6/+6
|
* Forgot to commit those: introduce hardcoded provider functionality,pjd2004-08-101-3/+33
| | | | | which allow to store provider's name in the metadata and avoid problems when few providers share the same last sector.
* Add '-p' option for 'insert' command which allows to specify prioritypjd2004-07-311-0/+7
| | | | | | of the new component. Version number wasn't bumped (it should be), because I think there are no geom_mirror users yet.
* - Check if 'slice' argument was given.pjd2004-07-311-0/+8
| | | | - Check if disk isn't already the mirror component.
* Add GEOM_MIRROR class which provide RAID1 functionality and has many usefulpjd2004-07-301-0/+617
features. The gmirror(8) utility should be used for control of this class. There is no manual page yet, but I'm working on it with keramida@. Many useful tests provided by: simon (thank you!) Some ideas from: scottl, simon, phk
OpenPOWER on IntegriCloud