| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
PR: 168016
Submitted by: Nobuyuki Koganemaru
Approved by: gjb
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
with alignment.
PR: bin/167567
Tested by: Warren Block
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
tries to align partition start offset and size to be multiple of
alignment value.
MFC after: 2 weeks
|
|
|
|
|
| |
Pointed out: Ben Kaduk
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
| |
often have wrapped lines.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
partitions instead of partition's indexes. This may be useful with
GPT partitioning scheme or EBR without GEOM_PART_EBR_COMPAT option.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
Re-revert it.
|
|
|
|
|
| |
Suggested by: jhb
MFC after: 1 week
|
|
|
|
|
|
| |
PR: docs/153933
Submitted by: jpaetzel@, Warren Block
MFC after: 1 week
|
|
|
|
|
| |
PR: docs/153933
MFC after: 3 days
|
|
|
|
| |
to arg0 and dumping core when `gpart bootcode` called without arguments.
|
|
|
|
|
|
| |
While I'm here remove redundancy and inconsistencies.
Obtained from: Juniper Networks
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
does restore them only when -l option is specified [1]. Make number of
entries field in backup format optional. Document -l and -r options of
`gpart show` action.
Suggested by: pjd [1]
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
restore it from given backup.
Discussed with: geom@
Approved by: kib (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was needed for recover implementation.
Implement the recover command for GPT. Now GPT will marked as
corrupt when any of three types of corruption will be detected:
1. Damaged primary GPT header or table
2. Damaged secondary GPT header or table
3. Secondary header is not located in the last LBA
Marked GPT becomes read-only. Any changes with corrupt table
are prohibited. Only "destroy" and "recover" commands are allowed.
Discussed with: geom@ (mostly silence)
Tested by: Ilya A. Arhipov
Approved by: mav (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
| |
Suggested by: kib
Approved by: kib (mentor)
MFC after: 5 days
|
|
|
|
|
|
|
| |
list other schemes attributes.
Reviewed by: simon, rpaulo
MFC after: 2 weeks
|