On 2018年01月16日 18:49, Sebastian Andrzej Siewior wrote: > On 2018-01-16 18:22:14 [+0800], Qu Wenruo wrote: >> Btrfs check is always recommended before really mount it. > > # btrfs check -p /dev/sdb4 > Checking filesystem on /dev/sdb4 > UUID: b3bfb56e-d445-4335-93f0-c1fb2d1f6df1 > checking extents [O] > cache and super generation don't match, space cache will be invalidated > root 5 inode 57648595 errors 200, dir isize wrong
This is a very minor problem. btrfs check --repair should handle it without problem. Or just ignore it if you don't trust check --repair. > > ERROR: errors found in fs roots > found 64009740288 bytes used, error(s) found > total csum bytes: 61644600 > total tree bytes: 865746944 > total fs tree bytes: 693469184 > total extent tree bytes: 84905984 > btree space waste bytes: 225096302 > file data blocks allocated: 63203807232 > referenced 63142268928 > >> However as long as there is no other problem, btrfs check should not >> report anything wrong. > > Is it important to note that the filesystem is a raid1 one? Nope, the repair code handles any chunk profile well. Thanks, Qu > >> Thanks, >> Qu > > Sebastian >
signature.asc
Description: OpenPGP digital signature
