Searched hist:"7 c45729a4d6d1c90879e6c5c2df325c2f6db7191" (Results 1 – 10 of 10) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | extent_cache.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | acl.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | inline.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | xattr.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | dir.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | namei.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | inode.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | super.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | file.c | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | f2fs.h | diff 7c45729a4d6d1c90879e6c5c2df325c2f6db7191 Fri Oct 14 13:51:23 CDT 2016 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: keep dirty inodes selectively for checkpoint
This is to avoid no free segment bug during checkpoint caused by a number of
dirty inodes.
The case was reported by Chao like this.
1. mount with lazytime option
2. fill 4k file until disk is full
3. sync filesystem
4. read all files in the image
5. umount
In this case, we actually don't need to flush dirty inode to inode page during
checkpoint.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|