[continued from previous message]

PV onto another is not supported; only and exactly
one PV is affected by this operation. Grows or
shrinks whose effects don't "fit" the designated PV
will result in an error message and no effect. For
example, you can't do a shrink on a multi-PV setup
such that the designated PV should shrink to zero
size and so effectively should disappear. Nor can
you do a grow which would necessitate the growth of
some other PV or the addition of new PVs.

As in diskutil coreStorage resizePV, note that you
cannot grow unless there is free space in the par-
tition map beyond the designated PV, which is not
normally the case because you usually don't leave
gaps of free space on your disk.

You can specify a size of zero (0) to fill up all
remaining space to the partition following the des-
ignated PV's booter or to the end of the partition
map, if possible.

DEVICES
A device parameter to any of the above commands (except where explicitly
required otherwise) can usually be any of the following:

+ The disk identifier (see below). Any entry of the form of
disk*, e.g. disk1s9.

+ The device node entry containing the disk identifier. Any
entry of the form of /dev/disk*, e.g. /dev/disk2.

+ The volume mount point. Any entry of the form of /Volumes/*,
e.g. /Volumes/Untitled. In most cases, a "custom" mount point
e.g. /your/custom/mountpoint/here is also accepted.

+ The URL form of any of the volume mount point forms described
above. E.g. file:///Volumes/Untitled or file:///.

+ A UUID. Any entry of the form of e.g.
11111111-2222-3333-4444-555555555555. The UUID can be a
"media" UUID which IOKit places in an IOMedia node as derived
from e.g. a GPT map's partition UUID, or it can be an AppleRAID
(or CoreStorage) set (LV) or member (PV) UUID.

DISK IDENTIFIER
The disk identifier string variously identifies a device unit, a session
upon that device, or a partition (slice) upon that session. It may take
the form of diskU, diskUsS, diskUsQ, or diskUsQsS, where U, S, and Q are
positive decimal integers (possibly multi-digit), and where:

+ U is the device unit. It may refer to hardware (e.g. a hard
drive, optical drive, or memory card) or a "drive" constructed
by software (e.g. an AppleRAID set or a disk image).

+ Q is the session and is only included for optical media; it
refers to the number of times recording has taken place on the
currently-inserted medium (disc).

+ S is the slice; it refers to a partition. Upon this partition,
the raw data that underlies a user-visible file system is usu-
ally present, but it may also contain specialized data for cer-
tain 3rd-party database programs, or data required for the sys-
tem software (e.g. EFI or booter partitions, or APM partition
map data).

Some units (e.g. floppy disks, RAID sets) contain file system data upon
their "whole" device instead of containing a partitioning scheme with
partitions.

Note that the forms diskUsQ and diskUsS appear the same and must be dis-
tinguished by context. For non-optical media, this two-part form identi-
fies a slice upon which (file system) data is stored. For optical media,
it identifies a session upon which a partitioning scheme (with its slices
with file systems) is stored.

SIZES
Wherever a size is emitted as an output, it is presented as a base-ten
approximation to the precision of one fractional decimal digit and a
base-ten SI multiplier, often accompanied by a precise count in bytes.
Scripts should refrain from parsing this human-readable output and use
the -plist option instead.

Wherever a size is to be supplied by you as an input, you can provide
values in several different ways, some absolute and some context-sensi-
tive. All suffixes described below are interpreted in a case-insensitive
manner. The B is optional.

The most common way is to specify absolute values as a decimal number,
possibly followed by a period and a decimal fraction, followed without
whitespace with a suffix as follows:

+ B is bytes (not blocks) where the multiplier is 1. This suffix
may be omitted.

+ K[B] is power of ten kilobytes where the multiplier is 1000 (1
x 10^3).

+ M[B] is power of ten megabytes where the multiplier is 1000000
(1 x 10^6).

+ G[B] is power of ten gigabytes where the multiplier is
1000000000 (1 x 10^9).

+ T[B] is power of ten terabytes where the multiplier is
1000000000000 (1 x 10^12).

+ P[B] is power of ten petabytes where the multiplier is
1000000000000000 (1 x 10^15).

+ E[B] is power of ten exabytes where the multiplier is
1000000000000000000 (1 x 10^18).

You can also use the following suffixes:

+ S | UAM ("sectors") is 512-byte units (device-independent)
where the multiplier is always 512.

+ DBS ("device block size") is the device-dependent native block
size of the encompassing whole disk, if applicable, where the
multiplier is often 512, but not always; indeed it might not be
a power of two.

+ Ki[B] is power of two kibibytes where the multiplier is 1024 (1
x 2^10).

+ Mi[B] is power of two mebibytes where the multiplier is 1048576
(1 x 2^20).

+ Gi[B] is power of two gibibytes where the multiplier is
1073741824 (1 x 2^30).

+ Ti[B] is power of two tebibytes where the multiplier is
1099511627776 (1 x 2^40).

+ Pi[B] is power of two pebibytes where the multiplier is
1125899906842624 (1 x 2^50).

+ Ei[B] is power of two exbibytes where the multiplier is
1152921504606846976 (1 x 2^60).

In certain contexts (e.g. when specifying partition triplets) you can
provide a relative value as follows:

+ % (with a preceding number) is a percentage of the whole-disk
size, the partition map size, or other allocatable size, as
appropriate by context. Use of % is not supported in all situ-
ations.

+ R (with no preceding number) specifies the remainder of the
whole-disk size or other allocatable size after all other
triplets in the group are taken into account. It need not be
in the last triplet. It must only appear in at most one
triplet among all triplets. Use of R is not supported in all
situations.

You can provide an operating system-defined constant value as follows:

+ %recovery% (with no preceding number) is the customary size of
Mac OS X Recovery Partitions.

Note again that B refers to bytes and S and UAM refer to a constant mul-
tiplier of 512; the latter are useful when working with tools such as gpt
(8) or df (1). Note also that this multiplier is not a "block" size as
actually implemented by the underlying device driver and/or hardware, nor
is it an "allocation block", which is a file system's minimum unit of
backing store usage, often formatting-option-dependent.

Examples: 10G (10 gigabytes), 4.23tb (4.23 terabytes), 5M (5 megabytes),
4GiB (exactly 2^32 bytes), 126000 (exactly 126000 bytes), 25.4% (25.4
percent of whole disk size).

FORMAT
The format parameter for the erasing and partitioning verbs is the file
system personality name. You can determine this name by looking in a
file system bundle's
/System/Library/Filesystems/<fs>.fs/Contents/Info.plist or by using the
listFilesystems verb, which also lists shortcut aliases for common per-
sonalities (these shortcuts are defined by diskutil for use with it
only).

Common examples include JHFS+, MS-DOS, etc.

EXAMPLES
Erase a disk
diskutil eraseDisk JHFS+ Untitled disk3

Erase a volume
diskutil eraseVolume HFS+ UntitledHFS /Volumes/SomeDisk

Partition a disk with three partitions
diskutil partitionDisk disk3 3 HFSX Name1 10G JHFS+ Name2 10G MS-DOS
NAME3 10G

Partition a disk with the APM partitioning scheme
diskutil partitionDisk disk3 APM HFS+ vol1 25% Journaled\ HFS+ vol2 25%
Journaled\ HFS+ vol3 50% Free\ Space volX 0%

Partition a disk with the GPT partitioning scheme
diskutil partitionDisk disk3 GPT HFS+ vol1 25% MS-DOS VOL2 25% HFS+ vol3
50% Free\ Space volX 0%

Resize a volume and create a volume after it, using all remaining space
diskutil resizeVolume /Volumes/SomeDisk 50g MS-DOS DOS 0b

Resize a volume and leave all remaining space as unused
diskutil resizeVolume /Volumes/SomeDisk 12g

Convert a disk to Core Storage and encrypt it
diskutil coreStorage convert disk3s2 -passphrase

Shrink your Core Storage PV in order to make space for a Boot Camp volume
subtract desired Windows size from LV size, to be new LV size, i.e. 150g
diskutil coreStorage list
diskutil coreStorage resizeStack LVUUID PVUUID 150g ms-dos BOOTCAMP 0

Revert a disk from Core Storage back to plain HFS, possibly decrypting
diskutil coreStorage revert disk5

Create a Core Storage setup "manually"
diskutil coreStorage createLVG LVG1 disk0s2 disk1s2
diskutil cs list
diskutil cs createLV LVGUUID jhfs+ LVG1-Vol1 100%

Remove a partition
diskutil eraseVolume Free\ Space not disk0s4

Merge two partitions into a new partition
diskutil mergePartitions JHFS+ not disk1s3 disk1s5

Split a partition into three new ones
diskutil splitPartition /Volumes/SomeDisk JHFS+ vol1 12g MS-DOS VOL2 8g
JHFS+ vol3 0b

Create a RAID
diskutil createRAID mirror MirroredVolume JHFS+ disk1 disk2

Destroy a RAID
diskutil destroyRAID /Volumes/MirroredVolume

Repair a damaged RAID
diskutil repairMirror /Volumes/MirroredVolume disk3

Convert volume into RAID volume
diskutil enableRAID mirror /Volumes/ExistingVolume

Erase a partition and shrink to add an associated Recovery Partition
diskutil splitPartition disk8s2 JHFS+ MacHD R %Apple_Boot% %noformat%
%recovery%

SEE ALSO
hdiutil(1), mount(8), umount(8), diskmanagementd(8),
diskmanagementstartup(8), diskarbitrationd(8), corestoraged(8), ioreg(8),
newfs_hfs(8), fsck_hfs(8), authopen(1), hfs.util(8), msdos.util(8),
ufs.util(8), drutil(1), vsdbutil(8)

ERRORS
diskutil will exit with status 0 if successful or 1 if it cannot complete
the requested operation; this includes cases in which usage text is
printed. Before diskutil returns with status 1, it prints a message
which might include an explanation local to diskutil, an error string
from the DiskManagement or MediaKit frameworks, an underlying POSIX
error, or some combination.

HISTORY
The eraseDisk and partitionDisk verbs had an option to add Mac OS 9 driv-
ers (in partitions designated for that purpose); there was also a
repairOS9Permissions verb. These have been removed.

Starting with Mac OS X 10.11, the verify- and repairPermissions verbs
have been removed.

Starting with Mac OS X 10.6, the input and output notation of disk and
partition sizes use power-of-10 suffixes. In the past this has been
power-of-2, regardless of the suffix (e.g. G, Gi, GiB) used for display
or accepted as input. Starting with Mac OS X 10.11, the B suffix is
optional even for "bare" numeric values.

Mac OS X 7 October 2015 Mac OS X

[Opération terminée]

--
Gérard FLEUROT <g4fleurot@free.fr> plus un

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)