summaryrefslogtreecommitdiffstats
path: root/sbin/geom
Commit message (Collapse)AuthorAgeFilesLines
* Remove superfluous paragraph macro.joel2012-03-253-5/+0
|
* Document GEOM_PART_LDM scheme and partition types.ae2012-03-191-2/+38
| | | | MFC after: 1 month
* Fix a variety of grammar issues and style nits.eadler2012-03-041-74/+75
| | | | | | | | PR: docs/165668 Submitted by: Robert Simmons <rsimmons0@gmail.com> Reviewed by: kaduk@mit.edu Approved by: cperciva MFC after: 1 week
* Remove reference to gsched_as module, which doesn'teadler2012-02-221-1/+1
| | | | | | | | | actually exist. PR: docs/163043 Submitted by: olgeni Approved by: brd MFC after: 3 days
* Provide a better explanation for the sizing of the boot partition, anddes2012-01-131-10/+14
| | | | | | | | reduce the size of the partition in the example from 128 blocks to 94 blocks so it will end on a 128-block boundary. Also remove the -b option from the next example. MFC after: 3 weeks
* Fix warning when compiling with gcc46:eadler2012-01-101-2/+1
| | | | | | | | error: variable 'secsz' set but not used Reviewed by: ae Approved by: dim MFC after: 3 days
* Add support for >2TB disks in GEOM RAID for Intel metadata format.jimharris2012-01-091-1/+1
| | | | | | Reviewed by: mav Approved by: scottl MFC after: 1 week
* Whitespace-only fix. Translators, please feel free to ignore.wblock2012-01-091-3/+4
| | | | | | Approved by: gjb (mentor) MFC after: 3 days X-MFC-with: r227774, r227777, r227800
* Clarity improvements.wblock2012-01-091-8/+8
| | | | | Approved by: gjb (mentor) MFC after: 3 days
* Correct and expand BSD partitioning scheme description.wblock2011-11-211-7/+9
| | | | | | | | Correct GUID to GPT in RECOVERING section. Reviewed by: ae Approved by: gjb (mentor) MFC after: 1 week
* Fix date.wblock2011-11-211-1/+1
| | | | | Approved by: gjb (mentor) MFC after: 1 week
* Add a section that explicitly describes partitioning schemes. Modifywblock2011-11-211-126/+154
| | | | | | | | | existing sections to refer to the new one. Rearrange partitioning scheme list so MBR and EBR types are together. Also add several corrections for grammar, clarity, and consistency. Approved by: gjb (mentor) MFC after: 1 week
* Fix build on some archs after r227464.mav2011-11-121-3/+4
|
* Fix buildworld breakage due after r227464.dim2011-11-121-1/+1
| | | | Pointy hat to: mav
* Major GEOM MULTIPATH class rewrite:mav2011-11-122-98/+194
| | | | | | | | | | | | | | | | | | | | | | | | | - Improved locking and destruction process to fix crashes. - Improved "automatic" configuration method to make it consistent and safe by reading metadata back from all specified paths after writing to one. - Added provider size check to reduce chance of ordering conflict with other GEOM classes. - Added "manual" configuration method without using on-disk metadata. - Added "add" and "remove" commands to allow manage paths manually. - Failed paths are no longer dropped from geom, but only marked as FAIL and excluded from I/O operations. - Automatically restore failed paths when all others paths are marked as failed, for example, because of device-caused (not transport) errors. - Added "fail" and "restore" commands to manually control FAIL flag. - geom is now destroyed on last path disconnection. - Added optional Active/Active mode support. Unlike Active/Passive mode, load evenly distributed between all working paths. If supported by the device, it allows to significantly improve performance, utilizing bandwidth of all paths. It is controlled by -A option during creation. Disabled by default now. - Improved `status` and `list` commands output. Sponsored by: iXsystems, inc. MFC after: 1 month
* Clarify disks/volumes above 2TiB support in geom_raid:mav2011-10-261-1/+4
| | | | | | | | | | - add support for volumes above 2TiB with Promise metadata format; - enforse and document other limitations: - Intel and Promise metadata formats do not support disks above 2TiB; - NVIDIA metadata format does not support volumes above 2TiB. Sponsored by: iXsystems, Inc. MFC after: 2 weeks
* Add support for creating GELI devices with older metadata version for usepjd2011-10-252-7/+84
| | | | | | | | | | | | | | with older FreeBSD versions: - Add -V option to 'geli init' to specify version number. If no -V is given the most recent version is used. - If -V is given don't allow to use features not supported by this version. - Print version in 'geli list' output. - Update manual page and add table describing which GELI version is supported by which FreeBSD version, so one can use it when preparing GELI device for older FreeBSD version. Inspired by: Garrett Cooper <yanegomi@gmail.com> MFC after: 3 days
* Add 'geli version' subcommand, which will print GELI metadata version of eachpjd2011-10-252-0/+62
| | | | | | | given GEOM provider or if not providers are given it will print versions supported by userland geli(8) utility and by ELI GEOM class. MFC after: 3 days
* When we detect GELI metadata version that is newer than the highest wepjd2011-10-251-5/+35
| | | | | | | support, inform the user about that instead of 'MD5 hash mismatch'. Suggested by: Garrett Cooper <yanegomi@gmail.com> MFC after: 3 days
* Simplify eli_resize() function.pjd2011-10-251-10/+4
| | | | MFC after: 3 days
* Simplify eli_dump() function and allow to dump metadata stored in backup file.pjd2011-10-251-13/+3
| | | | MFC after: 3 days
* If 'req' is NULL, print error on stderr.pjd2011-10-251-2/+7
| | | | MFC after: 3 days
* Simplify eli_is_attached() function and make it return boot instead of int.pjd2011-10-251-6/+2
| | | | MFC after: 3 days
* Simplify eli_backup_create() and eli_backup_restore() functions.pjd2011-10-251-87/+28
| | | | | | | As a side-effect it is now possible to backup unsupported (newer) GELI metadata versions. MFC after: 3 days
* Sort includes.pjd2011-10-251-13/+13
| | | | MFC after: 3 days
* - change "is is" to "is" or "it is"eadler2011-10-161-1/+1
| | | | | | | | - change "the the" to "the" Approved by: lstewart Approved by: sahil (mentor) MFC after: 3 days
* Don't use the whole free space when resizing partition to a larger sizeae2011-09-081-6/+6
| | | | | | | | | | | on a disk with non zero stripesize (e.g. disks with 4k sector size)[1]. Also do not use automatic alignment when size is exactly specified, but an alignment is not. Use automatic alignment only for case when user omits both "-s" and "-a" options. Reported by: Mikael Fridh <frimik at gmail> [1] Approved by: re (kib) MFC after: 1 week
* o Fix mdoc formatting for the '.Fx' macro. [1]ae2011-08-201-3/+13
| | | | | | | | o Add information about APM scheme and fix typos. [2] Submitted by: gjb [1], nwhitehorn [2] Approved by: re (kib) MFC after: 1 week
* Add new section "BOOTSTRAPPING" to the gpart(8), that describesae2011-08-191-12/+90
| | | | | | | | | bootstrap code images used to boot from MBR, GPT, BSD and VTOC8 schemes. Reviewed by: marius (previous version) Approved by: re (kib) MFC after: 1 week
* When user specifies the bootcode with size smaller than VTOC_BOOTCODE,ae2011-06-211-1/+4
| | | | | | | | gpart_write_partcode_vtoc8 does access out of range of allocated memory. Check size of bootcode before writing it. Pointed out by: ru MFC after: 1 week
* Mod the offset padding by alignment. Without this change we maydelphij2011-06-211-2/+2
| | | | | | pad too much when underlying GEOM object have a zero stripesize. MFC after: 1 month
* The "size" param needs no adjusting to stripeoffset.ae2011-06-211-2/+2
| | | | Reported by: Kris Moore
* Add "alignment" param to the request before calling gpart_autofill().ae2011-06-161-0/+1
|
* Do not use LCM from stripesize and user specified alignment value.ae2011-06-071-7/+4
| | | | | | | | When user wants have specific alignment - do what user wants. Use stripesize as alignment value in case, when some of gpart's arguments are ommitted for automatic calculation. Suggested by: mav
* Rework parts of this man page to improve grammar.gavin2011-06-061-37/+37
| | | | | | | Inspired by, and parts submitted by... PR: docs/157467 Submitted by: Ben Kaduk <kaduk mit.edu> MFC after: 2 weeks
* Remove redundant assignments to WARNS.ed2011-06-061-2/+0
| | | | For these directories, WARNS is already implied to be 6.
* Generally clean up markup.ru2011-06-031-71/+85
|
* Always use LCM when stripesize > 0.ae2011-06-021-2/+2
|
* Use stripesize and stripeoffset in the automatic calculation ofae2011-06-021-18/+33
| | | | | | | | | | partition offsets. If user requests specific alignment and provider's stripesize is not zero, then use a least common multiple from the stripesize and user specified value. Also fix "gpart resize" implementation: do not try to align the partition size, because the start offset may be not aligned. Instead align the end offset and then calculate size. Also use stripesize and stripeoffset for "gpart resize" command.
* mdoc: fix markupuqs2011-06-021-0/+1
|
* Document kern.geom.part.check_integrity sysctl variable.ae2011-05-301-1/+17
|
* Add example how to create MBR and BSD schemes and install boot code.ae2011-05-271-1/+28
|
* Synchronize manpage's synopsis with program's usage. Since -l and -rae2011-05-272-5/+6
| | | | | | | keys are mutually exclusive for the `gpart show` command, then mark them so. Requested by: ru
* Simplify ALIGNDOWN macro.ae2011-05-241-1/+1
|
* Fix calculation of alignment for odd values. Also do not change valueae2011-05-241-2/+2
| | | | when it is already aligned.
* Some partitioning schemes want to have partitions that are alignedae2011-05-151-10/+14
| | | | | | | | | | | | | with geometry. And they do recalculation of user specified parameters. MBR, PC98, VTOC8, EBR schemes are doing that. For these schemes an auto alignment feature (ie. gpart add -a alignment) would not work. But it can work for GPT and BSD schemes. BSD scheme usualy is created inside MBR, so we can use knowledge about offset of MBR partition to calculate aligned values for BSD partitions. Use "offset" attribute of the parent provider for better alignment. MFC after: 2 weeks
* Simplify the code a bit. For own providers GEOM_PART always providesae2011-05-151-61/+14
| | | | | | "start" and "end" config attributes. MFC after: 1 week
* Document the following sysctls:pjd2011-05-081-2/+22
| | | | | | | | | kern.geom.eli.version kern.geom.eli.key_cache_limit kern.geom.eli.key_cache_hits kern.geom.eli.key_cache_misses MFC after: 1 week
* Add "-a alignment" option to gpart(8). When it specified gpart(8)ae2011-05-032-27/+99
| | | | | | | tries to align partition start offset and size to be multiple of alignment value. MFC after: 2 weeks
* MFgraid/head:mav2011-03-244-0/+368
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add new RAID GEOM class, that is going to replace ataraid(4) in supporting various BIOS-based software RAIDs. Unlike ataraid(4) this implementation does not depend on legacy ata(4) subsystem and can be used with any disk drivers, including new CAM-based ones (ahci(4), siis(4), mvs(4), ata(4) with `options ATA_CAM`). To make code more readable and extensible, this implementation follows modular design, including core part and two sets of modules, implementing support for different metadata formats and RAID levels. Support for such popular metadata formats is now implemented: Intel, JMicron, NVIDIA, Promise (also used by AMD/ATI) and SiliconImage. Such RAID levels are now supported: RAID0, RAID1, RAID1E, RAID10, SINGLE, CONCAT. For any all of these RAID levels and metadata formats this class supports full cycle of volume operations: reading, writing, creation, deletion, disk removal and insertion, rebuilding, dirty shutdown detection and resynchronization, bad sector recovery, faulty disks tracking, hot-spare disks. For Intel and Promise formats there is support multiple volumes per disk set. Look graid(8) manual page for additional details. Co-authored by: imp Sponsored by: Cisco Systems, Inc. and iXsystems, Inc.
OpenPOWER on IntegriCloud