svn commit: r218537 - stable/8/sbin/geom/class/part
Andrey V. Elsukov
ae at FreeBSD.org
Fri Feb 11 05:48:45 UTC 2011
Date: Fri Feb 11 05:48:44 2011
New Revision: 218537
Fix up the grammar.
MFC r217342,217343,217344 by maxim:
o Typo fixes.
o Start each sentence on a new line. No content changes.
o Somehow I revert Dd macro in the previous commit.
Document the "bios-boot" partition type.
stable/8/sbin/geom/class/part/ (props changed)
--- stable/8/sbin/geom/class/part/gpart.8 Fri Feb 11 05:37:05 2011 (r218536)
+++ stable/8/sbin/geom/class/part/gpart.8 Fri Feb 11 05:48:44 2011 (r218537)
@@ -24,7 +24,7 @@
-.Dd November 22, 2010
+.Dd January 28, 2011
.Dt GPART 8
@@ -422,8 +422,9 @@ about its use.
.It Cm restore
Restore the partition table from backup previously created by
-action and given from standard input. Only partition table
-may be restored. This action does not affect content of partitions.
+action and given from standard input.
+Only partition table may be restored.
+This action does not affect content of partitions.
This mean that you should copy your data from backup after restoring
partition table and write bootcode again if it is needed.
@@ -508,6 +509,11 @@ utility also allows the user to specify
for partition types that do not have symbol names.
The symbolic names currently understood are:
.Bl -tag -width ".Cm freebsd-vinum"
+.It Cm bios-boot
+The system partition dedicated to second stage of the boot loader program.
+Usually it used by GRUB 2 loader when the partition table is GPT.
+The scheme-specific type is
+.Qq Li "!21686148-6449-6E6F-744E-656564454649" .
.It Cm efi
The system partition for computers that use the Extensible Firmware
@@ -703,20 +709,23 @@ action.
The GEOM class PART supports recovering of partition tables only for GPT.
The GUID partition table has a primary and secondary (backup) copy of
-metadata for redundance. They are stored in the begining and in the end
-of device respectively. Therefore it is acceptable to have some corruptions
-in the metadata that are not fatal to work with GPT. When kernel detects
-corrupt metadata it marks this table as corrupt and reports about corruption.
+metadata for redundance.
+They are stored in the begining and in the end of device respectively.
+Therefore it is acceptable to have some corruptions in the metadata that
+are not fatal to work with GPT.
+When kernel detects corrupt metadata it marks this table as corrupt and
+reports about corruption.
Any changes in corrupt table are prohibited except
.Cm recover .
In case when only first sector is corrupt kernel can not detect GPT even
-if partition table is not corrupt. You can write protective MBR with
+if partition table is not corrupt.
+You can write protective MBR with
.Xr dd 1
-command to restore ability of GPT detection. The copy of protective MBR is
-usually located in the
+command to restore ability of GPT detection.
+The copy of protective MBR is usually located in the
@@ -743,25 +752,27 @@ and
will report about corrupt table.
In case when the size of device has changed (e.g. volume expansion) the
-secondary GPT header will become located not in the last sector. This is
-not a metadata corruption, but it is dangerous because any corruption of
-the primary GPT will lead to lost of partition table. Kernel reports about
-this problem with message:
+secondary GPT header will become located not in the last sector.
+This is not a metadata corruption, but it is dangerous because any
+corruption of the primary GPT will lead to lost of partition table.
+Kernel reports about this problem with message:
.Bd -literal -offset indent
GEOM: provider: the secondary GPT header is not in the last LBA.
A corrupt table can be recovered with
.Cm gpart recover
-command. This command does reconstruction of corrupt metadata using
-known valid metadata. Also it can relocate secondary GPT to the end of
+This command does reconstruction of corrupt metadata using
+known valid metadata.
+Also it can relocate secondary GPT to the end of device.
.Pa NOTE :
The GEOM class PART can detect the same partition table on different GEOM
-providers and some of them will marked as corrupt. Be careful when choising
-a provider for recovering. If you did incorrect choise you can destroy
-metadata of another GEOM class, e.g. GEOM MIRROR or GEOM LABEL.
+providers and some of them will be marked as corrupt.
+Be careful when choosing a provider for recovering.
+If you choose incorrectly you can destroy the metadata of another GEOM class,
+e.g. GEOM MIRROR or GEOM LABEL.
.Sh EXIT STATUS
Exit status is 0 on success, and 1 if the command fails.
More information about the svn-src-stable-8