Re: Corrupted filesystem, looking for guidance

2019-02-12 Thread Artem Mygaiev
Have same issue (RAID5 over 4 disks): https://marc.info/?l=linux-btrfs&m=154815802313248&w=2 Having perfectly healthy HDDs it seem to be caused by some bit flips in SDRAM which is non-ECC in my case, unfortunately. Tried --repair, didn't helped, same for --init-csum-tree. Now using fs in ro mode (

btrfs RAID5 corrupted fs restore? data is OK

2019-01-22 Thread Artem Mygaiev
03606] BTRFS info (device sdf): no csum found for inode 13730923 start 1619410944 [81685.703608] BTRFS critical (device sdf): unable to find logical 144149573654298624 length 4096 [81685.703772] BTRFS critical (device sdf): unable to find logical 144149573654298624 length 4096 Any help is appreciated. Best regards, Artem Mygaiev

btrfs RAID5 corrupted fs restore? data is OK

2019-01-14 Thread Artem Mygaiev
Hello I am running Ubuntu Server 16.04 LTS with HWE stack (4.18 kernel). System is running on 2 protected SSDs in RAID1 mode, separate SSD assigned for swap and media download / processing cache and main data storage partition (read intense but not write intense, archive-like) is 32TB RAID5 btrfs