From mboxrd@z Thu Jan 1 00:00:00 1970 From: NeilBrown Subject: Re: OK, Now this is really weird Date: Sun, 27 Feb 2011 18:57:04 +1100 Message-ID: <20110227185704.18777dfa@notabene.brown> References: <20110227083433.69b3d99a@notabene.brown> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: lrhorer@satx.rr.com Cc: 'Linux RAID' List-Id: linux-raid.ids On Sun, 27 Feb 2011 01:22:41 -0600 "Leslie Rhorer" wrote: >=20 > > > >> > =A0 =A0 So what gives? =A0/dev/sdk3 no longer even exists, s= o why hasn't > > it > > > >> > been failed and removed on /dev /md3 like it has on /dev/md1= and > > > >> /dev/md2? > > > >> > > > >> Is it possible there has been no I/O request for /dev/md3 sinc= e > > > >> /dev/sdk failed? > > > > > > > > =A0 =A0 =A0 =A0Well, I thought about that. =A0It's swap space, = so I suppose it's > > > > possible. =A0I would have thought, however, that mdadm would fa= il a > > missing > > > > member whether there is any I/O or not. > > > > > > > > -- > > > > To unsubscribe from this list: send the line "unsubscribe linux= -raid" > > in > > > > the body of a message to majordomo@vger.kernel.org > > > > More majordomo info at =A0http://vger.kernel.org/majordomo-info= =2Ehtml > > > > > > > > > > I thought so as well. But how will mdadm know is the device is fa= ulty, > > > unless the device is generating errors? (which usually only happe= ns on > > > read and/or write) > >=20 > > With very recent mdadm the command > >=20 > > mdadm -If sdXX > >=20 > > will find any md array that has /dev/sdXX as a member and will fail= and > > remove it. >=20 > No, it's version 3.1.4, and that gives me a "Device or Resource > busy" error. It does report that it set sdk3 faulty, but the hot rem= ove > fails. >=20 > So how can I remove the drive (so I can add it back)? Maybe: mdadm /dev/md2 --remove failed 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