meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
linux:fs:zfs:issues:dva_0_has_invalid_offset [2021/05/21 16:11] – niziaklinux:fs:zfs:issues:dva_0_has_invalid_offset [2021/05/24 19:10] (current) – niziak
Line 37: Line 37:
  
 <code bash> <code bash>
-zdb -AAA -bbcsvL <zfs_pool>+zdb -AAA -bbbcsvL <zfs_pool>
 </code> </code>
 +
 +And sometimes it shows some errors during reading:
 +
 +<code>
 +zdb_blkptr_cb: Got error 52 reading <259, 75932, 0, 17> DVA[0]=<0:158039e9000:6000> [L0 ZFS plain file] fletcher4 lz4 unencrypted LE contiguous unique single size=20000L/6000P birth=62707L/62707P fill=1 cksum=516dd1ace1c:414cbfc202333b:af36411a2766c4f:7bc4d6777673687b -- skipping
 +</code>
 +
  
 ====== Find problematic file / volume ====== ====== Find problematic file / volume ======
Line 73: Line 80:
 mkdir /rpool mkdir /rpool
 zpool import -f -R /rpool rpool -o readonly=on zpool import -f -R /rpool rpool -o readonly=on
-<code>+ 
 +</code>
  
   * ''-e'' operate on exported pool   * ''-e'' operate on exported pool
Line 95: Line 103:
 If bad data has a correct checksum, then at present ZFS cannot fix it. Sometimes it can recognize that the data is bad and report an error, sometimes it has no option but to panic, but sometimes it cannot even tell if it's bad data. If bad data has a correct checksum, then at present ZFS cannot fix it. Sometimes it can recognize that the data is bad and report an error, sometimes it has no option but to panic, but sometimes it cannot even tell if it's bad data.
 </code> </code>
 +