Bug ID 1198669
Summary Unable to fully read some files with ntfs3
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Major
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter linus.kardell@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

I'm trying out the ntfs3 kernel driver on OpenSUSE Tumbleweed, but I'm unable
to read some files. I also posted about this here:
https://reddit.com/r/openSUSE/comments/u693vm/no_such_file_or_directory_when_reading_some_files/
, and at https://bugzilla.kernel.org/show_bug.cgi?id=215864

The files that it happens to are a few GiB in size. It doesn't fail
immediately, rather when I read it with dd status=progress the first time it
reads a bit into the file (a few MiB or over a hundred MiB, depending on the
files, but it seems to always be the same distance for the same file), and then
throws "No such file or directory".

On subsequent reads, it gets through the whole file. Only, it doesn't really,
because the resulting content is wrong. It's the correct length, but past a
certain point the it's all zeroes. So it never truly reads the whole file, but
only sometimes throws an error (when it's not in disk cache?). The same file
always comes out correct with ntfs-3g.

Also, not sure if related, but after I've mounted and unmounted a few times
with ntf3 and ntfs-3g, ntfs3 starts throwing errors saying:

"mount: /windows/d: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error."

and refuses to mount it unless I add -o ro. ntfs-3g still mounts it, and ntfs3
mounts it after rebooting.

The filesystem has compression enabled, in case that matters (though the files
should be incompressible, as they're gzipped).

I tried running chkdsk from Windows, but that did not change anything.


You are receiving this mail because: