All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artem S. Tashkinov" <aros@gmx.com>
To: ntfs3@lists.linux.dev
Cc: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Subject: NTFS driver excessive logging by default: Correct links count
Date: Tue, 7 Jul 2026 08:15:09 +0000	[thread overview]
Message-ID: <2230872c-1651-4fe3-a2a7-ccaf2b28317e@gmx.com> (raw)

Hello,

This is my ~22th attempt to draw attention to this issue. Konstantin has 
been emailed twice with a clean Windows image that exhibits the issue.

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.

This is still reproducible as of 7.1.3. I first reported the issue for 
Linux 6.8.2, i.e. over a year ago. Maybe someone could look into it 
after all. I can email you an NTFS image if necessary but _ANY_ Windows 
10 or 11 install will exhibit it.

Best regards,
Artem

             reply	other threads:[~2026-07-07  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07  8:15 Artem S. Tashkinov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-28 21:41 NTFS driver excessive logging by default: Correct links count Artem S. Tashkinov
2025-04-20 11:05 Artem S. Tashkinov
2024-03-27 10:28 Artem S. Tashkinov
2024-04-11 11:00 ` Konstantin Komarov
2024-04-11 13:01   ` Artem S. Tashkinov
2024-04-15 10:11     ` Enrico Mioso
2024-04-15 14:12       ` Artem S. Tashkinov
2024-05-27  8:25   ` Enrico Mioso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2230872c-1651-4fe3-a2a7-ccaf2b28317e@gmx.com \
    --to=aros@gmx.com \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=ntfs3@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.