XPost: linux.debian.bugs.dist
From:
[email protected]
Control: tags -1 + moreinfo
Hi,
On Sun, Jun 29, 2025 at 04:51:15PM +0800, dhao2001 wrote:
Package: src:linux
Version: 6.12.33-1
Severity: important
X-Debbugs-Cc: [email protected], [email protected]
User: [email protected]
Usertags: amd64
Dear Maintainer,
After upgrading the kernel version from `6.12.32` to
`6.12.33+deb13`, I was unable to perform file write operations on my
NTFS volumes, although file reads are still possible.
The volume's mount entry is as follows (mounted with GNOME Files):
```
/dev/nvme1n1p1 on /media/myname/Data type ntfs3 (rw,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,uhelper=udisks2)
```
An IO error occurs when writing files, either in GNOME Files or via
the terminal, or in other applications, e.g.,
```
myname@MyPC:~$ echo "xxx" > /media/myname/Data/test.txt
bash: /media/myname/Data/test.txt: Input/output error
```
After making sure to completely reboot Windows many times, I believe
that this issue is not due to Windows Fast Boot.
Also, when I boot with the previous version `6.12.32` kernel, this
issue no longer occurs.
Unfortunately, I didn't notice anything helpful in `dmesg`.
I'm not sure if this issue is directly related to the kernel image.
However, since ntfs3 is used to mount the NTFS volume, I decided to
report it here. Please let me know if this is the wrong place and I
would like to apologize for the potential mistakes.
In the meantime, please let me know if there is any information I
can submit to further clarify this issue.
This is very odd, as there seem to be not ntfs3 related changes in the
changes between v6.12.32 and v6.12.33 (which was as well a very small
release).
A couple of things:
1. Can you please try as well 6.15.4-1~exp1 in experimental to verify if
you can trigger the issue there as well?
2. Can you please still do the following, but each kernel respective,
mount the NTFS volume and try to write to it. Then paste the full
dmesg you get for both 6.12.32-1 booted system and 6.12.33-1
bootest system.
3. If you feel confident, can you bisect the changes between 6.12.32 and
6.12.33 to pinpoint the commit which "breaks" so we might hopefully
be able to narrow down more closely the problem?
Regards,
Salvatore
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)