Jaegeuk Kim 953a3e27e1 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>
2013-03-27 09:16:25 +09:00
..
2012-12-11 13:43:42 +09:00
2013-02-12 07:15:01 +09:00
2013-03-20 18:30:16 +09:00
2012-12-11 13:43:43 +09:00
2012-12-11 13:43:42 +09:00
2013-03-20 18:30:15 +09:00
2012-12-11 13:43:42 +09:00