|Main index||Section 8||日本語||Options|
disk represents the disk in question, and may be in the form da0 or /dev/da0. It will display the partition layout.
If the drive type is specified, the entry of that name in the disktab(5) file is used; otherwise, or if the type is specified as 'auto', a default layout is used.
This command opens the disk label in the default editor, and when the editor exits, the label is validated and if OK written to disk.
The bsdlabel utility is capable of restoring a disk label that was previously saved in a file in ASCII format. The prototype file used to create the label should be in the same format as that produced when reading or editing a label. Comments are delimited by ‘#’ and newline.
|/boot/boot||Default boot image.|
|Disk description file.|
8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 16 4.2BSD 2048 16384 5128 b: 1091994 81936 swap c: 1173930 0 unused 0 0 # "raw" part, don't edit
# /dev/da1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 51 tracks/cylinder: 19 sectors/cylinder: 969 cylinders: 1211 sectors/unit: 1173930 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0
8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 16 4.2BSD 1024 8192 16 b: 160000 81936 swap c: 1173930 0 unused 0 0 # "raw" part, don't edit
Lines starting with a ‘#’ mark are comments.
The partition table can have up to 8 entries. It contains the following information:
|#||The partition identifier is a single letter in the range ‘a’ to ‘h’. By convention, partition ‘c’ is reserved to describe the entire disk.|
The size of the partition in sectors,
(kilobytes - 1024),
(megabytes - 1024*1024),
(gigabytes - 1024*1024*1024),
(percentage of free space
removing any fixed-size partitions other than partition
(all remaining free space
fixed-size and percentage partitions).
a size of
indicates the entire disk.
Lowercase versions of suffixes
Size and suffix should be specified without any spaces between them.
Example: 2097152, 1G, 1024M and 1048576K are all the same size (assuming 512-byte sectors).
|The offset of the start of the partition from the beginning of the drive in sectors, or * to have bsdlabel calculate the correct offset to use (the end of the previous partition plus one, ignoring partition ‘c’). For partition ‘c’, * will be interpreted as an offset of 0. The first partition should start at offset 16, because the first 16 sectors are reserved for metadata.|
|Describes the purpose of the partition. The above example shows all currently used partition types. For UFS file systems and ccd(4) partitions, use type 4.2BSD. For Vinum drives, use type vinum. Other common types are swap and unused. By convention, partition ‘c’ represents the entire slice and should be of type unused, though bsdlabel does not enforce this convention. The bsdlabel utility also knows about a number of other partition types, none of which are in current use. (See the definitions starting with FS_UNUSED in <sys/disklabel.h> for more details.)|
|fsize||For 4.2BSD file systems only, the fragment size; see newfs(8).|
|bsize||For 4.2BSD file systems only, the block size; see newfs(8).|
|For 4.2BSD file systems, the number of cylinders in a cylinder group; see newfs(8).|
Save the in-core label for
into the file
This file can be used with the
bsdlabel da0s1 > savedlabel
Create a label for da0s1:
bsdlabel -w /dev/da0s1
Read the label for da0s1, edit it, and install the result:
bsdlabel -e da0s1
Read the on-disk label for da0s1, edit it, and display what the new label would be (in sectors). It does not install the new label either in-core or on-disk:
bsdlabel -e -n da0s1
Write a default label on da0s1. Use another Fl command to edit the partitioning and file system information:
bsdlabel -w da0s1
Restore the on-disk and in-core label for da0s1 from information in savedlabel:
bsdlabel -R da0s1 savedlabel
Display what the label would be for da0s1 using the partition layout in label_layout. This is useful for determining how much space would be allotted for various partitions with a labeling scheme using %-based or * partition sizes:
bsdlabel -R -n da0s1 label_layout
Install a new bootstrap on da0s1. The boot code comes from /boot/boot:
bsdlabel -B da0s1
Install a new label and bootstrap. The bootstrap code comes from the file newboot in the current working directory:
bsdlabel -w -B -b newboot /dev/da0s1
Completely wipe any prior information on the disk, creating a new bootable disk with a DOS partition table containing one slice, covering the whole disk. Initialize the label on this slice, then edit it. The dd(1) commands are optional, but may be necessary for some BIOSes to properly recognize the disk:
dd if=/dev/zero of=/dev/da0 bs=512 count=32 gpart create -s MBR da0 gpart add -t freebsd da0 gpart set -a active -i 1 da0 gpart bootcode -b /boot/mbr da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 bsdlabel -w -B da0s1 bsdlabel -e da0s1
This is an example disk label that uses some of the new partition size types such as %, M, G, and *, which could be used as a source file for "bsdlabel -R ada0s1 new_label_file":
8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 400M 16 4.2BSD 4096 16384 75 # (Cyl. 0 - 812*) b: 1G * swap c: * * unused e: 204800 * 4.2BSD f: 5g * 4.2BSD g: * * 4.2BSD
The various BSD Ns s all use slightly different versions of BSD labels and are not generally compatible.
|BSDLABEL (8)||October 5, 2016|
|Main index||Section 8||日本語||Options|
Please direct any comments about this manual page service to Ben Bullock.
|“||This philosophy, in the hands of amateurs, leads to inexplicably mind-numbing botches like the existence of two programs, “head” and “tail,” which print the first part or the last part of a file, depending. Even though their operations are duals of one another, “head” and “tail” are different programs, written by different authors, and take different options!||”|
|— The Unix Haters' handbook|