Lines Matching +full:lines +full:- +full:initial +full:- +full:states
2 dm-raid
5 The device-mapper RAID (dm-raid) target provides a bridge from DM to MD.
6 It allows the MD RAID drivers to be accessed using a device-mapper
11 -----------------------
26 - Transitory layout
29 - rotating parity 0 with data continuation
32 - rotating parity N with data continuation
35 - rotating parity 0 with data restart
38 - rotating parity N with data restart
41 - rotating parity zero (left-to-right) with data restart
44 - rotating parity N (right-to-left) with data restart
47 - rotating parity N (right-to-left) with data continuation
50 - parity and Q-syndrome on the last 2 disks;
52 raid6_la_6 Same as "raid_la" plus dedicated last Q-syndrome disk
54 - layout for takeover from raid5_la from/to raid6
55 raid6_ra_6 Same as "raid5_ra" dedicated last Q-syndrome disk
57 - layout for takeover from raid5_ra from/to raid6
58 raid6_ls_6 Same as "raid5_ls" dedicated last Q-syndrome disk
60 - layout for takeover from raid5_ls from/to raid6
61 raid6_rs_6 Same as "raid5_rs" dedicated last Q-syndrome disk
63 - layout for takeover from raid5_rs from/to raid6
67 - RAID10: Striped Mirrors (aka 'Striping on top of mirrors')
68 - RAID1E: Integrated Adjacent Stripe Mirroring
69 - RAID1E: Integrated Offset Stripe Mirroring
70 - and other similar RAID10 variants
103 Mark drive index 'idx' write-mostly.
105 See '--write-behind=' (man mdadm)
117 variations to how the copies are laid down - the default
133 The 2-device layout is equivalent 2-way RAID1. The 4-device
135 3-device layout is what might be called a 'RAID1E - Integrated
169 Here we see layouts closely akin to 'RAID1E - Integrated
173 The delta_disks option value (-251 < N < +251) triggers
185 where the data starts. This is used to provide out-of-place
190 forward reshaping, the out-of-place space will be allocated
195 number of stripes, calculate the redundancy blocks (CRC/Q-syndrome)
197 N-1 other new stripes. This out-of-place scheme is used to change
203 uses it to close the 'write hole' caused by the non-atomic updates
206 be throttled versus non-journaled raid4/5/6 sets.
224 If a drive has failed or is missing at creation time, a '-' can be
229 --------------
233 # RAID4 - 4 data drives, 1 parity (no metadata devices)
236 # (Lines separated for easy reading)
240 5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
242 # RAID4 - 4 data drives, 1 parity (with metadata devices)
252 -------------
268 Line 1 is the standard output produced by device-mapper.
274 Here we can see the RAID type is raid4, there are 5 devices - all of
275 which are 'A'live, and the array is 2/490221568 complete with its initial
282 - 'A' = alive and in-sync
283 - 'a' = alive but not in-sync
284 - 'D' = dead/failed.
289 <sync_action> One of the following possible states:
292 - No synchronization action is being performed.
294 - The current action has been halted.
296 - Array is undergoing its initial synchronization
300 - A device in the array is being rebuilt or
303 - A user-initiated full check of the array is
310 - The same as "check", but discrepancies are
313 - The array is undergoing a reshape.
320 raid parameter to support out-of-place reshaping).
321 <journal_char> - 'A' - active write-through journal device.
322 - 'a' - active write-back journal device.
323 - 'D' - dead journal device.
324 - '-' - no journal device.
329 -----------------
330 The dm-raid target will accept certain actions through the 'message' interface.
345 ---------------
363 discard support is disabled -- this ensures data integrity at the
369 For trusted devices, the following dm-raid module parameter can be set
376 ---------------
380 1.0.0 Initial version. Support for RAID 4/5/6
386 1.4.0 Non-functional change. Removes arg from mapping function.
402 1.9.2 Don't emit '- -' on the status table line in case the constructor
404 'D' on the status line. If '- -' is passed into the constructor, emit
405 '- -' on the table line and '-' as the status line health character.
410 1.11.1 Add raid4/5/6 journal write-back support via journal_mode option