Hi Jaegeuk,
On 2018/2/12 8:07, Jaegeuk Kim wrote:
> On 02/11, Junling Zheng wrote:
>> Hi, Jaegeuk
>>
>> On 2018/2/10 8:44, Jaegeuk Kim wrote:
>>> On 02/02, Junling Zheng wrote:
Commit "0a007b97aad6"(f2fs: recover directory operations by fsync)
fixed xfstest generic/342 case, but it also
On 2018/2/12 11:42, Yunlei He wrote:
> This patch add two bug on check back during flush nat entries,
> nat_tree_lock will prevent race from node block allocation
> in write_begin.
>
> Signed-off-by: Yunlei He
> ---
> fs/f2fs/node.c | 9 -
> 1 file changed, 4 insertions(+), 5 deletions(-
On 2018/2/12 14:55, Yunlei He wrote:
> This patch introduce a method to make nat journal more fresh:
> i. sort set list using entry # plus cp version difference (last modify
> set cp # and current cp #)
> ii. if meet with cache hit, update last modify cp # to current cp #
As we discuss off-line,
Commit "0a007b97aad6"(f2fs: recover directory operations by fsync)
fixed xfstest generic/342 case, but it also increased the written
data and caused the performance degradation. In most cases, there's
no need to do so heavy fsync actually.
So we introduce two new mount options "fsync={posix,strict
On 2018/2/6 12:31, Sheng Yong wrote:
> This patch introduces lost+found feature to fsck. If a file is found
> unreachable by fsck. Fsck tries to reconnect the file to lost+found
> directory:
> 1. Scan all unreachable file inodes, ignore non-inodes ones and
> directories.
> 2. Check them an
On 2018/2/10 10:28, Jaegeuk Kim wrote:
> This is to fix missing dquot_initialize for orphan inodes.
IMO, we don't need to call dquot_initialize as we have call the function
in evict(), right?
Thanks,
>
> Signed-off-by: Jaegeuk Kim
> ---
> fs/f2fs/checkpoint.c | 28
On 2018/2/13 18:57, Junling Zheng wrote:
> Commit "0a007b97aad6"(f2fs: recover directory operations by fsync)
> fixed xfstest generic/342 case, but it also increased the written
> data and caused the performance degradation. In most cases, there's
> no need to do so heavy fsync actually.
>
> So we
Hello,
I am a student at the University of Texas at Austin's CS department
and I am working on a new, record-and-replay, file system agnostic
crash consistency test harness called CrashMonkey [1][2]. As part of
this project, I need to run various file system checkers and return
one of several diff
