summaryrefslogtreecommitdiffstats
path: root/sbin/geom
Commit message (Collapse)AuthorAgeFilesLines
* Allow to specify only one disk. This is helpful when we want to extendpjd2006-01-302-5/+16
| | | | | | our concatenated device later. MFC after: 1 week
* Add a reference to geli(8).pjd2006-01-291-0/+3
| | | | MFC after: 3 days
* Teach NOP GEOM class how to gather the following statistics:pjd2005-12-082-6/+25
| | | | | | | | - number of read I/O requests, - number of write I/O requests, - number of read bytes, - number of written bytes. Add 'reset' subcommand for resetting statistics.
* - The geom(8) utility only uses three types of arguments: string (char *),pjd2005-12-0710-729/+327
| | | | | | | | | | | | | | | | | value (intmax_t) and boolean (int). Based on that provide three functions: - gctl_get_ascii() - gctl_get_int() - gctl_get_intmax() - Hide gctl_get_param() function, as it is only used internally in subr.c. - Allow to provide argument name as (fmt, ...). - Assert geom(8) bugs (missing argument is a geom(8) bug). - Clean-up and simplify the code by using new functions and assumtions (no more checking for missing argument). Tested by: regression tests
* s/5.5/6.0/ in HISTORY section.joel2005-11-241-1/+1
| | | | Discussed with: ru
* gmirror.8:ceri2005-10-252-2/+4
| | | | | | | | | Note the default balancing algorithm and stripe size. geom_mirror.c: Slightly friendlier error message. Reviewed by: pjd
* Add a note in example as well, that last sector is used for metadata,pjd2005-09-291-1/+2
| | | | | | | so it don't provoke confusions. Noticed by: Victor Sudakov <sudakov@sibptus.tomsk.ru> MFC after: 2 days
* Even if there are no valid keys in metadata, but provider is attachedpjd2005-09-101-5/+5
| | | | | | | we can still use setkey subcommand. MFC after: 3 days Found by: regression tests
* As with NO_CRYPT, don't try to compile geli(8) when NO_OPENSSL is definedmarius2005-08-271-1/+1
| | | | | | either. MFC after: 1 week
* Update Document.takawata2005-08-261-0/+3
|
* By default, when doing crypto work in software, start as many threadspjd2005-08-211-1/+3
| | | | | | as we have active CPUs and bind each thread to its own CPU. MFC after: 3 days
* Allow to change number of iterations for PKCS#5v2. It can only be usedpjd2005-08-192-23/+64
| | | | | | when there is only one key set. MFC after: 3 days
* Move function for calculating number of bits into more central place.pjd2005-08-193-6/+14
| | | | | | I want to use it so more. MFC after: 3 days
* Update manual page (now dedicated kernel thread is always started).pjd2005-08-171-2/+0
| | | | MFC after: 3 days
* Unfortunately dlerror(3) returns string, so there is no clean way topjd2005-08-141-11/+12
| | | | | | | | | | ignore "no such file" errors only, which I wanted to do. Because of this I ignored all other errors on dlopen(3) failure as well, which isn't good. Fix this situation by calling access(2) on library file first and ignore only ENOENT error. This allows to report all the rest of dlopen(3) errors. MFC after: 3 days
* When keys were configured without passphrase, number of iterations inpjd2005-08-141-0/+4
| | | | | | | | | | metadata is equal to -1. if we then wanted to attach provider (or change keys) and forget about '-p' flag it failed on assertion (quite ok, without assertion it could call PKCS#5v2 with 4294967295 iterations). Instead of failing on assertion, remind about '-p' flag. MFC after: 3 days
* GELI doesn't need cryptodev.pjd2005-08-121-1/+0
| | | | MFC after: 2 days
* Add code for Ext2FS and ReiserFS labels recognition.pjd2005-08-121-0/+6
| | | | | | Submitted by: Stanislav Sedov <stas@310.ru> PR: kern/84638 MFC after: 1 week
* Add missing check for the NO_CRYPT build option.ru2005-08-021-0/+2
| | | | Reported by: Alexander Polakov
* Misc cleanup (spelling, grammar, mdoc, style, cut >80 char lines).brueffer2005-07-301-83/+93
|
* I actually do need libmd.pjd2005-07-291-2/+2
|
* I think I found the problem, reconnect geli to the build.pjd2005-07-271-1/+1
|
* - Reduce WARNS level to 3, so it will be compilabe on alpha.pjd2005-07-271-3/+4
| | | | | | | - Don't link libmd, it is not needed. - Connect manual page to the build. MFC after: 1 week
* Disconnect geli from the build for now.pjd2005-07-271-1/+1
| | | | | I need to find out first what is the cause of sha2.c compilation problem on alpha.
* Connect GEOM_ELI class to the build.pjd2005-07-271-0/+1
| | | | MFC after: 1 week
* Add GEOM_ELI class which provides GEOM providers encryption.pjd2005-07-273-0/+1774
| | | | | | | | For features list and usage see manual page: geli(8). Sponsored by: Wheel Sp. z o.o. http://www.wheel.pl MFC after: 1 week
* Don't forget to initialize 'id' field.pjd2005-07-131-0/+1
| | | | MFC after: 3 days
* Remove trailing spaces.pjd2005-04-291-1/+1
|
* Fix stripe size in example.pjd2005-04-261-1/+1
| | | | | Found by: kris MFC after: 3 days
* Remove duplicated description of 'clear' subcommand.pjd2005-04-231-2/+0
| | | | | Pointed out by: marck X-MFC-after: few seconds
* Document 'clear' and 'dump' subcommands.pjd2005-04-151-0/+11
| | | | MFC after: 1 week
* Allow classes to specify local source files.pjd2005-04-071-2/+2
| | | | MFC after: 3 weeks
* Empty error buffer is not an error.pjd2005-04-071-1/+1
| | | | MFC after: 3 weeks
* Fix use of uninitialized buf[0].pjd2005-03-221-2/+2
| | | | | Reported by: stefanf MFC after: 3 days
* Be sure that class name storaed in 'class_name' is lower case.pjd2005-03-141-0/+3
| | | | MFC after: 1 week
* Define subcommands' usage inside g_command structure.pjd2005-03-147-141/+109
| | | | MFC after: 1 week
* - Add gc_usage field to g_command structure. This will allow to definepjd2005-03-142-56/+52
| | | | | | | | | | | | usage for a subcommand, so no 'usage' function has to be implemented in class library. - Bump version number as it breaks ABI, but don't provide backward compatibility, because there are probably no external consumers of this geom(8). This allows to print more precise usage for standard commands and simplify class libraries a bit. MFC after: 1 week
* Instead of documenting every standard subcommand's argument everywhere,pjd2005-03-147-98/+56
| | | | | | just leave reference to geom(8). MFC after: 1 week
* Document subcommands' arguments.pjd2005-03-141-2/+18
| | | | MFC after: 1 week
* Document '-s' option of 'status' subcommand.pjd2005-03-141-0/+6
| | | | MFC after: 1 week
* Add '-s' option to 'status' subcommand. It produces script-friendly output:pjd2005-03-141-26/+50
| | | | | | | | | | | | | | | | | | | # gmirror status Name Status Components mirror/root COMPLETE ad0s1a ad2s1a mirror/data DEGRADED da0 da1 (76%) da2 # gmirror status -s Name Status Components mirror/root COMPLETE ad0s1a mirror/root COMPLETE ad2s1a mirror/data DEGRADED da0 mirror/data DEGRADED da1 (76%) mirror/data DEGRADED da2 MFC after: 1 week
* Use int instead of size_t (%*s needs int).pjd2005-03-141-9/+9
| | | | MFC after: 1 week
* printf(3) expects that %*s having an int parameter, which generatesdelphij2005-03-141-5/+5
| | | | | | | warning on 64-bit platforms. Explicitly cast these values to int to work around this issue, as these values are tend to be small. Spotted by: ia64 tinderbox
* - Document 'status' subcommand.pjd2005-03-138-17/+68
| | | | | | - Update copyrights. MFC after: 1 week
* Add 'status' command which prints general information about devices.pjd2005-03-131-0/+176
| | | | | | | | | | | | | | For example: # gmirror status Name Status Components mirror/root COMPLETE ad0s1a ad2s1a mirror/data DEGRADED da0 da1 (76%) da2 MFC after: 1 week
* Update copyrights.pjd2005-03-131-1/+1
|
* Change function names related to 'list' command from 'show_one_*' topjd2005-03-131-7/+7
| | | | | | 'list_one_*'. MFC after: 1 week
* When listing all devices (geoms) from the given class, skip geoms withoutpjd2005-03-131-0/+2
| | | | | | | | providers. This prevents from listing geoms like <name>.sync which can be confusing. It still allows to show details about it by giving its name when listing. MFC after: 1 week
* Typos and grammar fixes, wordsmithingbrueffer2005-02-281-6/+6
|
* - Add md_provsize field to metadata, which will help withpjd2005-02-276-15/+36
| | | | | | | | | | | | | | | | | 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
OpenPOWER on IntegriCloud