From owner-freebsd-stable@freebsd.org Tue Oct 3 14:29:15 2017 Return-Path: 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 B10ABE3E8A7 for ; Tue, 3 Oct 2017 14:29:15 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0B15176892 for ; Tue, 3 Oct 2017 14:29:14 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA13109; Tue, 03 Oct 2017 17:29:13 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1dzOC9-000KQN-3i; Tue, 03 Oct 2017 17:29:13 +0300 Subject: Re: panic: Solaris(panic): blkptr invalid CHECKSUM1 To: Harry Schmalzbauer Cc: freebsd-stable@FreeBSD.org References: <59CFC6A6.6030600@omnilan.de> <59CFD37A.8080009@omnilan.de> <59D00EE5.7090701@omnilan.de> <493e3eec-53c6-3846-0386-d5d7f4756b11@FreeBSD.org> <59D28550.3070700@omnilan.de> <59D34DA0.802@omnilan.de> <59D39C88.4040501@omnilan.de> From: Andriy Gapon Message-ID: <4c144055-600c-89cf-13d5-0bf161726d1a@FreeBSD.org> Date: Tue, 3 Oct 2017 17:28:17 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <59D39C88.4040501@omnilan.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 14:29:15 -0000 On 03/10/2017 17:19, Harry Schmalzbauer wrote: > Have tried several different txg IDs, but the latest 5 or so lead to the > panic and some other random picked all claim missing devices... > Doh, if I only knew about -T some days ago, when I had all 4 devices > available. I don't think that the error is really about the missing devices. Most likely the real problem is that you are going too far back in history where the data required to import the pool is not present. It's just that there is no special error code to report that condition distinctly, so it gets interpreted as a missing device condition. -F/-X/-T is not guaranteed to work as the old (freed, overwritten) data is not kept indefinitely. -- Andriy Gapon