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:btrfs:btrfs_check [2019/10/22 20:04] – niziaklinux:fs:btrfs:btrfs_check [2023/03/13 10:44] (current) – niziak
Line 1: Line 1:
 +====== btrfs check ======
 +
 +====== checksum error at logical ======
 +
 +<code>
 +BTRFS warning (device sdb4): checksum error at logical 271624814592 on dev /dev/sdb4, physical 270551072768, root 677114, inode 739, offset 14508666880, length 4096, links 1 (path: Windows_10/Snapshots/{8b68a2dd-457e-496f-96df-cf24806dfe2d}.vdi)
 +</code>
 +
 +Reading of mentioned file returns IO error when hit 70% of progress.
 +
 +Corruption detected by periodic scrub. File was not touched for long time, so probably bitrot occurs.
 +This is single SSD data, so there is no mirror of data. There is a backup of data.
 +
 +Possible solution:
 +  * delete file to remove invalid entry from cksum tree and restore from backup
 +  * try playing with mounting with ''ro,rescue=ignoredatacsums'' and copy bad file to another place and delete from source
 +
 +
 +
 +======  corrupt leaf invalid data ref offset ======
 +<code>
 +[4038494.678130] BTRFS critical (device sdb4): corrupt leaf: block=407659724800 slot=84 extent bytenr=406204694528 len=16384 invalid data ref offset, have 25442122467423744 expect aligned to 4096
 +[4038494.678133] BTRFS info (device sdb4): leaf 407659724800 gen 8637875 total ptrs 97 free space 5617 owner 2
 +...
 +[4038494.679249] ref#9: extent data backref root 388257660928 objectid 99389691396278 offset 25442122467423744 count 11927552
 +[4038494.679251] ref#10: (extent 407659724800 has INVALID ref type 192)
 +...
 +[4038494.679393] BTRFS error (device sdb4): block=407659724800 write time tree block corruption detected
 +[4038494.689126] BTRFS: error (device sdb4) in btrfs_commit_transaction:2389: errno=-5 IO failure (Error while writing out transaction)
 +[4038494.689129] BTRFS info (device sdb4): forced readonly
 +[4038494.689131] BTRFS warning (device sdb4): Skipping commit of aborted transaction.
 +[4038494.689132] BTRFS: error (device sdb4) in cleanup_transaction:1944: errno=-5 IO failure
 +</code>
 +
 +<code bash>
 +btrfs check /dev/sdb4
 +
 +ERROR: errors found in fs roots
 +found 338856771584 bytes used, error(s) found
 +</code>
 +
 +<code bash>
 +btrfs rescue zero-log /dev/sdb4
 +btrfs check --repair /dev/mapper/pool2
 +</code>
 +
  
 ====== cache and super generation don't match ====== ====== cache and super generation don't match ======
Line 34: Line 80:
 </code> </code>
  
-Mount filesystem and find files belonging to inodes.+Root number is subvolume id number, so mount subvolume to find files belonging to inodes
 <code bash> <code bash>
-find /mountpoint -inum 418 -print+mount /dev/mapper/pool2 -o subvolid=649 /mountpoint 
 +find /mountpoint -xdev -inum 418 -print
 </code> </code>
 Find will report multiple files located on multiple subvolumes with the same inode. Find will report multiple files located on multiple subvolumes with the same inode.
Line 50: Line 97:
 <code> <code>
  
 +====== Rescan hasn't been ======
 +<code>
 +[7/7] checking quota groups
 +Rescan hasn't been initialized, a difference in qgroup accounting is expected
 +</code>
 +
 +<code bash>
 +btrfs quota rescan /mountpoint
 +</code>