linux/mdadm
1
0
Fork 0
Code Issues Activity

Merging upstream version 4.3+20240412.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-14 06:34:22 +01:00
parent 8e1e76d6e6
commit 9a795ca236
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
67 changed files with 2247 additions and 2747 deletions
Download patch file Download diff file Expand all files Collapse all files

21
mdadm.8.in
View file

@ -3179,7 +3179,7 @@ environment. This can be useful for testing or for disaster
recovery. You should be aware that interoperability may be
compromised by setting this value.
These change can also be suppressed by adding
These change can also be suppressed by adding
.B mdadm.imsm.test=1
to the kernel command line. This makes it easy to test IMSM
code in a virtual machine that doesn't have IMSM virtual hardware.
@ -3454,6 +3454,25 @@ is any string. These names are supported by
since version 3.3 provided they are enabled in
.IR mdadm.conf .
.SH UNDERSTANDING OUTPUT
.TP
EXAMINE
.TP
.B checkpoint
Checkpoint value is reported when array is performing some action including
resync, recovery or reshape. Checkpoints allow resuming action from certain
point if it was interrupted.
Checkpoint is reported as combination of two values: current migration unit
and number of blocks per unit. By multiplying those values and dividing by
array size checkpoint progress percentage can be obtained in relation to
current progress reported in /proc/mdstat. Checkpoint is also related to (and
sometimes based on) sysfs entry sync_completed but depending on action units
may differ. Even if units are the same, it should not be expected that
checkpoint and sync_completed will be exact match nor updated simultaneously.
.SH NOTE
.I mdadm
was previously known as