Hi Jaegeuk & Chao,
OK. I will post a final version including the modification.
Thanks.
On 2023/6/24 2:50, Jaegeuk Kim wrote:
On 06/23, Chao Yu wrote:
On 2023/5/24 10:42, Chunhai Guo wrote:
+ if (!c.fix_on) {
err = -1;
break;
On 06/23, Chao Yu wrote:
> On 2023/5/24 10:42, Chunhai Guo wrote:
> > + if (!c.fix_on) {
> > err = -1;
> > break;
> > }
>
> One more comment.
>
> I guess we'd better skip find_fsync_inode() and continue fsck rather
> than exiting
On 2023/5/24 10:42, Chunhai Guo wrote:
+ if (!c.fix_on) {
err = -1;
break;
}
One more comment.
I guess we'd better skip find_fsync_inode() and continue fsck rather
than exiting directly if c.fix_on is not set,
Hi Chao,
Sorry for replying late, I have send patch "fsck.f2fs: refactor looped
node chain detetected logic for cleanup" as you suggested.
Thanks.
On 2023/6/17 10:20, Chao Yu wrote:
On 2023/6/14 17:27, Chunhai Guo wrote:
Hi Jaegeuk,
Could you please help to confirm if this patch has been
On 2023/6/14 17:27, Chunhai Guo wrote:
Hi Jaegeuk,
Could you please help to confirm if this patch has been merged? I cannot
see the patch in the dev-test or dev branch.
Thanks.
On 2023/5/24 10:42, 郭纯海 wrote:
find_fsync_inode() detect the looped node chain by comparing the loop
counter with
Got it. Thanks.
On 2023/6/15 0:15, Jaegeuk Kim wrote:
On 06/14, Chunhai Guo wrote:
Hi Jaegeuk,
Could you please help to confirm if this patch has been merged? I cannot see
the patch in the dev-test or dev branch.
Thanks. Somehow it was dropped. I start to test again.
Thanks.
On
On 06/14, Chunhai Guo wrote:
> Hi Jaegeuk,
>
> Could you please help to confirm if this patch has been merged? I cannot see
> the patch in the dev-test or dev branch.
Thanks. Somehow it was dropped. I start to test again.
>
> Thanks.
>
> On 2023/5/24 10:42, 郭纯海 wrote:
> > find_fsync_inode()
Hi Jaegeuk,
Could you please help to confirm if this patch has been merged? I cannot
see the patch in the dev-test or dev branch.
Thanks.
On 2023/5/24 10:42, 郭纯海 wrote:
find_fsync_inode() detect the looped node chain by comparing the loop
counter with free blocks. While it may take tens of
On 05/24, Chunhai Guo wrote:
> find_fsync_inode() detect the looped node chain by comparing the loop
> counter with free blocks. While it may take tens of seconds to quit when
> the free blocks are large enough. We can use Floyd's cycle detection
> algorithm to make the detection more efficient,
On 2023/5/24 10:42, Chunhai Guo wrote:
find_fsync_inode() detect the looped node chain by comparing the loop
counter with free blocks. While it may take tens of seconds to quit when
the free blocks are large enough. We can use Floyd's cycle detection
algorithm to make the detection more
find_fsync_inode() detect the looped node chain by comparing the loop
counter with free blocks. While it may take tens of seconds to quit when
the free blocks are large enough. We can use Floyd's cycle detection
algorithm to make the detection more efficient, and fix the issue by
filling a NULL
11 matches
Mail list logo
