[chris@f24s ~]$ btrfs --version btrfs-progs v4.5.3 [chris@f24s ~]$ sudo btrfs check /dev/mapper/brick1 Checking filesystem on /dev/mapper/brick1 UUID: 30f4724a-9a9f-4a5d-a37d-3e53876bf2e1 checking extents checking free space cache checking fs roots checking csums checking root refs found 423302123916 bytes used err is 0 total csum bytes: 412769428 total tree bytes: 626229248 total fs tree bytes: 160776192 total extent tree bytes: 18219008 btree space waste bytes: 68151409 file data blocks allocated: 1030486196224 referenced 1005660291072
[chris@f24s ~]$ btrfs --version btrfs-progs v4.6.1 [chris@f24s ~]$ sudo btrfs check /dev/mapper/brick1 Checking filesystem on /dev/mapper/brick1 UUID: 30f4724a-9a9f-4a5d-a37d-3e53876bf2e1 checking extents checking free space cache checking fs roots checking csums checking root refs found 423405670400 bytes used err is 0 total csum bytes: 412769428 total tree bytes: 626229248 total fs tree bytes: 160776192 total extent tree bytes: 18219008 btree space waste bytes: 68151409 file data blocks allocated: 1030486196224 referenced 1005660291072 Looks like it's some kind of regression, or just confusing messages meant for developers and not the user. It's sort of annoying that these messages don't come with any advice what the user is supposed to do about them. Curious the found bytes between progs 4.5.3 and 4.6.1 differ... file system was not mounted in between these checks. ---- Chris Murphy -- 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
