On Mittwoch, 1. März 2017 19:14:07 CET you wrote: > In any > case, I started btrfs-check on the device itself.
*Sigh*, I had to restart it, because I forgot to redirect to a file and quite frankly wasn't expecting this flood of output, but here's a summary of the output after about 2 days: % wc -l btrfs_check_output_20170303.log 1360252 btrfs_check_output_20170303.log % grep -v "backref lost" btrfs_check_output_20170303.log | grep -v "check \ (leaf\|node\) failed" | grep -v "lost its parent" | grep -v "referencer count" checking extents ERROR: block group[3879328546816 1073741824] used 1072840704 but extent items used 1129164800 ERROR: block group[4163870130176 1073741824] used 1072259072 but extent items used 0 ERROR: block group[4223999672320 1073741824] used 1073664000 but extent items used 1074188288 ERROR: block group[4278760505344 1073741824] used 1073377280 but extent items used 1073901568 ERROR: block group[4406535782400 1073741824] used 1073627136 but extent items used 0 ERROR: extent [3830028140544 4096] referencer bytenr mismatch, wanted: 3830028140544, have: 3826183847936 % tail btrfs_check_output_20170303.log ERROR: data extent[3924538445824 4096] backref lost ERROR: data extent[3933464903680 4096] backref lost ERROR: data extent[3924538531840 4096] backref lost ERROR: data extent[3839131480064 4096] backref lost ERROR: data extent[3834701750272 4096] backref lost ERROR: data extent[3873087918080 4096] backref lost ERROR: data extent[3873072283648 4096] backref lost ERROR: data extent[3873088090112 8192] backref lost ERROR: data extent[3873072287744 4096] backref lost ERROR: data extent[3856294449152 4096] backref lost That's right, slowly approaching 1.5 million lines of btrfs-check output! That's *way* more than I ran it the last time this error happened a few weeks ago. Greetings -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
signature.asc
Description: This is a digitally signed message part.
