summaryrefslogtreecommitdiffstats
path: root/sys/geom/vinum/geom_vinum.c
Commit message (Collapse)AuthorAgeFilesLines
* Protect from creating striped and RAID5 plexes with unequally sizedle2006-03-301-10/+39
| | | | subdisks.
* Implement the 'resetconfig' command.le2006-03-231-0/+3
| | | | | PR: kern/94835 Submitted by: Ulf Lilleengen <lulf@stud.ntnu.no>
* Since we want a vinum geom created anytime the module loads, movele2005-11-241-133/+16
| | | | | | | | | | | the geom creation to a seperate init function and ignore the tasting. The config is now parsed only in the vinumdrive geom, which hopefully fixes the problem, that the drive class tasted before the vinum class had a chance, for good. Also restore the behaviour that the module can be loaded at boot time and on a running system.
* Finally bring in what was produced during Google SoC 2005:le2005-11-191-0/+6
| | | | | | | | | Add functions to rename objects and to move a subdisk from one drive to another. Obtained from: Chris Jones <chris.jones@ualberta.ca> Sponsored by: Google Summer of Code 2005 MFC in: 1 week
* Fix a stupid logic bug introduced in geom_vinum_drive.c rev 1.18:le2005-08-151-0/+2
| | | | | | | When a drive is newly created, it's state is initially set to 'down', so it won't allow saving the config to it (thus it will never know of itself being created). Work around this by adding a new flag, that's also checked when saving the config to a drive.
* Remove test for zero sectorsize when tasting. This check doesn'tle2005-03-071-3/+0
| | | | | | seem to be necessary anymore, and it prevents tasting a valid drive when booting with geom_vinum already loaded, since SCSI disks set their sectorsize not until first opening them.
* /* -> /*- for copyright notices, minor format tweaks as necessaryimp2005-01-061-1/+1
|
* Implement 'setstate' to allow setting the state of drives and subdisksle2004-11-261-0/+3
| | | | for debugging and emergency purposes.
* Implement checkparity/rebuildparity.le2004-11-261-0/+3
|
* Don't allow to create a drive that already exists.le2004-10-021-0/+8
|
* Read a whole sector instead of GV_HDR_LEN, since a sector might bele2004-09-131-1/+1
| | | | bigger (i.e. on CD-ROMs).
* Move config_new_drive() to the correct place and rename it tole2004-08-271-32/+1
| | | | gv_config_new_drive().
* Tag all geom classes in the tree with a version number.phk2004-08-081-0/+1
|
* Shut up the compiler and temporarily '#if 0' gv_destroy_geom(),le2004-07-291-0/+2
| | | | until we need it again.
* Use a temporary geom when tasting vinumdrives and lock the 'real'le2004-07-241-0/+4
| | | | | | | | | vinumdrive geom with an exclusive bit. This should fix the problem when underlying partitions overlap (i.e. the 'a' partition is at the same offset as the 'c' partition). Ideas borrowed from pjd@, quite a bit of testing by Matthias Schuendehuette <msch@snafu.de>.
* Disable kldunloading of geom_vinum temporarily until I figured outle2004-07-241-1/+1
| | | | how to do it correctly.
* g_clone_bio() can fail, be ready for this.pjd2004-07-051-2/+6
| | | | Approved by: le
* Mark a plex as 'newborn' when it is created. This is used to indicatele2004-06-251-0/+1
| | | | that new RAID5 plexes need to be initialized first.
* Currently, if the drives specified for volume creation arecsjp2004-06-241-2/+19
| | | | | | | | | | | | | | | | | not active GEOM providers, it will result in a kernel panic. If the GEOM provider or disk goes away before the volume configuration data gets written to the disk, it will result in another kernel panic. o Make sure that the drives specified for volume creation are active GEOM providers. o When writing out volume configuration data to associated drives, make sure that the GEOM provider is active, otherwise continue to the next drive in the volume. Approved by: le, bmilekic (mentor)
* Clean up allocated ressources when destroying the main vinum geom.le2004-06-181-2/+36
|
* Add a first version of a GEOMified vinum.le2004-06-121-0/+569
OpenPOWER on IntegriCloud