From owner-freebsd-fs@FreeBSD.ORG Sat Mar 21 16:01:04 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8508626 for ; Sat, 21 Mar 2015 16:01:04 +0000 (UTC) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5266D768 for ; Sat, 21 Mar 2015 16:01:04 +0000 (UTC) Received: by lbbrr9 with SMTP id rr9so29255494lbb.0 for ; Sat, 21 Mar 2015 09:01:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7eDZOVieq7T1Drw+zaY4nj8/tQtWw+uW+MNx/yM1bmc=; b=L4xzmm7a8jYWsfgunCYabh9rrAoNllcgjA3IIRrQ8XR+NzcxXrNiMauY6Iwf6+ZwNo brqcXsOveitcTGQaoWZtlfZqhlnye7t/0iO9VN89zXnqBYYltMJuC4WPEXvdPNZaG207 m3CpFsYDvHlaPhBJ891ErkVswEg9mRbioT2AoKK7ylKqj/6o6q3OevS21loYXH0f9Ic5 y5evbFVb9sepiUXvXCJigNjvMw0+ZwGQbSuIFYqxcJ7aTsMJHTQuGMU0C/8CscqVpBvl r5Ew8paOKJJ1sDFirw+FageiwSuURPpeMSCSKlrSapaZ7EaPC1NaqzAuAX0QpzxgYRKO kRqQ== MIME-Version: 1.0 X-Received: by 10.152.10.209 with SMTP id k17mr47125310lab.50.1426953662190; Sat, 21 Mar 2015 09:01:02 -0700 (PDT) Received: by 10.112.162.5 with HTTP; Sat, 21 Mar 2015 09:01:02 -0700 (PDT) In-Reply-To: References: <550C8D1A.3070402@gmail.com> <550C938F.70500@gmail.com> <986BB4BF-D960-46EE-8E15-6FC5A5B6D219@ultra-secure.de> <550C9E70.60501@gmail.com> <550CA2BF.2070406@gmail.com> Date: Sat, 21 Mar 2015 09:01:02 -0700 Message-ID: Subject: Re: zfs on FreeBSD 8.2 64bit stuck in "One or more devices is currently being resilvered" From: motty cruz To: Mehmet Erol Sanliturk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Mar 2015 16:01:05 -0000 Hi Mehmet, are you thinking a bad HDD bay? If I ran the gstat command I see is writing to disk : dT: 1.002s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 0 0 0 0.0 0 0 0.0 0.0| acd0 0 9 0 0 0.0 9 144 22.1 3.1| mfid0 0 9 0 0 0.0 9 144 22.6 3.1| mfid0s1 0 9 0 0 0.0 9 144 22.9 3.2| mfid0s1a 0 0 0 0 0.0 0 0 0.0 0.0| mfid0s1b 0 0 0 0 0.0 0 0 0.0 0.0| mfid0s1d 0 0 0 0 0.0 0 0 0.0 0.0| mfid0s1e 0 0 0 0 0.0 0 0 0.0 0.0| mfid0s1f 2 4631 4631 13270 0.4 0 0 0.0 73.0| da0 0 0 0 0 0.0 0 0 0.0 0.0| da1 3 3979 3979 13345 0.7 0 0 0.0 78.0| da2 0 0 0 0 0.0 0 0 0.0 0.0| da3 5 4503 4503 13263 0.5 0 0 0.0 76.0| da4 5 4245 4245 13254 0.6 0 0 0.0 77.5| da5 4 4741 0 0 0.0 4741 11626 1.2 86.7| da6 disk being replace is da6, as you can see w/s11626? unless I am not reading this right? so I don't think is the cable or port. I really don't know what is causing this issue: today is the 3rd day resilvering: # zpool status pool: tank state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scrub: resilver in progress for 47h47m, 100.00% done, 0h0m to go config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz2 ONLINE 0 0 0 label/019 ONLINE 0 0 0 label/001b ONLINE 0 0 0 label/003 ONLINE 0 0 0 label/007b ONLINE 0 0 0 1.79T resilvered label/005 ONLINE 0 0 0 label/006 ONLINE 0 0 0 label/0171 ONLINE 0 0 0 any suggestion on what should be my next step? Thanks in advance! -Motty On Fri, Mar 20, 2015 at 10:23 PM, Mehmet Erol Sanliturk < m.e.sanliturk@gmail.com> wrote: > > > On Fri, Mar 20, 2015 at 3:44 PM, Motty Cruz wrote: > >> Can you describe what you did to replace the disk? >> >> I sure can. I had spare hdd in the pool. >> #zpool replace tank label/004 label/007b >> >> label/003 ONLINE 0 0 0 >> replacing DEGRADED 0 0 0 >> 433419809408607751 UNAVAIL 0 0 0 >> was/dev/label/007 >> label/004 ONLINE 0 0 0 2.47T >> resilvered >> label/005 ONLINE 0 0 0 >> >> after two days of resilvering, the server became unresponsive. I reboot >> the server started to resilver again. after that I also >> detached bad disk. >> #zpool detach tank 433419809408607751 >> >> I have tried zpool clear tank but no success, >> >> Thanks, >> Motty >> On 03/20/2015 03:32 PM, Rainer Duffner wrote: >> >>> Am 20.03.2015 um 23:25 schrieb Motty Cruz : >>>> >>>> Hello Rainer, >>>> >>>> a disk went bad, I had to replace it, soon after replacing the bad HDD >>>> it started the "resilver" process. Process went on and on for hours, >>>> unfortunately server stop responding, I was force to reboot. after >>>> rebooting started "resilver" process again, from zero. I put the HDD >>>> offline replace it "thinking it was a factory bad HHD" started the >>>> "resilver" process again. >>>> >>>> >>> I would assume that the ZFS still thinks it=E2=80=99s the old disk some= how. >>> This is what usually happens then. >>> >>> >>> I=E2=80=99m not sure if an upgraded FreeBSD will help you with your >>> resilver-problem. >>> >>> Can you describe what you did to replace the disk? >>> >>> >>> >>> >> _______________________________________________ >> freebsd-fs@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > > Is there a possibility that the resilvered parts ( port , cable , etc. ) > have hardware failure problems which OS is not able to complete resilveri= ng > or it is seen that part to be resilvered ? > > > > Mehmet Erol Sanliturk > > > > > > --=20 Thanks for your support, Motty