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 GaponReceived on Tue Apr 10 2018 - 18:59:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC