From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: raid1 recovery: reads and writes Date: Tue, 16 Dec 2008 14:04:58 -0700 Message-ID: <494817FA.5040108@intel.com> References: <18758.51053.866819.442495@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Jon Nelson Cc: Neil Brown , LinuxRaid List-Id: linux-raid.ids 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