From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: Test feedback 2.6.17.4+libata-tj-stable (EH, hotplug) Date: Tue, 11 Jul 2006 11:52:16 +0900 Message-ID: <44B31260.5030409@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from nz-out-0102.google.com ([64.233.162.192]:50657 "EHLO nz-out-0102.google.com") by vger.kernel.org with ESMTP id S965094AbWGKCwj (ORCPT ); Mon, 10 Jul 2006 22:52:39 -0400 Received: by nz-out-0102.google.com with SMTP id o37so146684nzf for ; Mon, 10 Jul 2006 19:52:38 -0700 (PDT) In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Christian Pernegger Cc: linux-ide@vger.kernel.org, linux-raid@vger.kernel.org Christian Pernegger wrote: > The fact that the disk had changed minor numbers after it was plugged > back in bugs me a bit. (was sdc before, sde after). Additionally udev > removed the sdc device file, so I had to manually recreate it to be > able to remove the 'faulty' disk from its md array. That's because md is stilling holding onto sdc in failed mode. A hotplug script which checks whether a removed device is in md array and if so removes it from the array will solve the problem. Not sure whether that would be the correct approach though. Thanks. -- tejun