Re: Raid5/6 journal re-add

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Nov 19, 2017 at 4:00 PM, Larkin Lowrey <llowrey@xxxxxxxxx> wrote:
> I did a 'pull-the-drive' test on a raid6 array with a write-journal and
> found that mdadm (v4.0-218-gfe05dc4 - 2017-11-09) would not let me --re-add
> the drive so I add to --add it.
>
> mdadm: --re-add for /dev/sdq1 to /dev/md124 is not possible
>
> My expectation was that the drive would be recognized as being the missing
> member and would be re-added and only out-of-sync regions would be resync'd.
>
> When I --add'ed the drive to the array the resync process started for the
> entire array, not just for the out-of-sync regions. Is this correct behavior
> for arrays with write journals? Are there plans to perform a selective
> re-sync rather than a full re-sync?

Needs to be in the mdadm.conf for this array, see 'man mdadm.conf'

-- 
Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux