From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Lyakas Subject: Re: RAID-10 explicitly defined drive pairs? Date: Sun, 25 Mar 2012 11:30:04 +0200 Message-ID: References: <20111212115459.GC20730@fi.muni.cz> <4EE61EAE.20101@anonymous.org.uk> <20120106150823.GX25976@fi.muni.cz> <20120107075526.59ed433c@notabene.brown> <20120322213114.61fd4e44@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20120322213114.61fd4e44@notabene.brown> Sender: linux-raid-owner@vger.kernel.org To: NeilBrown Cc: Jan Kasprzak , linux-raid , John Robinson List-Id: linux-raid.ids Thanks, Neil! I will merge this in and test. On Thu, Mar 22, 2012 at 12:31 PM, NeilBrown wrote: > On Thu, 22 Mar 2012 12:01:48 +0200 Alexander Lyakas > wrote: > >> Neil, >> >> > =A0echo frozen > /sys/block/mdN/md/sync_action >> > =A0mdadm --add /dev/mdN /dev...... >> > =A0echo recover > /sys/block/mdN/md/sync_action >> > >> > it should do them all at once. >> > >> > I should teach mdadm about this.. >> >> What is required to do that from mdadm? I don't see any other place >> where MD_RECOVERY_FROZEN is set, except via sysfs. So do you suggest >> that mdadm use sysfs for that? > > Yes. > > http://neil.brown.name/git?p=3Dmdadm;a=3Dcommitdiff;h=3D9f58469128c99= c0d7f434d28657f86789334f253 > >> Also, what should be done if mdadm succeeds to "freeze" the array, b= ut >> fails to "unfreeze" it for some reason? > > What could possibly cause that? > I guess if someone kills mdadm while it was running.. > > > NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-raid" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html