On Tue, Sep 24, 2019 at 3:29 AM <hoegge@xxxxxxxxx> wrote: > > # btrfs fi show > gives no result - not when adding path either > > # btrfs fi df /volume1 > Data, single: total=4.38TiB, used=4.30TiB > System, DUP: total=8.00MiB, used=96.00KiB > System, single: total=4.00MiB, used=0.00B > Metadata, DUP: total=89.50GiB, used=6.63GiB > Metadata, single: total=8.00MiB, used=0.00B > GlobalReserve, single: total=512.00MiB, used=0.00B > > Here is the log: > https://send.firefox.com/download/5a19aee66a42c04e/#PTt0UkT53Wrxe9EjCQfrWA (password in separate e-mail) > I have removed a few mac-addresses and things before a certain data (that contained all other kinds of info). Let me know if it is too little. I think they were having problems, I kept getting 502 errors, and then reached the download retries limit I bet. > > Concerning restoring files - I should have all originals backed up, so assume I can just delete the bad ones and restore the originals. That would take care also of all the checksums, right? But BTRFS does not do anything to prevent the bad blocks from being used again, right? We don't know if they're bad sectors or not yet. That would be shown by libata as a read or write error. A read error, md will handle by reconstructing the data from parity and write it back to the drive. And at that time the drive firmware will determine if the write succeeds or not and if not it'll internally mark that physical sector as bad and remap the LBA for that sector to a different reserve physical sector. > I'll ask Synology about their stack. > > I can't find sysfs on the system - should it be mounted uner /sys ? This is what I have: # echo check > /sys/block/mdX/md/sync_action replace the X with the raid you're checking - this is a bit different if they're using LVM raid. -- Chris Murphy
