summaryrefslogtreecommitdiffstats
path: root/sbin/geom
Commit message (Collapse)AuthorAgeFilesLines
* Fix the online usage for the "dump" command.ru2007-05-241-1/+1
|
* Fix the construction of the gctl_req that got broken by mymarcel2007-05-171-1/+3
| | | | | | | | | | | | previous commit and that introduced optional parameters. Existing classes (like geli(8)) use empty strings by default and expect the parameter to be passed to the kernel as such. Also, the default value of a string argument can be NULL. Fix both cases by making the optional parameter conditional upon gc_argname being set and making sure to test for NULL before dereferencing the pointer. Reported by: brueffer@
* Bump G_LIB_VERSION to reflect the ABI change.marcel2007-05-161-1/+1
| | | | Pointed out by: pjd@
* Add gpart(8).marcel2007-05-1517-91/+512
| | | | | | | 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.
* Correct some typos.pjd2007-05-061-2/+2
|
* Fix mdoc warnings.pjd2007-05-061-3/+1
|
* Do some cleanups (like freeing memory and closing file descriptors) beforepjd2007-05-011-6/+6
| | | | leaving the functions.
* - Protect against specifing journal less than 100MB and against journalpjd2007-04-031-3/+12
| | | | | | | | | which size is not multiple of sector size. Reported by: Eric Anderson <anderson@centtech.com> - Improve wording in error message. I'm sorry, I don't remember who submitted this one.
* Exit status should be 1 on error.pjd2007-03-231-8/+5
| | | | | | PR: bin/110705 Reported by: Tom Judge MFC after: 2 weeks
* Warn when user use sectorsize bigger than the page size, which will leadpjd2007-03-051-0/+4
| | | | | | | | to problems when the geli device is used with file system or as a swap. Hopefully will prevent problems like kern/98742 in the future. MFC after: 1 week
* Fix incorrect comment. Geli will protect against data modification, ofpjd2007-03-051-5/+6
| | | | | | | course! It won't protect against reply attacks - try harder to explain them correctly. MFC after: 1 week
* 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-273-0/+241
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Correct typo.pjd2007-02-221-1/+1
| | | | Spotted by: Tomasz Dudzisz
* Forgot to hook up gjournal manual page to the build.pjd2007-02-101-1/+0
| | | | Reminded by: simon, piso
* Add gjournal(8) manual page. Documentation of kern.geom.journal.* sysctlspjd2007-01-291-0/+238
| | | | | | is still missing, ehh. Reviewed by: trhodes
* When the following conditions are meet:pjd2007-01-251-1/+13
| | | | | | | | | | | | | | | | - First configured key is based only on keyfile (no passphrase). - Device is attached. - User changes first key (setkey) from keyfile to passphrase and doesn't specify number of iterations (with -i option). ...geli(8) won't store calculated number of iterations in metadata. This result in device beeing unaccesable after detach. One can recover from this situation by guessing number of iterations generated, storing it in metadata and trying to attach device. Recovery procedure isn't nice, but one's data is not lost. Reported by: Thomas Nickl <T.Nickl@gmx.net> MFC after: 1 week
* Implement gctl_change_param() function, which changes value of existingpjd2007-01-252-0/+28
| | | | | | parameter. MFC after: 1 week
* Remove duplicate "clear" subcommand.ceri2006-12-211-4/+0
| | | | | PR: docs/106947 Submitted by: TAOKA Fumiyoshi
* Bump .Dd for -f|-F.ceri2006-11-022-2/+2
|
* Now, that we have gjournal in the tree add possibility to configurepjd2006-11-014-14/+39
| | | | | | 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.
* G_TYPE_NONE was replaced with G_TYPE_BOOL.pjd2006-11-011-2/+2
|
* Fix powerpc build.pjd2006-11-011-0/+1
| | | | Reported by: Peter Grehan <grehan@freebsd.org>
* Hook up gjournal bits to the build.pjd2006-10-311-0/+1
| | | | Sponsored by: home.pl
* Add userland control utility for gjournal GEOM class.pjd2006-10-314-0/+465
| | | | Sponsored by: home.pl
* Be sure to not create devices with (mediasize % sectorsize) != 0.pjd2006-10-101-0/+1
| | | | | Reported by: xride MFC after: 1 week
* Be sure to not create device whichpjd2006-10-101-0/+1
|
* A GEOM cache can speed up read performance by sending fixed sizeru2006-10-063-1/+251
| | | | | | | | | | read requests to its consumer. It has been developed to address the problem of a horrible read performance of a 64k blocksize FS residing on a RAID3 array with 8 data components, where a single disk component would only get 8k read requests, thus effectively killing disk performance under high load. Documentation will be provided later. I'd like to thank Vsevolod Lobko for his bright ideas, and Pawel Jakub Dawidek for helping me fix the nasty bug.
* MFp4: G_TYPE_BOOL sounds much better than G_TYPE_NONE.pjd2006-09-308-53/+53
| | | | Changes: 98722
* MFp4:pjd2006-09-302-47/+47
| | | | | | | | | | | - Print proper error message when argument is specified twice. Before the change it was detected properly, because of how G_OPT_DONE() macro worked. - Use err(3) functions where appropriate. - Add some assertions. - Bump version number, because G_TYPE_BOOL addition breaks API and ABI. Changes: 98721,98722,98723,101360,106985
* Add __printflike() attribute to various functions.pjd2006-09-301-4/+4
|
* Markup fixes.ru2006-09-182-6/+9
|
* Remove a contraction and add a missing article.brueffer2006-09-171-2/+2
|
* Fix copy&paste mistake.pjd2006-09-161-1/+1
| | | | Submitted by: Matthias Lederhofer <matled@gmx.net>
* Add 'configure' subcommand which for now only allows setting and removingpjd2006-09-162-1/+88
| | | | | | | | of the BOOT flag. It can be performed on both attached and detached providers. Requested by: Matthias Lederhofer <matled@gmx.net> MFC after: 1 week
* Note that we don't destroy keys on read-only attached providers.pjd2006-09-161-2/+5
| | | | MFC after: 1 week
* First kill detached providers, because of two reasons:pjd2006-09-161-7/+3
| | | | | | | | | - after killing all attached providers, all providers are then detached and operation is repeated for those who were attached, - we don't want to remove keys for read-only attached providers, we only want to detach them. MFC after: 1 week
* - Split failure probability configuration into read failure probability andpjd2006-09-082-13/+28
| | | | | | | write failure probability. - Allow to specify an error number to return of failure. MFC after: 3 days
* o Spell.maxim2006-08-101-1/+1
| | | | Submitted by: ru
* o Strip eol whitespaces.maxim2006-08-091-2/+2
|
* o New sentence, new line.maxim2006-08-091-2/+3
| | | | o Touch Dd for -r.
* Allow geli to operate on read-only providers.pjd2006-08-092-4/+7
| | | | | Initial patch from: vd MFC after: 2 weeks
* Add missing #.pjd2006-08-071-1/+1
|
* Allow to use the old -a option to specify an encryption algorithm to usepjd2006-06-061-9/+27
| | | | | (for backward compatibility), but print a warning to inform about the change.
* Clarify and merge two sentences.brueffer2006-06-061-4/+2
| | | | Discussed with: pjd
* Mdoc cleanup and some wording improvements.brueffer2006-06-061-15/+15
|
* Remove section committed by mistake. It is not yet ready.pjd2006-06-061-33/+0
|
* Document geli(8) data authentication.pjd2006-06-051-12/+116
| | | | Supported by: Wheel Sp. z o.o. (http://www.wheel.pl)
OpenPOWER on IntegriCloud