Bug 219123

Summary:	NTFS3 "Correct links count" excessive logging
Product:	File System	Reporter:	Artem S. Tashkinov (aros)
Component:	Other	Assignee:	fs_other
Status:	NEW ---
Severity:	high	CC:	almaz.alexandrovich
Priority:	P3
Hardware:	All
OS:	Linux
Kernel Version:		Subsystem:
Regression:	No	Bisected commit-id:

Description Artem S. Tashkinov 2024-08-04 12:40:30 UTC

Linux 6.9.12 continues to SPAM dmesg with these warning messages:

[ 3488.396120] ntfs3: nvme0n1p3: ino=35bac, Correct links count -> 2.
[ 3488.398239] ntfs3: nvme0n1p3: ino=41bf5, Correct links count -> 2.
[ 3488.398334] ntfs3: nvme0n1p3: ino=41bf6, Correct links count -> 2.
[ 3488.398780] ntfs3: nvme0n1p3: ino=438bb, Correct links count -> 2.
[ 3488.399967] ntfs3: nvme0n1p3: ino=3cb07, Correct links count -> 2.
[ 3488.400341] ntfs3: nvme0n1p3: ino=41a1a, Correct links count -> 2.
[ 3488.406072] ntfs3: nvme0n1p3: ino=4023e, Correct links count -> 2.
[ 3488.407905] ntfs3: nvme0n1p3: ino=37ec2, Correct links count -> 2.
[ 3488.408044] ntfs3: nvme0n1p3: ino=3eb0d, Correct links count -> 2.
[ 3488.413279] ntfs3: nvme0n1p3: ino=3f976, Correct links count -> 2.
[ 3515.004617] ntfs3: 130 callbacks suppressed
[ 3515.004620] ntfs3: nvme0n1p3: ino=b608, Correct links count -> 4.
[ 3515.004937] ntfs3: nvme0n1p3: ino=b5fc, Correct links count -> 4.
[ 3515.004950] ntfs3: nvme0n1p3: ino=b5fd, Correct links count -> 4.
[ 3515.005241] ntfs3: nvme0n1p3: ino=4201e, Correct links count -> 4.
[ 3515.005404] ntfs3: nvme0n1p3: ino=4201f, Correct links count -> 4.
[ 3515.005449] ntfs3: nvme0n1p3: ino=4201d, Correct links count -> 4.
[ 3515.005634] ntfs3: nvme0n1p3: ino=b5ff, Correct links count -> 4.
[ 3515.005791] ntfs3: nvme0n1p3: ino=b5fe, Correct links count -> 4.
[ 3515.005961] ntfs3: nvme0n1p3: ino=b601, Correct links count -> 4.
[ 3515.006133] ntfs3: nvme0n1p3: ino=b600, Correct links count -> 4.

I thought the issue had been fixed.

Comment 1 Artem S. Tashkinov 2024-08-18 13:57:53 UTC

6.10.5, still not fixed:

[  349.164324] ntfs3: nvme0n1p3: ino=3640e, Correct links count -> 2.
[  349.165679] ntfs3: nvme0n1p3: ino=4df08, Correct links count -> 2.
[  349.165774] ntfs3: nvme0n1p3: ino=4df09, Correct links count -> 2.
[  349.166885] ntfs3: nvme0n1p3: ino=3d7a7, Correct links count -> 2.
[  349.167402] ntfs3: nvme0n1p3: ino=4dd32, Correct links count -> 2.
[  349.172777] ntfs3: nvme0n1p3: ino=48cd8, Correct links count -> 2.
[  349.174086] ntfs3: nvme0n1p3: ino=37d95, Correct links count -> 2.
[  349.179436] ntfs3: nvme0n1p3: ino=4bd89, Correct links count -> 2.
[  349.180013] ntfs3: nvme0n1p3: ino=4c55b, Correct links count -> 2.
[  349.181104] ntfs3: nvme0n1p3: ino=3b07c, Correct links count -> 2.
[  366.905986] ntfs3: 152 callbacks suppressed
[  366.905992] ntfs3: nvme0n1p3: ino=4ec78, Correct links count -> 2.
[  366.913658] ntfs3: nvme0n1p3: ino=437b4, Correct links count -> 2.
[  366.915721] ntfs3: nvme0n1p3: ino=4c90e, Correct links count -> 2.
[  366.917454] ntfs3: nvme0n1p3: ino=4e317, Correct links count -> 2.
[  366.920051] ntfs3: nvme0n1p3: ino=4eca8, Correct links count -> 2.

Comment 2 Artem S. Tashkinov 2024-08-18 14:52:21 UTC

The disk has been double checked with chkdsk and no errors were found.

Comment 3 Artem S. Tashkinov 2024-08-30 09:41:45 UTC

I've just gone ahead and commented out:

ntfs_inode_warn(inode, "Correct links count -> %u.", names);

in fs/ntfs3/inode.c

Comment 4 Artem S. Tashkinov 2024-08-30 09:43:06 UTC

I first reported the issue on 3/27/24 and it's still unresolved. Sigh.

Comment 5 Artem S. Tashkinov 2024-10-04 08:04:03 UTC

This is not fixed in 6.11 either.

Could you please DROP/STOP logging this stuff?

This is a NTFS driver error, not the filesystem error.