https://bugzilla.kernel.org/show_bug.cgi?id=200871
--- Comment #14 from Chao Yu (c...@kernel.org) --- (In reply to Stathis Maneas from comment #13) > Indeed, I can tell what is the block address in which the updated inode is > going to be stored using both dump.f2fs and the output of the SSA blocks. OK, let me catch the address where inode block will update to, and try your case again. > > Then, the file system gets initialized from scratch before the operation is > executed once again. Based on the file system's deterministic behaviour, > when the operation is repeated, then the updated inode will eventually be > stored into the same block. In your case, once inode udpates, LBA of inode block will change to LBA+1. We can record finial LBA of inode block locates in first round, then in next round, we can inject error directly in fixed LBA. > > Please let me know if my understanding is accurate. -- You are receiving this mail because: You are watching the assignee of the bug. _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
