From owner-freebsd-stable@freebsd.org  Sat Jul 22 19:28:23 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 A377DDAB6E8
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sat, 22 Jul 2017 19:28:23 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client CN "mail.norma.perm.ru",
 Issuer "Vivat-Trade UNIX Root CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1633D3B63
 for <freebsd-stable@freebsd.org>; Sat, 22 Jul 2017 19:28:22 +0000 (UTC)
 (envelope-from emz@norma.perm.ru)
Received: from [IPv6:2a02:2698:26:9b0e:71b3:748:aac9:67e1]
 (dynamic-2a02-2698-26-0-0.perm.ertelecom.ru
 [IPv6:2a02:2698:26:9b0e:71b3:748:aac9:67e1] (may be forged))
 (authenticated bits=0)
 by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPSA id v6MJSFD0098892
 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-stable@freebsd.org>; Sun, 23 Jul 2017 00:28:17 +0500 (YEKT)
 (envelope-from emz@norma.perm.ru)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key;
 t=1500751697; bh=FO4XLJ1haa/yTNxW5CR/gyiVnawxUnuhRpilFXpmyiE=;
 h=Subject:To:References:From:Date:In-Reply-To;
 b=DrGYhICgwdTjsBiQtDFnTpK8j2ZxLLJY13c0+4RqZ27UmM7gOFOVLpf0I6/4Not/X
 eBKHkJh6uCzQDj8uWJcs/OzU8N91oc8Yulv95Dpixs50co/c7a3dm6/zaF8hbmIzEa
 aWKI4htu1tVaNWAFJ45mEW0uW1p9zHTcpyhCSg14=
Subject: Re: cannot destroy faulty zvol
To: freebsd-stable@freebsd.org
References: <73ed4a4d-a156-457a-37d3-12d7ef4f89b9@norma.perm.ru>
From: "Eugene M. Zheganin" <emz@norma.perm.ru>
Message-ID: <c604f49c-f47e-bc73-ea1c-93943053f60e@norma.perm.ru>
Date: Sun, 23 Jul 2017 00:28:01 +0500
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <73ed4a4d-a156-457a-37d3-12d7ef4f89b9@norma.perm.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2017 19:28:23 -0000

Hi,

On 22.07.2017 17:08, Eugene M. Zheganin wrote:
>
> is this weird error "cannot destroy: already exists" related to the 
> fact that the zvol is faulty ? Does it indicate that metadata is 
> probably faulty too ? Anyway, is there a way to destroy this dataset ?
Follow-up: I sent a similar zvol of the thexactly same size into the 
faulty one, zpool errors are gone, still cannot destroy the zvol. Is 
this a zfs bug ?

Eugene.