linux.git/fs/f2fs/node.c, branch v3.17

f2fs: truncate stale block for inline_data

2014-08-25T21:52:09+00:00

This verifies to truncate any allocated blocks, offset[0], by inline_data.
Not figured out, but for making sure.

Signed-off-by: Jaegeuk Kim

f2fs: fix incorrect calculation with total/free inode num

2014-08-21T20:57:06+00:00

Theoretically, our total inodes number is the same as total node number, but
there are three node ids are reserved in f2fs, they are 0, 1 (node nid), and 2
(meta nid), and they should never be used by user, so our total/free inode
number calculated in ->statfs is wrong.

This patch indroduces F2FS_RESERVED_NODE_NUM and then fixes this issue by
recalculating total/free inode number with the macro.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: remove rewrite_node_page

2014-08-21T20:57:02+00:00

I think we need to let the dirty node pages remain in the page cache instead
of rewriting them in their places.
So, after done with successful recovery, write_checkpoint will flush all of them
through the normal write path.
Through this, we can avoid potential error cases in terms of block allocation.

Signed-off-by: Jaegeuk Kim

f2fs: handle EIO not to break fs consistency

2014-08-21T20:55:05+00:00

There are two rules when EIO is occurred.
1. don't write any checkpoint data to preserve the previous checkpoint
2. don't lose the cached dentry/node/meta pages

So, at first, this patch adds set_page_dirty in f2fs_write_end_io's failure.
Then, writing checkpoint/dentry/node blocks is not allowed.

Note that, for the data pages, we can't just throw away by redirtying them.
Otherwise, kworker can fall into infinite loop to flush them.
(Ref. xfstests/019)

Signed-off-by: Jaegeuk Kim

f2fs: unlock_page when node page is redirtied out

2014-08-21T16:21:01+00:00

This patch fixes missing unlock_page when a node page is redirtied out.

Signed-off-by: Jaegeuk Kim

f2fs: fix to recover inline_xattr/data and blocks

2014-08-19T17:01:34+00:00

This patch fixes not to skip xattr recovery and inline xattr/data recovery
order.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: should clear the inline_xattr flag

2014-08-19T17:01:34+00:00

During the recovery, we should clear the inline_xattr flag if its xattr node
block is recovered.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: fix the initial inode page for recovery

2014-08-19T17:01:34+00:00

If a new inode page is needed for recover_dentry, we should assing i_inline
as zero.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: fix typo

2014-08-19T17:01:33+00:00

Fix typo and some grammatical errors.

The words "filesystem" and "readahead" are being used without the space treewide.

Signed-off-by: Park Ju Hyung 
Signed-off-by: Jaegeuk Kim

f2fs: avoid skipping recover_inline_xattr after recover_inline_data

2014-08-02T14:43:51+00:00

When we recover data of inode in roll-forward procedure, and the inode has both
inline data and inline xattr. We may skip recovering inline xattr if we recover
inline data form node page first.
This patch will fix the problem that we lost inline xattr data in above
scenario.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim