From owner-freebsd-current@freebsd.org Tue May 1 14:34:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9725FAD064 for ; Tue, 1 May 2018 14:34:57 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6865375371; Tue, 1 May 2018 14:34:57 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from [192.168.200.3] (c-73-216-227-39.hsd1.va.comcast.net [73.216.227.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: gallatin) by duke.cs.duke.edu (Postfix) with ESMTPSA id 7034427001F8; Tue, 1 May 2018 10:34:50 -0400 (EDT) DMARC-Filter: OpenDMARC Filter v1.3.1 duke.cs.duke.edu 7034427001F8 Authentication-Results: duke.cs.duke.edu; dmarc=none header.from=cs.duke.edu DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cs.duke.edu; s=mail0816; t=1525185291; bh=JBd+stOZw0q3CdEBnOOfROjZoSyLqQ8dtHBvraHpPUE=; h=Subject:To:From:Date:From; b=VbPRQ0zyThifteSYtoH8/4pRIVjx2gF+inX4w4O0WVJj3KmXBGf0w9JulmmdfO+be 4UursmdRQonalNV730oDLpA8hUtss2WV5ZNqyzrtlLfHxMXARIQZKiJVvVLKwy2JrR YRDv7Tl7xC2Fx+UrR3QwoyFDMGKefMlK//Kr3EbOeySFDhxo3RW7vH0iQI0mXZwmym mZP8Pw7Moz015PIqKFzx5c+M0tv0+zUPPVhKvr3hIK15/2r0H5ZMjcKUMiOtmSilvd hLYjzCLEKv/ulrglqs6OIUBy7yQmN1jcGtP2roZTrJ1yZuS78fGaUPgfNjV2WEJMfo 8V+3ye5SMjJXw== Subject: Re: Odd ZFS boot module issue on r332158 To: Andriy Gapon , Allan Jude , freebsd-current@FreeBSD.org References: <935ad20e-017c-5c34-61b4-9db58788a663@freebsd.org> <5316e5ea-17a2-2f23-3c88-1671f41b5642@cs.duke.edu> <00fd72d0-cb41-eaf7-347e-6f3423bb6008@FreeBSD.org> From: Andrew Gallatin Message-ID: Date: Tue, 1 May 2018 10:34:49 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 14:34:58 -0000 On 04/10/18 16:51, Andriy Gapon wrote: > On 10/04/2018 22:48, Andrew Gallatin wrote: >> On 04/10/18 11:25, Andriy Gapon wrote: >>> On 10/04/2018 15:27, Andrew Gallatin wrote: >>>> Is there something like tools/diag/prtblknos for ZFS? >>> >>> zdb. >>> >>> It has a manual page, but in the case like this you typically want to run >>> zdb -d[d*] >>> Add d-s until you get all the information you want. >>> >>> It looks like five d-s is needed to get individual blocks reported. >>> >> >> Thanks for the instructions! >> >> How do I interpret this output: > [snip] >>                0 L1  1:1f01016c000:1000 20000L/1000P F=3 B=16769122/16769122 >>                0  L0 1:1f00f9e3000:20000 20000L/20000P F=1 B=16769122/16769122 >>            20000  L0 1:1f00fa03000:20000 20000L/20000P F=1 B=16769122/16769122 >>            40000  L0 1:1f00fa23000:20000 20000L/20000P F=1 B=16769122/16769122 > > The first number is an offset within the file (hex); Lx is a block level where > L0 is a data block, L1 is an indirect block just above data blocks, etc; x:y:z > is a (top-level) vdev number, a block offset on disk (hex) and a block size on > disk(hex); the rest is not as important. > > The quoted offsets appear to be just below 2TB. > > > Are these byte addresses? Or do I need to multiply by the blocksize to determine the offset into the file? From your "just below 2TB" I'm assuming byte addresses. This is a supermicro board X10SRA. They do have a f/w update, but I suspect it is mainly just for new ucode. Of course there is no changelong. I guess I'll try it if/when I'm totally unable to boot into a new BE. I just checked, and my EFI loader is ~1 year old, I should probably try updating that too. FWIW, I just updated to head again, and I see a problem with just one module, which looks like the attached. Drew