meta data for this page
  •  
Book Creator
 Add this page to your book
Book Creator
 Remove this page from your book  

 Manage book(0 page(s))
 Help

This is an old revision of the document!

btrfs check

corrupt leaf invalid data ref offset

[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.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
btrfs check --repair /dev/mapper/pool2

cache and super generation don't match

btrfs check --repair /dev/mapper/pool2
[3/7] checking free space cache
cache and super generation don't match, space cache will be invalidated

It is not real problem, but cache can be cleared: 

btrfs check --repair --clear-space-cache v1 /dev/mapper/pool2
enabling repair mode
Opening filesystem to check...
Checking filesystem on /dev/mapper/pool2
UUID: 947b20e3-bc05-4f85-8989-d19178506209
Free space cache cleared

bad file extent, some csum missing

btrfs check --repair /dev/mapper/pool2
[4/7] checking fs roots
root 649 inode 418 errors 1040, bad file extent, some csum missing
root 649 inode 419 errors 1040, bad file extent, some csum missing
ERROR: errors found in fs roots

Root number is subvolume id number, so mount subvolume to find files belonging to inodes 

mount /dev/mapper/pool2 -o subvolid=649 /mountpoint
find /mountpoint -xdev -inum 418 -print

Find will report multiple files located on multiple subvolumes with the same inode. List subvolumes to get root id: 

btrfs sub list /mountpoint
ID 257 gen 524652 top level 5 path @volume
ID 258 gen 524651 top level 257 path @volume/subvol1
ID 649 gen 524652 top level 257 path @volume/subvol12
<code>

====== Rescan hasn't been ======
<code>
[7/7] checking quota groups
Rescan hasn't been initialized, a difference in qgroup accounting is expected
btrfs quota rescan /mountpoint