[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKYAXd_j-MAYP_8a3xEi2MmxZ9Po8t2di5_yi+7V1xXJuD006A@mail.gmail.com>
Date: Thu, 16 Jun 2022 09:46:23 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: 李扬韬 <frank.li@...o.com>
Cc: "sj1557.seo@...sung.com" <sj1557.seo@...sung.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: 答复: [PATCH] exfat: intorduce skip_stream_check mount opt
2022-06-10 22:07 GMT+09:00, 李扬韬 <frank.li@...o.com>:
> HI Namjae,
>
>> Still having problem on linux-exfat after recovering it using windows
>> chkdsk?
>
> After repairing with the chkdsk tool on the windows platform, the current
> file can be accessed normally on linux.
> However, it can be accessed normally on the Windows platform itself, and no
> tools are required to repair it.
> Imagine that if some users do not have a Windows environment and do not
> understand repair tools, they
> cannot access these files on Linux.
>
> Why not just skip the stream entry like Windows does and allow access
> without fixing it?
If the name hash is not checked, file lookup performance will degrade.
Probably you don't want the overall performance degrade for a few
corrupted files. I suggest fixing it by fsck in exfatprogs before
mounting. We are preparing repair function release in fsck to do that
in next month.
Thanks!
>
> Thx,
> Yangtao
>
Powered by blists - more mailing lists