Re: NTFS driver excessive logging by default: Correct links count

Enrico Mioso
2024-04-15T10:11:30Z

On Thu, Apr 11, 2024 at 01:01:21PM +0000, Artem S. Tashkinov wrote:
>
>
> On 4/11/24 11:00, Konstantin Komarov wrote:
> > On 27.03.2024 13:28, Artem S. Tashkinov wrote:
> > > Hello,
> > >
> > > I hoped 6.8.2 would have the issue fixed but no luck.
> > >
> > > Whenever I list files on my NTFS partitions I get a lot of SPAM in
> > > dmesg, e.g.:
> > >
> > > ntfs3: sda3: ino=14c, Correct links count -> 1.
> > > ntfs3: sda3: ino=73, Correct links count -> 1.
> > > ntfs3: sda3: ino=167, Correct links count -> 1.
> > > ntfs3: sda3: ino=d9, Correct links count -> 1.
> > > ntfs3: sda3: ino=d5, Correct links count -> 1.
> > >
> > > And the partition in question has been fully chkdsk'ed and has no issues.
> > >
> > > Please fix.
> > >
> > > Best regards,
> > > Artem
> >
> > Hello Artem,
> >
> > Probably your volume contains non-critical (minor) errors.
> > chkdsk does not show them, but fixes them if you specify /f.
> >
>
> I have run chkdsk /f twice and I'm still getting these errors:
>
> ntfs3: sda7: ino=14c, Correct links count -> 1.
> ntfs3: sda7: ino=73, Correct links count -> 1.
> ntfs3: sda7: ino=d9, Correct links count -> 1.
> ntfs3: sda7: ino=98, Correct links count -> 1.
> ntfs3: sda7: ino=d5, Correct links count -> 1.
> ntfs3: sda7: ino=f2, Correct links count -> 1.
> ntfs3: sda7: ino=e1, Correct links count -> 1.
> ntfs3: sda7: ino=e8, Correct links count -> 1.
> ntfs3: sda7: ino=e5, Correct links count -> 1.
> ntfs3: sda7: ino=e4, Correct links count -> 1.
>
> 1. It's a bug
You are probably right, but let's make it explicit: you're assuming no bugs can be present in chkdsk.exe.
> 2. Even if it's not a bug (I'm 100% sure there is one since chkdsk does
> not fix it), there must be a single message per partition per boot at most.
I might be wrong, but I see different ino values, so limiting the messages at one per boot wouldn't probably make much sense or am I mistaken?

Thanks,
Enrico

>
> Regards,
> Artem
>