Searched hist:"953 a3e27e10fc6acb480801ea47197d0270d735e" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | node.h | diff 953a3e27e10fc6acb480801ea47197d0270d735e Thu Mar 21 01:21:57 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|
| H A D | namei.c | diff 953a3e27e10fc6acb480801ea47197d0270d735e Thu Mar 21 01:21:57 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|
| H A D | file.c | diff 953a3e27e10fc6acb480801ea47197d0270d735e Thu Mar 21 01:21:57 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|
| H A D | f2fs.h | diff 953a3e27e10fc6acb480801ea47197d0270d735e Thu Mar 21 01:21:57 CDT 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|