On 2019/10/3 上午10:18, Andrey Ivanov wrote: > On 03.10.2019 5:00, Qu Wenruo wrote: >>> I think "btrfs check" is looped somewhere. Or not? >> >> You can try "btrfs check --mode=lowmem --repair" as an alternative. > > $ btrfs check -p --mode=lowmem --repair sda4.image.copy > enabling repair mode > WARNING: low-memory mode repair support is only partial > Opening filesystem to check... > Checking filesystem on sda4.image.copy > UUID: a942b8da-e92d-4348-8de9-ded1e5e095ad > [1/7] checking root items (0:00:07 elapsed, 509895 > items checked) > Fixed 0 roots. > No device size related problem found (0:00:47 elapsed, 71347 > items checked) > [2/7] checking extents (0:00:47 elapsed, 71347 > items checked) > cache and super generation don't match, space cache will be invalidated > [3/7] checking free space cache (0:00:00 elapsed) > ERROR: root 5 DIR_INDEX[843063 15] data_len shouldn't be 256sed, 1055 > items checked) > invalid dir item size > ERROR: fail to repair inode 908624 name filterlog.html filetype 1 > ERROR: root 5 DIR ITEM[843063 15] name filterlog.html filetype 1 missing > ERROR: root 5 INODE REF[908624, 843063] name filterlog.html filetype 1 > missing > ERROR: root 5 DIR_INDEX[843063 18] data_len shouldn't be 256 > ERROR: root 5 INODE_ITEM[908627] index 18 name Sent/sbd filetype 2 mismath > ERROR: root 5 DIR_INDEX[843063 18] should contain only one entry > Set isize in inode 843063 root 5 to 318 > ERROR: root 5 EXTENT_DATA[843064 45056] csum missing, have: 0, expected: > 16384 > invalid dir item size > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item size > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item size > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item size > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item size > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item sizets (0:00:13 elapsed, 1297 > items checked) > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item size > invalid dir item size > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > invalid dir item size > invalid dir item size
The problem is the invalid dir item size caused by that bitflip. I'm afraid there are too many unexpected bitflips. But at least you can try to salvage some data. Thanks, Qu > ERROR: fail to repair inode 843091 name Sent.sbd filetype 2 > ERROR: root 5 DIR INDEX[843063 18] missing name Sent.sbd filetype 2 > > ... > > > I think it looped again.
signature.asc
Description: OpenPGP digital signature
