> If you want checksum and your fs can stand normal RO mount, go RO mount, > and do normal cp, you will get csum error in kernel message if there is any. Also, try btrfsck and btrfs scrub. both help in identifying (and sometimes correcting) csum errors. They would give both logs on console and dmesg for csum error detection and correction. Thanks On Sat, Feb 24, 2018 at 8:36 PM, Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote: > > > On 2018年02月24日 19:13, Marián Mlčoch wrote: >> Hello, >> i requst IRC , but nobody helps. >> My primary question is , how mark restored files with ignored errors. >> >> btrfs restore –iv /vol /restorage >> >> this command restores files like charm but no marker for ok and bad >> files (bad crc , bad ...). WHY? >> This file system isnt newbie , i mean this is urgent feature. > > From btrfs-restore(8): > > btrfs-restore - try to restore files from a *damaged* btrfs filesystem image > > Unless your filesystem is really damaged, you shouldn't use btrfs-restore. > It's used to *salvage* data, no wonder it will bypass all checksum checking. > > If you want checksum and your fs can stand normal RO mount, go RO mount, > and do normal cp, you will get csum error in kernel message if there is any. > >> >> I restore terabytes miloins files , how after this check bad files ??? >> >> Please send me info around this , and add this feature ifnt exist. >> >> I see one way use dump restore filter but how? >> >> btrfs restore –ivD /vol /restorage | grep ??? for bad files >> >> Second question is when files is restored with switch –iv , exist way to >> update metadata in next restore without overwrite? > > What did you mean update metadata? > > Thanks, > Qu > >> This is for restore >> next urgent feature. >> >> Thanks for info Marian. >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
