From owner-freebsd-fs@freebsd.org Mon May 30 07:11:44 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9B5BB5446E for ; Mon, 30 May 2016 07:11:44 +0000 (UTC) (envelope-from blackcatzilla@gmail.com) Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (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 9915B1A3C for ; Mon, 30 May 2016 07:11:44 +0000 (UTC) (envelope-from blackcatzilla@gmail.com) Received: by mail-ig0-x22c.google.com with SMTP id ct2so25810622igb.0 for ; Mon, 30 May 2016 00:11:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bYMug2SN6rYxmHEjGLFqn+8l86geXUecNH7Ja75aGyk=; b=c8ZrigFvg26EW7YhBY0s87c0zy1K5SNx3YbKiiuSxIOGIlokWh1gii/W7Z6pxXQdzv nVbL6WcNUTpX97jRm9wc7fHkD8kShHyVYD4rcZv8oapOgOqntYT+qFOqSB4miT6euTEx bZpvHGGMMaYXhK/areJQdYS8hvi4m7PQpWlOcWVLzUsb4kfMQftCBddU2iU2YumDEKL4 6IONxZu5zJlgPMfbf+EzXJ5hVIVHkzDrNkw7ZDphskvfEnkbBY7lsJg7fl1+78Nkfmkx piIvcS7cT7Ex4Ttdue7beDzbTMVx0pw0DUBlyIicswybJksgZaaEgSE2YlUb3wcLjC3x PNTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bYMug2SN6rYxmHEjGLFqn+8l86geXUecNH7Ja75aGyk=; b=P7urDgIBpOHWXjvNMG4d4UD0rTwKrIzYJYpfT9njRc3en3CHJ0J2YnZGq+5k4he/tP 7Lmgb7s0KUmcQvS1ftq5X7cqqTGK0WPQsZgWl921xVvsNkTX4hTiaOpuYtYizeFl28v9 gIhr5Ug+sBoxlgLOEXfIacDYJU8sFWrCO3FAWxitv11hOVVHeG7ek9f8yd1HRvxEKxbp CCqzo5qmCxjNtEFuPKztIgjBzhC3J6INzkU1wYGZjTFj0ZWLfWkVU82q3A/NmxX0pVFa Pz2HNBnsXz/VHUCR/09O+pafW10Ykva6a81zdsULNRZX9+ImOO3ADC/LqfJElMq8pfMW 05nQ== X-Gm-Message-State: ALyK8tJ659WNWp613+b+croTUEYo5FPsMpVmqj/HRK3y+cF+1ZS5WwQWXJmrIl8cpGOjRz9N813btSrFsN7yVQ== X-Received: by 10.50.18.198 with SMTP id y6mr6122097igd.86.1464592303966; Mon, 30 May 2016 00:11:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.36.46.201 with HTTP; Mon, 30 May 2016 00:11:24 -0700 (PDT) In-Reply-To: <574BD273.5040401@gmail.com> References: <574BD273.5040401@gmail.com> From: BlackCat Date: Mon, 30 May 2016 10:11:24 +0300 Message-ID: Subject: Re: ZFS - RAIDZ1 Recovery (Evgeny Sam) To: esamorokov Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2016 07:11:45 -0000 Hello Evgeny, 2016-05-30 8:41 GMT+03:00 esamorokov : > I think this table should make it a little bit clear, i hope :) > > Drive State #1 State #2 State #3 State #4 > ada1 (ada1p2) OK OK DISCONNECTED CONNECTED (OLD POOL) > ada2 (ada2p2) OK OK OK OK (new Pool) > ada3 (ada3p2) OK FAILED REPLACED CONNECTED FAILED DRIVE (OLD POOL) > ZH_VOL (pool) OK DEGRADED DESTROYED RECREATED > > Thank you, > Evgeny. > > On 05/29/2016 11:31 AM, BlackCat wrote: > > Evgeny, > > I still can not figure, what happened to ada2 drive. You say that the > broken drive is ada3 and you attempt to replace it. But then something > went wrong, you attempted to recover the pool but without success. > After that you attach original ada3 drive back to machine and write > your initial post to this mailing list? > > Log, which you attached to your initial post, shows that you attempted > to remove _ada2_ from the pool, then you create new pool with the same > name and add _ada2p2_ to it. zfs added _ada2p2_ to new pool without > any warnings. Then you try to add _ada1p2_ to the new pool and zfs > rejects to do that since it suspects that _ada1p2_ already belongs to > other pool. > > The dump of labels from your message shows that: > * _adad1p2 is partially Ok (labels at the end of partition are missed) > * _ada2p2 is Ok, but belongs to new pool > * _ada3p2_ is Ok: all labels exists and belongs to old pool > > I am really puzzled what happened with each of your drives. > Thank you for this nice formatted table, it perfectly summarize states of drives. But I still can not figure how drives change from one state to another, especially how could you attach ada2p2 to new pool without detaching it from old one. Ok if no one else would suggest any better solution, let's keep one's fingers crossed and try to import pool as-is (in any case you have copies of your original drives): # zpool import -o ro -fF 2918670121059000644 zh_vol_old -- BR BC