From owner-freebsd-stable@freebsd.org Tue Oct 3 14:39:48 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 0E414E3ECC3 for ; Tue, 3 Oct 2017 14:39:48 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9F6E176EFA; Tue, 3 Oct 2017 14:39:47 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id v93Edjfm000131; Tue, 3 Oct 2017 16:39:45 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id AA83426E; Tue, 3 Oct 2017 16:39:45 +0200 (CEST) Message-ID: <59D3A131.8040803@omnilan.de> Date: Tue, 03 Oct 2017 16:39:45 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Andriy Gapon CC: freebsd-stable@FreeBSD.org Subject: Re: panic: Solaris(panic): blkptr invalid CHECKSUM1 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> <4c144055-600c-89cf-13d5-0bf161726d1a@FreeBSD.org> In-Reply-To: <4c144055-600c-89cf-13d5-0bf161726d1a@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 03 Oct 2017 16:39:45 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) 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:39:48 -0000 Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 16:28 (localtime): > 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. Sounds reasonable. When the RAM-corruption happened, a live update was started, where several pool availability checks were done. No data write. Last data write were view KBytes some minutes before the corruption, and the last significant ammount written to that pool was long time before that. So I still have hope to find an importable txg ID. Are they strictly serialized? Dou you know any other possibility to get data from a dataset (by objetct id) without importing the whole pool? zdz successfully checks the one datset (object ID) I'm interested in; the rest of the pool isnt much an issue... Thank you very much for your help! -harry