From owner-freebsd-current@freebsd.org Tue May 1 18:14:59 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 D3F2EFB2C89 for ; Tue, 1 May 2018 18:14:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 75733852A3; Tue, 1 May 2018 18:14:58 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P8200C0078CCB00@st13p35im-asmtp001.me.com>; Tue, 01 May 2018 17:14:45 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1525194885; bh=Oqqc0X9ejxcystNubgbEU1uONgKMGSxdGwWgxZbQwO8=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=CuqxyJD43LIsyMFzAb1X64qs2hJz14gDx4zi0USohcdTzjrhjSbfmvP/CNkCwF+Ku aeYfqwZe7f9ttB/yG/u3NH7bIm0nGTpxpRmom7DRdUH+HOrL1BxpGA1iWDbZqnlIrV CdFFtFTX2hPaTlmJ72UOAIC18tEo2VARkqyuUOxUXy5pVjtBjIwiEv8A6Iy+AVEu/K JPkL/lWXkzmGX6npbNb/GsfRFSDpBbkakgSGKR9mAEKAPiVps/xL91svmhVwXtN3ng 6Hh2k/vdJ3xjSV6G0nG7xNDs//ewpnpAOD+tpmm8ChkCApcHJcWptR3U0Tnv30gF8n S9uXZnU3Zur0A== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P82004AB7WG5J10@st13p35im-asmtp001.me.com>; Tue, 01 May 2018 17:14:43 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-05-01_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1805010168 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: Odd ZFS boot module issue on r332158 Date: Tue, 01 May 2018 20:14:40 +0300 In-reply-to: Cc: Andriy Gapon , Allan Jude , freebsd-current@FreeBSD.org To: Andrew Gallatin References: <935ad20e-017c-5c34-61b4-9db58788a663@freebsd.org> <5316e5ea-17a2-2f23-3c88-1671f41b5642@cs.duke.edu> <00fd72d0-cb41-eaf7-347e-6f3423bb6008@FreeBSD.org> X-Mailer: Apple Mail (2.3445.6.18) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 18:14:59 -0000 > On 1 May 2018, at 17:34, Andrew Gallatin wrote: >=20 > 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? >>>>=20 >>>> zdb. >>>>=20 >>>> 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. >>>>=20 >>>> It looks like five d-s is needed to get individual blocks reported. >>>>=20 >>>=20 >>> Thanks for the instructions! >>>=20 >>> How do I interpret this output: >> [snip] >>> 0 L1 1:1f01016c000:1000 20000L/1000P F=3D3 = B=3D16769122/16769122 >>> 0 L0 1:1f00f9e3000:20000 20000L/20000P F=3D1 = B=3D16769122/16769122 >>> 20000 L0 1:1f00fa03000:20000 20000L/20000P F=3D1 = B=3D16769122/16769122 >>> 40000 L0 1:1f00fa23000:20000 20000L/20000P F=3D1 = B=3D16769122/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. >=20 > Are these byte addresses? Or do I need to multiply by the blocksize = to determine the offset into the file? =46rom your "just below 2TB" I'm = assuming byte addresses. >=20 > 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. >=20 > I just checked, and my EFI loader is ~1 year old, I should probably = try > updating that too. >=20 > FWIW, I just updated to head again, and I see a problem with just one > module, which looks like the attached. >=20 could you test https://reviews.freebsd.org/D15207 = ? rgds, toomas