Date: Tue, 10 Apr 2018 23:51:09 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Andrew Gallatin <gallatin@cs.duke.edu>, Allan Jude <allanjude@FreeBSD.org>, freebsd-current@FreeBSD.org Subject: Re: Odd ZFS boot module issue on r332158 Message-ID: <ffe4e081-a087-bfd8-3063-3b4cbbb8b13e@FreeBSD.org> In-Reply-To: <ed5be5d5-9ce0-c8f0-90a3-1ba46dd87637@cs.duke.edu> References: <b772ee51-b27c-6591-c925-b4abd19678e8@cs.duke.edu> <935ad20e-017c-5c34-61b4-9db58788a663@freebsd.org> <5316e5ea-17a2-2f23-3c88-1671f41b5642@cs.duke.edu> <00fd72d0-cb41-eaf7-347e-6f3423bb6008@FreeBSD.org> <ed5be5d5-9ce0-c8f0-90a3-1ba46dd87637@cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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*] <ZFS filesystem name> <file's inode number> >> 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. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ffe4e081-a087-bfd8-3063-3b4cbbb8b13e>