https://bugzilla.kernel.org/show_bug.cgi?id=200635
--- Comment #4 from Chao Yu (c...@kernel.org) --- Thanks for reminding that, IMO, yes, after we enable superblock checksum feature, we can know which sb is corrupted, and try to recovery corrupted sb with another good one. Although, for your case, I guess the only corrupted field is f2fs_super_block.cp_payload, which should be 0 instead of 1, as it can be correctly hinted from checkpoint package fields that are under checksum protection already. So, w/o sb checksum feature, do you wish that we can have a try with recovering sb fields from checkpoint pack? -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
