From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
Cc: "Artem S. Tashkinov" <aros@gmx.com>, ntfs3@lists.linux.dev
Subject: Re: NTFS driver excessive logging by default: Correct links count
Date: Mon, 27 May 2024 10:25:08 +0200 [thread overview]
Message-ID: <ZlRDZIWnetE2kZYl@rivendell> (raw)
In-Reply-To: <32a9b58b-9781-4fb5-af86-3ba96041f85f@paragon-software.com>
Hello all!!
So, if I understand things correctly, this problem has been fixed in commit 110b24eb1a749bea3440f3ca2ff890a26179050a and this issue caused corruption in the FS.
Did the corruption happen even when mounting the filesystem read-only (via the mount ... -o ro flag)?
Or was a write needed?
and what kind of write?
Thanks a lot,
Enrico
next prev parent reply other threads:[~2024-05-27 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 10:28 NTFS driver excessive logging by default: Correct links count 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-20 11:05 Artem S. Tashkinov
2025-06-28 21:41 Artem S. Tashkinov
2026-07-07 8:15 Artem S. Tashkinov
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=ZlRDZIWnetE2kZYl@rivendell \
--to=mrkiko.rs@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=aros@gmx.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.