| commit | 953a3e27e10fc6acb480801ea47197d0270d735e | [log] [tgz] |
|---|---|---|
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | Thu Mar 21 15:21:57 2013 +0900 |
| committer | Jaegeuk Kim <jaegeuk.kim@samsung.com> | Wed Mar 27 09:16:25 2013 +0900 |
| tree | 8ff66198318ee79464b9ac47e8ee091acf140c20 | |
| parent | fa37241743ac26ba0ac6f54579158c2fae310a5c [diff] |
f2fs: fix to give correct parent inode number for roll forward When we recover fsync'ed data after power-off-recovery, we should guarantee that any parent inode number should be correct for each direct inode blocks. So, let's make the following rules. - The fsync should do checkpoint to all the inodes that were experienced hard links. - So, the only normal files can be recovered by roll-forward. Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>