Re: raid1 recovery: reads and writes

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

 



Jon Nelson wrote:
..

Yes it is hard to guess what is happening here; however, should not
the following commit go to -stable?

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=56ac36d722d0d27c03599d1245ac0ab59e474e5c

Is it possible this commit is (partially) responsible for what I was
seeing? Under what conditions would it trigger?

I don't think this commit is responsible, it's a fix for a case where the kernel was asked to do a repair but a recovery is pending.

This commit addressed a bug in external-metadata support when adding a spare disk via sysfs. It would be fairly difficult to trigger this in the non-external-metadata case. It would require a check/repair request to come in immediately after the disk was (re-)added, but before the kernel started the resync.

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