From owner-freebsd-fs@FreeBSD.ORG Sat Mar 21 05:23:55 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 30922E65 for ; Sat, 21 Mar 2015 05:23:55 +0000 (UTC) Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) (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 DA5F0697 for ; Sat, 21 Mar 2015 05:23:54 +0000 (UTC) Received: by yhim52 with SMTP id m52so20284970yhi.2 for ; Fri, 20 Mar 2015 22:23:54 -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=LDe6pF9zLS8WU2amyTR5tzQi6iTN+vfPwRiqs4ic8Kw=; b=mKtQeuSLSookPEmql6g8sS+lkNRQRbqa+K3Py6pl+3VQLjs6y49D+oUN780A1IJwyU y+iFz9BzAep0LGU5+FsANeu0uraNwnisr0gW2YCylynDo71Ah+QOTf7de5x0NV0xXxLG DM6tWLER/uk2rvy6A4hXfb6Os0+WOE+8AquHs1g+d5/cDwSVkcNZ8x1uI/83G8wio78+ C2hfDq82SRtYuU+l+pBwE6oW25DaqL5j7jfmTwbibp+L07+uLUVoEfASVNWkKISceaIM ccJzFpUqyRCJi/ThSllCmbQLTq6nmWmO6Uqx+PmHrlKURTvTHno7o5zX0ZusRcQ0Ylgf tMXA== MIME-Version: 1.0 X-Received: by 10.236.26.143 with SMTP id c15mr85742347yha.192.1426915433958; Fri, 20 Mar 2015 22:23:53 -0700 (PDT) Received: by 10.170.60.69 with HTTP; Fri, 20 Mar 2015 22:23:53 -0700 (PDT) In-Reply-To: <550CA2BF.2070406@gmail.com> 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: Fri, 20 Mar 2015 22:23:53 -0700 Message-ID: Subject: Re: zfs on FreeBSD 8.2 64bit stuck in "One or more devices is currently being resilvered" From: Mehmet Erol Sanliturk To: Motty Cruz 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 05:23:55 -0000 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 someh= ow. >> 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 resilvering or it is seen that part to be resilvered ? Mehmet Erol Sanliturk