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/18 09:48] – 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 62: Line 69:
 System stuck in bootloop. System stuck in bootloop.
  
-Boot from Live USB with ZFS Support (Ubuntu has 0.8.3 ZOL). +  * Boot from Live USB with ZFS Support (Ubuntu has 0.8.3 ZOL). 
-stop zfs-zer service +  * stop zfs-zed service 
-rmmod zfs +  * ''rmmod zfs'' 
-modprobe zfs zfs_recover=1+  * ''modprobe zfs zfs_recover=1''
  
 +It doesn't help. After hit ZFS warning insread of panic, ZFS informs about unrecoverable error and pool is suspended.
 +
 +Last possibility is to boot from Live system from USB and  copy all data to other zpool and recreate ''rpool'':
 +<code bash>
 mkdir /rpool mkdir /rpool
 zpool import -f -R /rpool rpool -o readonly=on zpool import -f -R /rpool rpool -o readonly=on
  
 +</code>
 +
 +  * ''-e'' operate on exported pool
 +  * ''-L'' Disable leak detection and the loading of space maps.  By default, zdb verifies that all non-free blocks are referenced, which can be very expensive.
 +<code bash>
 zdb -e -bcsvL rpool zdb -e -bcsvL rpool
 +</code>
  
  
Line 86: 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>
 +