From owner-freebsd-fs@FreeBSD.ORG Thu Aug 7 05:12:02 2008 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A6A01065679 for ; Thu, 7 Aug 2008 05:12:02 +0000 (UTC) (envelope-from vyeperman@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by mx1.freebsd.org (Postfix) with ESMTP id 498FB8FC0A for ; Thu, 7 Aug 2008 05:12:02 +0000 (UTC) (envelope-from vyeperman@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so213657wfg.7 for ; Wed, 06 Aug 2008 22:12:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=YFEdZAVZCTjxR/5V/JMMV1E+hKSFU4vFXmLQS5dsRbE=; b=rkvmdI8WYVFXVnsc4qKKsnY3xzHnjUd869o+1c2p/EKxgOZyuVFZ0aCjj5+nQE48/k 4ZHy1/Fj8sJvS63kgeIoPvUMeMsOLg3SNICbN2GjVzgJHo2+fyVCrkBeGQBl5j1hN8C8 K18BuJcAgiIZmjVkwfFLUOaSDcUOI2j2oRKh0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=D5IyMWCK2o+/HASO/LaU3kwOno2XahkUktKmp8Hu11oxgd7jJkemf4V2nyA7/sDgWx OdVGqHO5C5feSyucb8nuU5qZ8roqllqFA4DWZ/EfczcwTjz7lCWvTY6LgxgXDf5Dqh9P aR+Y4wobAdpMkynGGcIXrWtZzorfxNSYTpEGY= Received: by 10.142.212.19 with SMTP id k19mr311311wfg.142.1218085921917; Wed, 06 Aug 2008 22:12:01 -0700 (PDT) Received: by 10.143.7.6 with HTTP; Wed, 6 Aug 2008 22:12:01 -0700 (PDT) Message-ID: <6c3c36d00808062212y4e9a1464i48e146e84725a36e@mail.gmail.com> Date: Wed, 6 Aug 2008 22:12:01 -0700 From: "Vye Wilson" To: "Jeremy Chadwick" In-Reply-To: <20080807044759.GA7505@eos.sc1.parodius.com> MIME-Version: 1.0 References: <6c3c36d00808062109y6ae176a0ha055129392b00542@mail.gmail.com> <20080807044759.GA7505@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: zpool degraded - 'UNAVAIL cannot open' functioning drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Aug 2008 05:12:02 -0000 When I physically disconnected the disk it showed: subdisk18: detached ad18: detached There was nothing in dmesg after plugging the disk back in but atacontrol showed it on channel 9: ATA channel 9: Master: ad18 Serial ATA v1.0 Slave: no device present After detaching and reattaching the device with atacontrol this is what dmesg had to say: subdisk18: detached ad18: detached ata9: [ITHREAD] ad18: 286168MB at ata9-master SATA150 zpool is still saying it cannot read from ad18 after detaching and reattaching with atacontrol. However, I remade the zpool and instead of physically removing the drive I just used the atacontrol detatch/attach and it was able to resilver without any issues. That helps but what if I do have a drive failure? I shouldn't need to halt the system to switch out the drive. Thanks. On Wed, Aug 6, 2008 at 9:47 PM, Jeremy Chadwick wrote: > On Wed, Aug 06, 2008 at 09:09:02PM -0700, Vye Wilson wrote: > > Hello, > > > > I setup a raidz1 zpool to test ZFS with a device failure and to see how > > quickly the zpool could be resilvered. The system I'm using has a > backplane > > that all the drives are connected to, so everything is hotswappable. I > > created the raidz1 zpool and then removed one of the drives. zpool status > > showed that the pool was degraded but online. Ok great, so lets bring the > > now functioning drive back online. > > > > [root@Touzyoh /home/vye]# zpool online ztemp ad18 > > Bringing device ad18 online > > > > Everything looks good... lets check the zpool status > > > > pool: ztemp > > state: DEGRADED > > status: One or more devices could not be opened. Sufficient replicas > exist > > for > > the pool to continue functioning in a degraded state. > > action: Attach the missing device and online it using 'zpool online'. > > see: http://www.sun.com/msg/ZFS-8000-D3 > > scrub: resilver completed with 0 errors on Wed Aug 6 20:59:54 2008 > > config: > > > > NAME STATE READ WRITE CKSUM > > ztemp DEGRADED 0 0 0 > > raidz1 DEGRADED 0 0 0 > > ad10 ONLINE 0 0 0 > > ad14 ONLINE 0 0 0 > > ad18 UNAVAIL 0 0 0 cannot open > > > > errors: No known data errors > > > > Doh! still degraded. It shows 'UNAVAIL cannot open' I've tried rebooting > but > > it will not open that drive at all. According to dmesg the drive is > > functional, and if I destroy the pool and recreate it the drive works > fine. > > I wasn't able to find any similar issues on this mailing list or in > google. > > Does anyone have any ideas? I've attached my dmesg output. > > What was in your dmesg when you yanked the disk? What was in your dmesg > when you re-inserted the disk? > > Did you try detaching it administratively using "atacontrol detach" > first, then retaching it using "atacontrol attach"? > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > -- --Vye