diff options
| author | Artur Paszkiewicz <artur.paszkiewicz@intel.com> | 2017-03-09 12:00:01 +0300 |
|---|---|---|
| committer | Shaohua Li <shli@fb.com> | 2017-03-17 02:55:55 +0300 |
| commit | 4536bf9ba2d03404655586b07f8830b6f2106242 (patch) | |
| tree | 2b83774c1661296f1d5913c363342f5beaaf5eb9 /drivers/phy/phy-bcm-kona-usb2.c | |
| parent | 664aed04446c7f653d8acbe2cdf7989f28238524 (diff) | |
| download | linux-4536bf9ba2d03404655586b07f8830b6f2106242.tar.xz | |
raid5-ppl: load and recover the log
Load the log from each disk when starting the array and recover if the
array is dirty.
The initial empty PPL is written by mdadm. When loading the log we
verify the header checksum and signature. For external metadata arrays
the signature is verified in userspace, so here we read it from the
header, verifying only if it matches on all disks, and use it later when
writing PPL.
In addition to the header checksum, each header entry also contains a
checksum of its partial parity data. If the header is valid, recovery is
performed for each entry until an invalid entry is found. If the array
is not degraded and recovery using PPL fully succeeds, there is no need
to resync the array because data and parity will be consistent, so in
this case resync will be disabled.
Due to compatibility with IMSM implementations on other systems, we
can't assume that the recovery data block size is always 4K. Writes
generated by MD raid5 don't have this issue, but when recovering PPL
written in other environments it is possible to have entries with
512-byte sector granularity. The recovery code takes this into account
and also the logical sector size of the underlying drives.
Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Diffstat (limited to 'drivers/phy/phy-bcm-kona-usb2.c')
0 files changed, 0 insertions, 0 deletions