On 07/31/2016 02:13 AM, Hans van Kranenburg wrote: > On 07/31/2016 01:18 AM, Hans van Kranenburg wrote: >> blahblahblahblahblalahba >> >> Doing a btrfs check now on the block device, will fup with the output. >> > > Output so far: > > -# btrfs check /dev/xvdc 2>&1 | tee btrfs-check-xvdc > checking extents > ref mismatch on [3649516437504 16384] extent item 0, found 1 > Backref 3649516437504 parent 4100606377984 root 4100606377984 not found > in extent tree > backpointer mismatch on [3649516437504 16384] > owner ref check failed [3649516437504 16384] > ref mismatch on [4091477114880 16384] extent item 0, found 1 [...] > ref mismatch on [4103438221312 16384] extent item 0, found 1 > Backref 4103438221312 parent 4100606377984 root 4100606377984 not found > in extent tree > backpointer mismatch on [4103438221312 16384] > owner ref check failed [4103438221312 16384] > checking free space tree > checking fs roots > [...] >
Yay... checking free space tree checking fs roots checking csums checking root refs Checking filesystem on /dev/xvdc UUID: 37c37071-4080-418b-a27a-29d7d15ec00d cache and super generation don't match, space cache will be invalidated found 1877500653751 bytes used err is 0 total csum bytes: 1805473324 total tree bytes: 28709109760 total fs tree bytes: 26028736512 total extent tree bytes: 589660160 btree space waste bytes: 4777447505 file data blocks allocated: 2809995116544 referenced 2809992523776 -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenb...@mendix.com | www.mendix.com -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
