| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In addition to adding `static' where possible:
- bin/date: Move `retval' into extern.h to make it visible to date.c.
- bin/ed: Move globally used variables into ed.h.
- sbin/camcontrol: Move `verbose' into camcontrol.h and fix shadow warnings.
- usr.bin/calendar: Remove unneeded variables.
- usr.bin/chat: Make `line' local instead of global.
- usr.bin/elfdump: Comment out unneeded function.
- usr.bin/rlogin: Use _Noreturn instead of __dead2.
- usr.bin/tset: Pull `Ospeed' into extern.h.
- usr.sbin/mfiutil: Put global variables in mfiutil.h.
- usr.sbin/pkg: Remove unused `os_corres'.
- usr.sbin/quotaon, usr.sbin/repquota: Remove unused `qfname'.
|
|
|
|
|
|
|
| |
That should help to handle some cases when disk has some RAID metadata that
should be ignored, especially during boot.
MFC after: 3 days
|
|
|
|
|
|
| |
boundary.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
provider in an Active/Passive configuration.
Reviewed by: mav
MFC after: 4 weeks
|
| |
|
|
|
|
|
|
|
|
|
| |
references to it in gsched(8) to the existing ada(4) driver.
PR: docs/170085
Submitted by: olgeni
Approved by: gavin
MFC after: 5 days
|
|
|
|
|
|
| |
PR: docs/169089
Submitted by: John W. O'Brien <john@saltant.com>
MFC after: 3 days
|
|
|
|
| |
MFC after: 1 day
|
|
|
|
|
|
|
| |
PR: 168016
Submitted by: Nobuyuki Koganemaru
Approved by: gjb
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
when it finds corrupt data.
PR: kern/165695
Submitted by: Robert Simmons <rsimmons0@gmail.com>
Reviewed by: pjd
Approved by: cperciva
MFC after: 1 week
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
with alignment.
PR: bin/167567
Tested by: Warren Block
MFC after: 1 week
|
|
|
|
| |
redundancy) for the following RAID levels: RAID4/5E/5EE/6/MDF.
|
|
|
|
|
| |
format options. Use it for specifying byte order for the DDF metadata:
big-endian defined by specification and little-endian used by Adaptec.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
defined by the SNIA Common RAID Disk Data Format Specification v2.0.
Supports multiple volumes per array and multiple partitions per disk.
Supports standard big-endian and Adaptec's little-endian byte ordering.
Supports all single-layer RAID levels. Dual-layer RAID levels except
RAID10 are not supported now because of GEOM RAID design limitations.
Some work is still to be done, but the present code already manages basic
interoperation with RAID BIOS of the Adaptec 1430SA SATA RAID controller.
MFC after: 1 month
Sponsored by: iXsystems, Inc.
|
|
|
|
|
|
| |
PR: 167382
Submitted by: John W. O'Brien (john%saltant.com)
X-Needs-MFC: r226840
|
|
|
|
|
|
|
|
| |
some environment to differentiate 4 possible RAID5 on-disk layouts.
Tested with Intel and AMD RAID BIOSes.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Implement "configure" command to allow switching operation mode of
running device on-fly without destroying and recreation.
- Implement Active/Read mode as hybrid of Active/Active and Active/Passive.
In this mode all paths not marked FAIL may handle reads same time,
but unlike Active/Active only one path handles write requests at any
point in time. It allows to closer follow original write request order
if above layers need it for data consistency (not waiting for requisite
write completion before sending dependent write).
- Hide duplicate messages about device status change.
- Remove periodic thread wake up with 10Hz rate.
MFC after: 2 weeks
Sponsored by: iXsystems, Inc.
|
| |
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
PR: docs/165668
Submitted by: Robert Simmons <rsimmons0@gmail.com>
Reviewed by: kaduk@mit.edu
Approved by: cperciva
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
actually exist.
PR: docs/163043
Submitted by: olgeni
Approved by: brd
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
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
|