summaryrefslogtreecommitdiffstats
path: root/sys/geom/raid3
Commit message (Collapse)AuthorAgeFilesLines
* Fix typo which cased that 64kB elements limit was not set properly andpjd2006-01-301-1/+1
| | | | | | | 16kB elements limit wasn't set at all. Submitted by: Vsevolod Lobko <seva@ip.net.ua> MFC after: 3 days
* Remove dead code.pjd2006-01-181-2/+0
| | | | | | Found by: Coverity Prevent(tm) Coverity ID: CID105 MFC after: 3 days
* Check for g_read_data(9) errors properly:sobomax2005-11-301-1/+1
| | | | | | | | | | o The only indication of error condition is NULL value returned by the function; o value pointed to by error argument is undefined in the case when operation completes successfully. Discussed with: phk
* Normalize a significant number of kernel malloc type names:rwatson2005-10-311-1/+1
| | | | | | | | | | | | | | | | | | | - Prefer '_' to ' ', as it results in more easily parsed results in memory monitoring tools such as vmstat. - Remove punctuation that is incompatible with using memory type names as file names, such as '/' characters. - Disambiguate some collisions by adding subsystem prefixes to some memory types. - Generally prefer lower case to upper case. - If the same type is defined in multiple architecture directories, attempt to use the same name in additional cases. Not all instances were caught in this change, so more work is required to finish this conversion. Similar changes are required for UMA zone names.
* Fix possible live-lock under heavy load where we can't allocate morepjd2005-10-281-1/+12
| | | | | | | | memory for request. I was sure graid3 should handle such situations well, but green@ reported it is not and we want to fix it before 6.0. Submitted by: green
* Use root_mount KPI for RAID3 to delay root file system mount.pjd2005-07-272-0/+28
| | | | | | | | | Actually, one cannot setup root file system on RAID3 device, but when other file system exist in /etc/fstab which are placed on RAID3 device, boot process will be interrupted when these devices are missing. MFC after: 3 days X-MFC-note: MFC only to RELENG_6, as RELENG_5 doesn't have root_mount KPI.
* cp can't be NULL.pjd2005-05-111-7/+5
| | | | Noticed by: Coverity Prevent analysis tool
* gp can't be NULL.pjd2005-05-111-10/+8
| | | | Noticed by: Coverity Prevent analysis tool
* If an error occurs, clean up before returning from g_raid3_connect_disk().pjd2005-03-261-14/+17
|
* Check for return values.pjd2005-03-261-0/+8
| | | | | Submitted by: sam Found by: Coverity Prevent analysis tool
* - Add md_provsize field to metadata, which will help withpjd2005-02-272-9/+59
| | | | | | | | | | | | | | | | | shared-last-sector problem. After this change, even if there is more than one provider with the same last sector, the proper one will be chosen based on its size. It still doesn't fix the 'c' partition problem (when da0s1 can be confused with da0s1c) and situation when 'a' partition starts at offset 0 (then da0s1a can be confused with da0s1 and da0s1c). One can use '-h' option there, when creating device or avoid sharing last sector. Actually, when providers share the same last sector and their size is equal, they provide exactly the same data, so the name (da0s1, da0s1a, da0s1c) isn't important at all. - Provide backward compatibility. - Update copyright's year. MFC after: 1 week
* Update copyright in files changed this year.pjd2005-02-163-3/+3
|
* Increase default synchronization speed.pjd2005-01-091-1/+1
| | | | MFC after: 3 days
* - Fix 'rebuild' command - it can no longer relay on retaste eventpjd2005-01-043-50/+34
| | | | | | | | (we ignore it). - Remove code used for handling spoil events, as spoiling is not possible anymore, because we keep consumers open for writing all the time. MFC after: 4 days
* Remove unused #include.pjd2005-01-031-1/+0
|
* Stop explicitly touching td_base_pri outside of the scheduler and simplyjhb2004-12-301-1/+4
| | | | | set a thread's priority via sched_prio() when that is the desired action. The schedulers will start managing td_base_pri internally shortly.
* Remove debug code.pjd2004-12-281-10/+2
|
* - Add genid field to the metadata which will allow to improve reliability a bit.pjd2004-12-253-61/+206
| | | | | | | | | | | | | | | 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. - Implement backward compatibility mechanism. After this change when metadata in old version is detected, it is automatically upgraded to the new (current) version.
* Now, when force device destruction is done on shutdown, hide warning,pjd2004-12-211-1/+1
| | | | | | that device cannot be destroyed immediately, under debug=1. Suggested by: simon
* Improve reliability and clean up code a bit.pjd2004-12-211-189/+140
| | | | For more details check src/sys/geom/mirror/g_mirror.c rev.1.47,1.48,1.49,1.50.
* bioq_insert_head() function is already in subr_disk.c.pjd2004-12-131-10/+0
|
* When initializing device, set d_softc and d_no fields for all components,pjd2004-12-041-3/+4
| | | | | | | | because we know it then and we need it when inserting a component which wasn't destroyed while device was running. Reported by: Michael Handler <handler@grendel.net> MFC after: 1 week
* Before trying to update metadata (so open consumer for writing), be surepjd2004-11-091-11/+26
| | | | | | | | | | that the events queue is empty. In other case we're able to hit the race where for example da0s1 is tasted by some other class, which means that da0 is open with exclusive bit set, which means that we can't open da0 for writing if it is our component. Reported by: Attila Nagy <bra@fsn.hu> (and somebody else sometime ago, but I cannot find who it was)
* Don't rely on DIRTY flag to be sure that consumer if open, becausepjd2004-11-091-1/+1
| | | | | DIRTY flag can be removed in idle process. Use consumer's acw field instead to avoid opening consumer twice.
* For BIO_READ check if provider is open for reading and for BIO_WRITE,pjd2004-11-091-3/+11
| | | | | | check if provider is open for writing. This fixes panic when device is open only for writing and we send write request.
* Drop Giant lock before grabbing the topology lock.pjd2004-11-091-0/+2
|
* If device is marked as beeing destroyed, deny all access requests.pjd2004-11-081-1/+2
|
* Don't forget to make sure that there are no not-finished requests beforepjd2004-11-051-14/+33
| | | | | | marking components as clean. Pointed out by: scottl
* - Mark all raid3 components as clean after kern.geom.raid3.idletime seconds.pjd2004-11-052-2/+82
| | | | - Make kern.geom.raid3.timeout variable tunable.
* Mark raid3 devices as clean on shutdown (after all file systems arepjd2004-11-051-3/+52
| | | | | | unmounted). Suggested by: scottl
* - Use ->index consumer's field to track number of in-flight requests.pjd2004-11-051-2/+10
| | | | - Remove unused #include.
* Just use MAXPHYS as maximum I/O request size, instead of using my ownpjd2004-09-282-8/+4
| | | | | #define for this purpose. No functional change.
* Decrease kern.geom.raid3.timeout to 4, so it is smaller thanpjd2004-09-271-1/+1
| | | | vfs.root.mountdelay by default.
* Avoid race while synchronizing components. It is very hard to bump into,pjd2004-09-272-7/+37
| | | | | | | | | but it is possible: 1. Read data from good component for synchronization. 2. Write data to the same area. 3. Write synchronization data, which are now stale. Found by: tegge (for gmirror)
* This is not needed anymore, it is forced in GEOM now.pjd2004-09-201-3/+0
| | | | | | | | | Actually, it can even cause some problems, because GEOM requires sectorsize to be more than 0 on first access, not on provider creation, so we can skip valid providers by doing this check here. Reported by: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Sven Willenberger <sven@dmv.com>
* Allow to configure debug level from /boot/loader.conf.pjd2004-08-301-0/+1
|
* GCC, ehh.pjd2004-08-291-0/+1
|
* Use sc->sc_mediasize instead of sc->sc_provider->mediasize which containspjd2004-08-281-4/+3
| | | | exactly the same value, but is shorter.
* Warn the user if we are not going to use whole provider space.pjd2004-08-281-4/+12
| | | | Requested by: Michael Handler <handler@grendel.net>
* Don't allow to insert providers, which are too small.pjd2004-08-281-0/+4
| | | | Reported by: Michael Handler <handler@grendel.net>
* Skip providers with not defined sector size.pjd2004-08-261-0/+3
| | | | Reported by: kuriyama
* Log verification errors at level 1.pjd2004-08-251-2/+6
|
* Implementation of 'verify reading' algorithm, which uses parity data forpjd2004-08-223-18/+163
| | | | | | | | verification of regular data when device is in complete state. On verification error, EIO error is returned for the bio and sysctl kern.geom.raid3.stat.parity_mismatch is increased. Suggested by: phk
* Add version history.pjd2004-08-211-0/+5
|
* Implement new reading algorithm, which will use parity component for readingpjd2004-08-213-102/+143
| | | | | | | | | | | | | | | | | | | | | | | | as well, even if device is in complete state. I observe 40% of speed-up with this option for random read operations, but slowdown for sequential reads. Basically, without this option reading from a RAID3 device built from 5 components (c0-c4) looks like this: Request no. Used components 1 c0+c1+c2+c3 2 c0+c1+c2+c3 3 c0+c1+c2+c3 With the new feature: Request no. Used components 1 c0+c1+c2+c3 2 (c1^c2^c3^c4)+c1+c2+c3 3 c0+(c0^c2^c3^c4)+c2+c3 4 c0+c1+(c0^c1^c3^c4)+c3 5 c0+c1+c2+(c0^c1^c2^c4) 6 c0+c1+c2+c3 [...]
* We really don't want to receive spoil event for synchroniztion consumers.pjd2004-08-181-1/+0
|
* Dump device status on 'list' command.pjd2004-08-181-0/+2
|
* Minor style.9 cleanup.obrien2004-08-161-3/+4
|
* Decrease debug level to 0.pjd2004-08-161-1/+1
|
* Fix warning.pjd2004-08-161-1/+1
|
OpenPOWER on IntegriCloud