- 30 Dec, 2015 7 commits
-
-
Chao Yu authored
do_checkpoint and write_checkpoint can fail due to reasons like triggering in a readonly fs or encountering IO error of storage device. So it's better to report such error info to user, let user be aware of failure of doing checkpoint. Signed-off-by:
Chao Yu <chao2.yu@samsung.com> Signed-off-by:
Jaegeuk Kim <jaegeuk@kernel.org>
-
Jaegeuk Kim authored
If user tries to update or read data, we don't need to call f2fs_balance_fs which triggers f2fs_gc, which increases unnecessary long latency. Reviewed-by:
-
Chao Yu authored
Only cover sbi->cp_rwsem on one dnode page's allocation and modification instead of multiple's in f2fs_map_blocks, it can reduce the covered region of cp_rwsem, then we can avoid potential long time delay for concurrent checkpointer. Signed-off-by:
-
Jaegeuk Kim authored
This patch introduces recording node block allocation in dnode_of_data. This information helps to figure out whether any node block is allocated during specific file operations. Reviewed-by:
-
Jaegeuk Kim authored
The f2fs_balance_fs doesn't need to cover f2fs_new_inode or f2fs_find_entry works. Reviewed-by:
-
Jaegeuk Kim authored
We can check inode's inline_data flag when calling to convert it. Reviewed-by:
-
Jaegeuk Kim authored
If there is no candidates for shrinking slab entries, we don't need to traverse any trees at all. Reviewed-by:
-
- 22 Dec, 2015 1 commit
-
-
Jaegeuk Kim authored
It would be better to use atomic variable for total_extent_tree. Reviewed-by:
-
- 17 Dec, 2015 4 commits
-
-
Chao Yu authored
This patch adds a tracepoint for sync_dirty_inodes. Signed-off-by:
-
Fan Li authored
check map->m_len right after it changes to avoid excess call to update dnode_of_data. Signed-off-by:
Fan li <fanofcode.li@samsung.com> Reviewed-by:
-
Chao Yu authored
Previously, when finishing a checkpoint, we have persisted all fs meta info including meta inode, node inode, dentry page of directory inode, so, after a sudden power cut, f2fs can recover from last checkpoint with full directory structure. But during checkpoint, we didn't flush dirty pages of regular and symlink inode, so such dirty datas still in memory will be lost in that moment of power off. In order to reduce the chance of lost data, this patch enables f2fs_balance_fs_bg with the ability of data flushing. It will try to flush user data before starting a checkpoint. So user's data written after last checkpoint which may not be fsynced could be saved. When we mount with data_flush option, after every period of cp_interval (could be configured in sysfs: /sys/fs/f2fs/device/cp_interval) seconds user data could be flushed into device once f2fs_balance_fs_bg was called in kworker thread or gc thread. Signed-off-by:
-
Chao Yu authored
Add to stat dirty regular and symlink inode for showing in debugfs. Signed-off-by:
-
- 16 Dec, 2015 7 commits
-
-
Chao Yu authored
Add a new option 'data_flush' to enable data flush functionality. Signed-off-by:
-
Chao Yu authored
Maintain regular/symlink inode which has dirty pages in global dirty list and record their total dirty pages count like the way of handling directory inode. Signed-off-by:
-
Chao Yu authored
Introduce __f2fs_commit_super to include duplicated codes in f2fs_commit_super for cleanup. Signed-off-by:
-
Jaegeuk Kim authored
It needs to relocate its location to see exact trace logs. Signed-off-by: -
Chao Yu authored
We have already got one copy of valid super block in memory, do not grab buffer header of super block all the time. Signed-off-by:
-
Yunlei He authored
f2fs use fields of f2fs_super_block struct directly in a grabbed buffer. Once the buffer happen to be destroyed (e.g. through dd), it may bring in unpredictable effect on f2fs. This patch fixes to allocate additional buffer to store datas of super block rather than using grabbed block buffer directly. Signed-off-by:
Yunlei He <heyunlei@huawei.com> Signed-off-by:
-
Fan Li authored
f2fs_map_blocks will set m_flags and m_len to 0, so we don't need to reset m_flags ourselves, but have to reset m_len to correct value before use it again. Signed-off-by:
-
- 15 Dec, 2015 5 commits
-
-
Chao Yu authored
Introduce __remove_dirty_inode to clean up codes in remove_dirty_dir_inode. Signed-off-by:
-
Chao Yu authored
Add a new dirt list node member in inode info for linking the inode to global dirty list in superblock, instead of old implementation which allocate slab cache memory as an entry to inode. It avoids memory pressure due to slab cache allocation, and also makes codes more clean. Signed-off-by:
-
Chao Yu authored
remove_dirty_dir_inode will be renamed to remove_dirty_inode as a generic function in following patch for removing directory/regular/symlink inode in global dirty list. Here rename ino management related functions for readability, also in order to avoid name conflict. Signed-off-by:
-
Jaegeuk Kim authored
This patch adds MAX_VOLUME_NAME to sync with f2fs-tools. Signed-off-by: -
Chao Yu authored
Do more sanity check for superblock during ->mount. Signed-off-by:
-
- 14 Dec, 2015 3 commits
-
-
Fan Li authored
map.m_len should be reduced after skip a block Signed-off-by:
-
Fan Li authored
@lend of filemap_write_and_wait_range is supposed to be a "offset in bytes where the range ends (inclusive)". Subtract 1 to avoid writing an extra page. Signed-off-by:
-
Chao Yu authored
If read_node_page return LOCKED_PAGE, in its caller it's better a) skip unneeded 'Update' flag and mapping info verfication; b) check nid value stored in footer structure of node page. Signed-off-by:
-
- 09 Dec, 2015 3 commits
-
-
Jaegeuk Kim authored
When modifying sb contents, we need to use lock its buffer. Signed-off-by: -
Jaegeuk Kim authored
Previously, f2fs_commit_super hacks the bh->blocknr to write the broken alternate superblock. Instead of it, we should use the correct logic to retrieve its buffer head with locking it appropriately. Reviewed-by:
-
Jaegeuk Kim authored
This patch enhances the existing bit operation when f2fs allocates SSR blocks. Reviewed-by:
-
- 04 Dec, 2015 10 commits
-
-
Chao Yu authored
In commit 3c454145 ("f2fs: do not trim preallocated blocks when truncating after i_size"), in order to follow the regulation: "truncate(x) where x > i_size will not trim all blocks past i_size." like other file systems, in ->setattr we invoked truncate_setsize instead of f2fs_truncate to avoid unneeded block trimming in such case, but forgot to call f2fs_convert_inline_inode keep consistency of inline data conversion rule. This patch fixes to convert inline data if necessary. Signed-off-by:
-
Chao Yu authored
Use sbi->blocks_per_seg directly to avoid unnecessary calculation when using 1 << sbi->log_blocks_per_seg. Signed-off-by:
-
Chao Yu authored
For direct IO, f2fs only allocate new address for the block which is not exist in the disk before, its mapping info should not exist in extent cache previously, so here we do not need to call f2fs_drop_largest_extent to drop related cache. Due to no more callers for f2fs_drop_largest_extent now, kill it. Signed-off-by:
-
Chao Yu authored
In recover_data, value of argument 'type' will be CURSEG_WARM_NODE all the time, remove it for cleanup. Signed-off-by:
-
Chao Yu authored
Clean up codes in lookup_journal_in_cursum() with __has_cursum_space(). Signed-off-by:
-
Chao Yu authored
No logic changes, just clean up the error path. Signed-off-by:
-
Jaegeuk Kim authored
If device does not support discard, some obsolete dnodes can be recovered by roll-forward. This patch enhances the recovery flow. Signed-off-by: -
Jaegeuk Kim authored
While handling extent trees, we can enter into a reclaiming path anytime. If it tries to release some extent nodes in the same extent tree, write_lock(&et->lock) would be hanged. In order to avoid the deadlock, we can just skip it. Note that, if it is an unreferenced tree, we should get write_lock(&et->lock) successfully and release all of therein nodes. Reviewed-by:
-
Chao Yu authored
get_lock_data_page in f2fs_readdir can fail due to a lot of reasons (i.e. no memory or IO error...), it's better to report this kind of error to user rather than ignoring it. Signed-off-by:
-
Chao Yu authored
We should clear uptodate flag for all pages atomic written when we drop them, otherwise before these cached pages were reclaimed or invalidated eventually, we will see invalid data when hitting them again. Signed-off-by:
-
