Re: write-refresh md array (feature request)

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

 



Hello!
You can achieve this with a bit inderect way - there are sync_min and
sync_max params which can be used to operate on certain borders of
array, more info
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/md.txt?id=refs/tags/v3.11#n579
.

On Tue, Sep 10, 2013 at 10:19 PM, Henrique de Moraes Holschuh
<hmh@xxxxxxxxxx> wrote:
> (please CC me on replies).
>
> I've been in several situations where it would have been helpful to be able
> to refresh weak sectors by rewriting the whole md raid component device,
> without the need to increase array failure risk through a fail+remove+add
> cycle for the component device.
>
> How difficult would it be to implement a "refresh" as a Linux md driver
> sync_action, pigging back on "check" ?
>
> Are there any drawbacks to write-refreshing component devices?
>
> --
>   "One disk to rule them all, One disk to find them. One disk to bring
>   them all and in the darkness grind them. In the Land of Redmond
>   where the shadows lie." -- The Silicon Valley Tarot
>   Henrique Holschuh
> --
> 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



-- 
Best regards,
[COOLCOLD-RIPN]
--
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