Only one file was erroneous, but now it's not just the erroneous file that has disappeared, over eight thousand other files have disappeared as well. The disappeared files seem to be those that were recently modified or newly created.
I create a snapshot every day, and each snapshot is kept for a month. Those over eight thousand files have disappeared from all the snapshots. On August 20, 2023 5:03:12 PM UTC, piorunz <pior...@gmx.com> wrote: >Ok. You said file with error has disappeared from the system. Is that >still the case? If there anything you need to "recover"? If file with >error is already gone, then you should have no more errors while reading >the drive to backup it. > > >On 20/08/2023 13:24, Longhao.Chen wrote: >> Thanks for your reply. >> >> The disk is a 1TB Samsung SSD with less than 4TiB written, the SMART is >> completely normal with no errors. I suspect that this error may have been >> caused by random bit flipping in the memory (DDR4 non-ECC memory). >> >> I just want to fix the checksum error (because the file with the checksum >> error is not important), so I used the command 'btrfs check >> --init-csum-tree'. >> >> 于 2023年8月20日 GMT+08:00 下午8:12:31, piorunz <pior...@gmx.com> 写到: >>> On 20/08/2023 12:11, Longhao.Chen wrote: >>>> Thanks for your reply. I previously read in the btrfs documentation that >>>> "when repairing the file system, it is advisable to choose a newer >>>> kernel", so I used Ubuntu's livecd for the repair. >>> >>> First of all, did you found the cause of this unrepairable error? >>> Is HDD failing? What SMART data say? >>> You should not repair or use medium which is failing, it may cause >>> further damage. >>> >>> -- >>> With kindest regards, Piotr. >>> >>> ⢀⣴⠾⠻⢶⣦⠀ >>> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system >>> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ >>> ⠈⠳⣄⠀⠀⠀⠀ >>> >> > >-- >With kindest regards, Piotr. > >⢀⣴⠾⠻⢶⣦⠀ >⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system >⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ >⠈⠳⣄⠀⠀⠀⠀ >
