Re: check: "warning line 4144"
On 2017年10月25日 14:54, Tom Hale wrote: > > > On 19/10/17 15:58, Qu Wenruo wrote: >> On 2017年10月19日 16:53, Tom Hale wrote: >>> In running btrfs check, I got the following message: >>> >>> warning line 4144 >>> >>> Could this be a little more descriptive? >>> >>> * Does it mean I should rebuild my FS from scratch? >>> * Is there anything I can do to remove this warning? >>> >> >> --repair is dangerous, use it unless you're sure the problem can be >> fixed by it. >> >> What's the output of "btrfs check" and "btrfs check --mode=lowmem" after >> doing the repair? > > Plain `btrfs check` gives me: > > checking extents > checking free space cache > checking fs roots > checking csums > checking root refs > Checking filesystem on /dev/mapper/vg_svelte-home > UUID: 93722fa7-7e8f-418a-a7ca-080aca8db94b > found 192318169092 bytes used, no error found > total csum bytes: 185482112 > total tree bytes: 1924104192 > total fs tree bytes: 1597767680 > total extent tree bytes: 102514688 > btree space waste bytes: 325265468 > file data blocks allocated: 6169163599872 > referenced 575636733952 At least your fs is good to go. > > Could somebody please answer my initial questions about this obscure > warning? Only two places will output this warning, and they are both used by original mode. So at least if you're using lowmem mode, you won't encounter this warning line. And for your line at 4144, git blames shows it's from the ancient day of btrfs-progs. According to a quick glance of it, it seems that during the check, it encountered a shared node, which is quite common for fs with snapshots, but it doesn't do the cleanup correctly. I think it's caused by some extent tree problem, which lacks some backref or has some mismatch backref, to cause the shared node checking code behaved unexpectedly. (runtime glitch) Thanks, Qu > > Thanks, > signature.asc Description: OpenPGP digital signature
Re: check: "warning line 4144"
On 19/10/17 15:58, Qu Wenruo wrote: > On 2017年10月19日 16:53, Tom Hale wrote: >> In running btrfs check, I got the following message: >> >> warning line 4144 >> >> Could this be a little more descriptive? >> >> * Does it mean I should rebuild my FS from scratch? >> * Is there anything I can do to remove this warning? >> > > --repair is dangerous, use it unless you're sure the problem can be > fixed by it. > > What's the output of "btrfs check" and "btrfs check --mode=lowmem" after > doing the repair? Plain `btrfs check` gives me: checking extents checking free space cache checking fs roots checking csums checking root refs Checking filesystem on /dev/mapper/vg_svelte-home UUID: 93722fa7-7e8f-418a-a7ca-080aca8db94b found 192318169092 bytes used, no error found total csum bytes: 185482112 total tree bytes: 1924104192 total fs tree bytes: 1597767680 total extent tree bytes: 102514688 btree space waste bytes: 325265468 file data blocks allocated: 6169163599872 referenced 575636733952 Could somebody please answer my initial questions about this obscure warning? Thanks, -- Tom Hale -- 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
Re: check: "warning line 4144"
On 2017年10月19日 16:53, Tom Hale wrote: > In running btrfs check, I got the following message: > > warning line 4144 > > Could this be a little more descriptive? > > * Does it mean I should rebuild my FS from scratch? > * Is there anything I can do to remove this warning? > > Complete output below: > > == > $ sudo btrfs check --repair -p /dev/mapper/fix-backup --repair is dangerous, use it unless you're sure the problem can be fixed by it. What's the output of "btrfs check" and "btrfs check --mode=lowmem" after doing the repair? Thanks, Qu > enabling repair mode > Checking filesystem on /dev/mapper/fix-backup > UUID: 0f5b7713-929d-41e7-b214-32500b5c77fc > ref mismatch on [195215851520 16384] extent item 0, found 1 > Backref 195215851520 parent 1463 root 1463 not found in extent tree > backpointer mismatch on [195215851520 16384] > owner ref check failed [195215851520 16384] > repair deleting extent record: key 195215851520 169 1 > adding new tree backref on start 195215851520 len 16384 parent 0 root 1463 > Repaired extent references for 195215851520 > > Fixed 0 roots. > cache and super generation don't match, space cache will be invalidated > warning line 4144 [o] > > checking csums > checking root refs > found 294913892352 bytes used, no error found > total csum bytes: 282955440 > total tree bytes: 5166727168 > total fs tree bytes: 4489232384 > total extent tree bytes: 353075200 > btree space waste bytes: 886405127 > file data blocks allocated: 7930446508032 > referenced 1126675288064 > == > -- 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
check: "warning line 4144"
In running btrfs check, I got the following message: warning line 4144 Could this be a little more descriptive? * Does it mean I should rebuild my FS from scratch? * Is there anything I can do to remove this warning? Complete output below: == $ sudo btrfs check --repair -p /dev/mapper/fix-backup enabling repair mode Checking filesystem on /dev/mapper/fix-backup UUID: 0f5b7713-929d-41e7-b214-32500b5c77fc ref mismatch on [195215851520 16384] extent item 0, found 1 Backref 195215851520 parent 1463 root 1463 not found in extent tree backpointer mismatch on [195215851520 16384] owner ref check failed [195215851520 16384] repair deleting extent record: key 195215851520 169 1 adding new tree backref on start 195215851520 len 16384 parent 0 root 1463 Repaired extent references for 195215851520 Fixed 0 roots. cache and super generation don't match, space cache will be invalidated warning line 4144 [o] checking csums checking root refs found 294913892352 bytes used, no error found total csum bytes: 282955440 total tree bytes: 5166727168 total fs tree bytes: 4489232384 total extent tree bytes: 353075200 btree space waste bytes: 886405127 file data blocks allocated: 7930446508032 referenced 1126675288064 == -- Tom Hale -- 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
