| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
error: variable 'secsz' set but not used
Reviewed by: ae
Approved by: dim
MFC after: 3 days
|
|
|
|
|
|
| |
Reviewed by: mav
Approved by: scottl
MFC after: 1 week
|
|
|
|
|
|
| |
Approved by: gjb (mentor)
MFC after: 3 days
X-MFC-with: r227774, r227777, r227800
|
|
|
|
|
| |
Approved by: gjb (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
Correct GUID to GPT in RECOVERING section.
Reviewed by: ae
Approved by: gjb (mentor)
MFC after: 1 week
|
|
|
|
|
| |
Approved by: gjb (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Pointy hat to: mav
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
support, inform the user about that instead of 'MD5 hash mismatch'.
Suggested by: Garrett Cooper <yanegomi@gmail.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
As a side-effect it is now possible to backup unsupported (newer)
GELI metadata versions.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
- change "the the" to "the"
Approved by: lstewart
Approved by: sahil (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
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 Add information about APM scheme and fix typos. [2]
Submitted by: gjb [1], nwhitehorn [2]
Approved by: re (kib)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
pad too much when underlying GEOM object have a zero stripesize.
MFC after: 1 month
|
|
|
|
| |
Reported by: Kris Moore
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Inspired by, and parts submitted by...
PR: docs/157467
Submitted by: Ben Kaduk <kaduk mit.edu>
MFC after: 2 weeks
|
|
|
|
| |
For these directories, WARNS is already implied to be 6.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
keys are mutually exclusive for the `gpart show` command, then mark
them so.
Requested by: ru
|
| |
|
|
|
|
| |
when it is already aligned.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
"start" and "end" config attributes.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
tries to align partition start offset and size to be multiple of
alignment value.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
Make `geom XXX list` and `geom XXX status` outputs more consistent:
Add -a options to print all geoms, not only ones with providers.
Add -g option for `status` to report geom's names, not provider's.
Make `status` by default report provider's status (if present), not geom's.
Make `status` report consumer's statuses, not only "synchronized" field.
|
|
|
|
|
| |
Pointed out: Ben Kaduk
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
I'm sorry to anyone who felt offended by this.
PR: docs/155385
Reported by: maga_lena <mirto@riseup.net>
MFC after: 1 week
|