tree 9e576b0984e21e4ab3a4515bab29864d63fbcf01
parent dbe6a5ff4fa78bdfa983458c338831d91b35f315
author Jaegeuk Kim <jaegeuk.kim@samsung.com> 1376027175 +0900
committer Jaegeuk Kim <jaegeuk.kim@samsung.com> 1376029524 +0900

f2fs: fix inconsistency between xattr node blocks and its inode

Previously xattr node blocks are stored to the COLD_NODE log, which means that
our roll-forward mechanism doesn't recover the xattr node blocks at all.
Only the direct node blocks in the WARM_NODE log can be recovered.

So, let's resolve the issue simply by conducting checkpoint during fsync when a
file has a modified xattr node block.

This approach is able to degrade the performance, but normally the checkpoint
overhead is shown at the initial fsync call after the xattr entry changes.
Once the checkpoint is done, no additional overhead would be occurred.

Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>