Re: How to force rewrite of a smart detected bad block with raid5: checkarray?

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

 





Marc MERLIN wrote:

So, I went back and read man md, and md.txt in the kernel Documentation
tree, but I could not find documentation on this:
echo 3907029168 > sync_min echo 3907029170 > sync_max
and as per my other post, it didn't work for me on 2.6.36
(echo: write error: Invalid argument)

sync_max is mentioned in md.txt for 2.6.29.1 (currently running here):

  This is a number of sectors at which point a resync/recovery
     process will pause.  When a resync is active, the value can
     only ever be increased, never decreased.  The value of 'max'
     effectively disables the limit.

There is no mention of sync_min.

Regards,

Richard
--
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