Searched refs:reshape (Results 1 – 5 of 5) sorted by relevance
175 value) to any reshape supporting raid levels 4/5/6 and 10.207 Takeover/reshape is not possible with a raid4/5/6 journal device;312 reshape313 - The array is undergoing a reshape.426 # Add required out-of-place reshape space to the beginniong of the given 2 data devices,430 # Example table of the out-of-place reshape space addition for one data device, e.g. dm-1435 # Mapping table for e.g. raid5_rs reshape causing the size of the raid device to double-fold once t…464 with a reshape in progress.465 1.9.0 Add support for RAID level takeover/reshape/region size473 1.10.1 Fix data corruption on reshape request[all …]
582 raid_state_str := "frozen" | "reshape" |"resync" | "check" | "repair" | "recover" | "idle" |"undef"
67 return [np.repeat(arr, r).reshape(-1, 2) for arr in index]109 lengths = (np.diff(vec) + self.element_size).reshape(len(vec))
2786 bool reshape; in rs_prepare_reshape() local2810 reshape = false; in rs_prepare_reshape()2812 reshape = true; in rs_prepare_reshape()2815 reshape = true; in rs_prepare_reshape()2821 reshape = true; in rs_prepare_reshape()2825 reshape = false; in rs_prepare_reshape()2832 if (reshape) { in rs_prepare_reshape()
314 These are called when resync/recovery/reshape starts or stops.