summaryrefslogtreecommitdiffstats
path: root/sys/geom
Commit message (Collapse)AuthorAgeFilesLines
...
* Implement the 'resetconfig' command.le2006-03-233-0/+43
| | | | | PR: kern/94835 Submitted by: Ulf Lilleengen <lulf@stud.ntnu.no>
* Update copyright for 2006.pjd2006-03-195-5/+5
|
* kern.geom.raid3.sync_requests=2 seems to be a better default - it stillpjd2006-03-191-3/+3
| | | | | | keeps disks very busy, but makes system much more responsive. While here, kill extra space.
* kern.geom.mirror.sync_requests=2 seems to be a better default - it stillpjd2006-03-191-2/+2
| | | | | | keeps disks very busy, but makes system much more responsive. While here, kill extra space.
* Fix a typo.ru2006-03-131-1/+1
|
* Fix build on 64-bit platforms.ru2006-03-132-4/+4
|
* - Reimplement I/O data allocation to prevent deadlocks.pjd2006-03-133-352/+672
| | | | | | | | | | | | | | | | | | | Submitted by: green - Speed up synchronization process by using configurable number of I/O requests in parallel. + Add kern.geom.raid3.sync_requests tunable which defines how many parallel I/O requests should be used. + Retire kern.geom.raid3.reqs_per_sync and kern.geom.raid3.syncs_per_sec sysctls. - Fix race between regular and synchronization requests. - Reimplement raid3'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. Tested by: Mike Tancsa <mike@sentex.net> MFC after: 3 days
* - Speed up synchronization process by using configurable number of I/Opjd2006-03-133-274/+559
| | | | | | | | | | | | | | | 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-102-0/+2
| | | | | | | | 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
* Allow to dump kernel to gmirror providers.pjd2006-03-081-0/+37
| | | | | | | Some conditions have to be met to make it work properly. This will be described in the manual page. MFC after: 3 days
* We need to check if file system size is equal to provider's size, becausepjd2006-03-041-2/+7
| | | | | | | | | | | | sysinstall(8) still bogusly puts first partition at offset 0 instead of 16, so glabel/ufs will find file system on slice instead of partition. Before sysinstall is fixed, we must keep this code, which means that we wont't be able to detect UFS file systems created with 'newfs -s ...'. PS. bsdlabel(8) creates partitions properly. MFC after: 3 days
* - Lock Giant if needed around the call to vnode_create_vobject(). This isjeff2006-03-021-0/+3
| | | | | | | only important if devfs is not mpsafe. Sponsored by: Isilon Systems, Inc. Found by: kris
* Assert proper use of bio_caller1, bio_caller2, bio_cflags, bio_driver1,pjd2006-03-011-0/+23
| | | | | | bio_driver2 and bio_pflags fields. Reviewed by: phk
* Do not use bio structure after g_io_deliver(), it may not longer by valid.pjd2006-02-221-1/+1
| | | | | Found and fixed by: Vsevolod Lobko <seva@ip.net.ua> MFC after: 3 days
* Inform when label disappears.pjd2006-02-181-16/+36
| | | | MFC after: 3 days
* Allow to use g_slice_orphan() from outside.pjd2006-02-182-2/+2
| | | | MFC after: 3 days
* - Do not depend on fact that file system covers entire provider.pjd2006-02-181-19/+13
| | | | | | | | It won't work for file systems created with -s option. Use better file system verfication. - Add myself to the copyright. MFC after: 3 days
* This function returns nothing.pjd2006-02-181-1/+1
|
* If provider's sector size prevents reading SBLOCKSIZE bytes returnpjd2006-02-181-8/+10
| | | | immediatelly.
* On component state change to ACTIVE don't forget to update metadata.pjd2006-02-122-6/+4
| | | | MFC after: 3 days
* Use time_uptime instead of time_second, as the latter may go backwards.pjd2006-02-122-8/+8
| | | | | Suggested by: ru MFC after: 3 days
* Allow to set kern.geom.raid3.disconnect_on_failure from loader.conf.pjd2006-02-121-0/+2
| | | | MFC after: 3 days
* - Add kern.geom.raid3.disconnect_on_failure sysctl/tunnable (default to 1pjd2006-02-112-31/+76
| | | | | | | | | | | | | | | to preserve currect behaviour). When set to 0, components are not disconnected - graid3 will try to still use them (only first error will be logged). This is helpful when we have two broken components, but in different places, so actually all data is available. Such buggy component will be visible in 'graid3 list' output with flag BROKEN. - Never disconnect the last valid component. If we detect errors there we will just pass them up. This wasn't reasonable to deny access to the whole provider because of one broken sector. Prodded by: ru MFC after: 3 days
* - Add kern.geom.mirror.disconnect_on_failure sysctl/tunnable (default to 1pjd2006-02-112-10/+47
| | | | | | | | | | | | | | | to preserve currect behaviour). When set to 0, components are not disconnected - gmirror will try to still use them (only first error will be logged). This is helpful when we have two broken components, but in different places, so actually all data is available. Such buggy component will be visible in 'gmirror list' output with flag BROKEN. - Never disconnect the last valid component. If we detect errors there we will just pass them up. This wasn't reasonable to deny access to the whole provider because of one broken sector. Prodded by: ru MFC after: 3 days
* Correct typo. 'fbp' is NULL here so this will result in a panic.pjd2006-02-111-1/+1
| | | | MFC after: 3 days
* Mark array as CLEAN when there are no write requests inpjd2006-02-112-101/+53
| | | | | | | | kern.geom.raid3.idletime seconds. Write, not any requests. Mark array as clean immediatelly on last write close. Prodded by: ru MFC after: 3 days
* Mark array as CLEAN when there are no write requests inpjd2006-02-112-103/+54
| | | | | | | | kern.geom.mirror.idletime seconds. Write, not any requests. Mark array as clean immediatelly on last write close. Prodded by: ru MFC after: 3 days
* Teach geli how to load keyfiles before root file system is mounted.pjd2006-02-111-19/+106
| | | | | | | | | | | | | | | | | | | | | | An example entries for loader.conf to make it possible: geli_da0_keyfile0_load="YES" geli_da0_keyfile0_type="da0:geli_keyfile0" geli_da0_keyfile0_name="/boot/keys/da0.key0" geli_da0_keyfile1_load="YES" geli_da0_keyfile1_type="da0:geli_keyfile1" geli_da0_keyfile1_name="/boot/keys/da0.key1" geli_da0_keyfile2_load="YES" geli_da0_keyfile2_type="da0:geli_keyfile2" geli_da0_keyfile2_name="/boot/keys/da0.key2" geli_da1s3a_keyfile0_load="YES" geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" Thanks for jhb and kan who showed me the right direction. MFC after: 3 days
* Check rootvnode variable to see if we still want to ask for passphrase onpjd2006-02-111-28/+2
| | | | | | boot. Other methods just don't work properly. MFC after: 3 days
* Catch the case when a subdisk has no provider or no consumerle2006-02-081-9/+12
| | | | attached to it.
* Clean up some sysctl descriptions, debug messages etc.brueffer2006-02-071-7/+7
| | | | | Approved by: pjd MFC after: 3 days
* Remove trailing spaces.pjd2006-02-0128-67/+67
|
* Allow to specify only one disk. This is helpful when we want to extendpjd2006-01-301-3/+3
| | | | | | our concatenated device later. MFC after: 1 week
* 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
* Rename geom_uzip class to g_uzip in order to be consistent with the namingfjoe2006-01-221-2/+2
| | | | | | of other GEOM modules. PR: 89998
* Fix bio leak in case of malloc(9) failure.pjd2006-01-181-0/+1
| | | | | | Found by: Coverity Prevent(tm) Coverity ID: CID794 MFC after: 3 days
* Remove dead code.pjd2006-01-181-2/+0
| | | | | | Found by: Coverity Prevent(tm) Coverity ID: CID105 MFC after: 3 days
* Remove dead code.pjd2006-01-181-2/+0
| | | | | | Found by: Coverity Prevent(tm) Coverity ID: CID104 MFC after: 3 days
* Style cleanups.pjd2006-01-181-24/+21
| | | | X-MFC-after: Already MFCed to RELENG_6 by accident.
* Move $FreeBSD$ from comment to __FBSDID().pjd2006-01-171-2/+3
|
* - Use better types.pjd2006-01-171-6/+6
| | | | | | - Log problems at level 0 when killing providers. MFC after: 3 days
* Check return value.pjd2006-01-171-0/+4
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Remove dead code.pjd2006-01-171-2/+0
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Remove unused value.pjd2006-01-171-2/+1
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Log situation when EIO is returned.pjd2006-01-171-0/+1
|
* Remove bio leak when EIO error is emulated.pjd2006-01-171-5/+5
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Get rid of the gv_bioq hack in most parts of the I/O path andle2006-01-065-81/+89
| | | | use the standard bioq structures.
* MFp4: Typo fix (without it the XML GEOM tree wasn't consistent).pjd2005-12-191-1/+1
| | | | Reported by: Eric Anderson <anderson@centtech.com>
* Fix build breakage by fixing typo.pjd2005-12-091-1/+1
| | | | Reported by: glebius
* - Allow to specify the byte which will be used for filling read buffer.pjd2005-12-081-4/+7
| | | | | | - Improve sysctl description a bit. Submitted by: Ivan Voras <ivoras@gmail.com>
OpenPOWER on IntegriCloud