NTFS Driver Lands Some Late Feature Enhancements For Linux 6.12

[avis]

I'm pretty sure there was an answer that this behavior is intended and won't be changed. I've encountered this errors myself and indeed after checking the filesystem from windows, the errors are gone. So the real bug is, that ntfsfix doesn't notice and can't fix it. About the bugreport, this should be closed as won't fix/works.

This is reproducible in 20 minutes.

Chkdsk does Not solve the issues.

Do any of you even have windows installed? No? Then what the hell are you talking about?

Of course if you created an NTFS partition in Linux and write to it in Linux "there's no bug".

[Yndoendo]

Ummm, might be missing something, but seems to me ntfs should only be used when wanting to retrieve files say off a portable thumb drive or something where permissions don't matter.... When using Linux, format drives to a proper Linux format like ext4, etc. In my case for example, except for a few thumb drives, all my internal and external drives are formatted ext4. Why fiddle faddle with Windows formats at all for general use....

I had to package multiple USB drives with WSUS Offline Update tool, since Microsoft doesn't actually have offline management tools. Windows's built-in and the company's security system hates files and brings the system to a halt while also marking some of those files provided by Microsoft as possible security risks, the irony. They needed to be NTFS formatted. Best throughput for making these USB drives was not from Windows but from Linux, 16 USB drives in total.

[stiiixy]

I had to package multiple USB drives with WSUS Offline Update tool, since Microsoft doesn't actually have offline management tools. Windows's built-in and the company's security system hates files and brings the system to a halt while also marking some of those files provided by Microsoft as possible security risks, the irony. They needed to be NTFS formatted. Best throughput for making these USB drives was not from Windows but from Linux, 16 USB drives in total.

I thought that project stopped updating years ago?

[Danny3]

No, because copying files preserving the creation time is not a thing to begin with (on Linux at least).

That's very sad!
I wish somebody thought about it!
At least for archiving and security purposes.

[woddy]

I removed everything to do with Windows many years ago, so this news leaves me completely indifferent.

[ssokolow]

That's very sad!
I wish somebody thought about it!
At least for archiving and security purposes.

The introduction of the conception of a concept of "creation time" in the POSIX world wasn't that long ago. For the longest time, you just had atime (access time), mtime (modification time), and ctime (metadata modification time).

[smitty3268]

Have to push the forum count why does a late ntfs3 pull only get a slight slap and bcachefs gets the hole shitstorm ???? Btw. dont feed the troll

Linus gives these types of polite warnings to people all the time.

Usually people take the hint and improve. When they don't, then things tend to escalate over time.

[[deXter]]

You don't have partitions with Windows 10/11 installed on them, so there's that.

Install either, open the partition, get hundreds of these errors immediately.

This takes 20 minutes to reproduce.

It is in fact a Windows 11 system partition that I tested on. I've also got some games installed on there which I access via Steam from Linux, so I have it mounted all the time, so yes, I've tested it for longer than 20 minutes.

It's in my fstab with the windows_names and nocase options too, for better compatibility and reducing chances of corruptions.

I would recommend creating a new partition and testing with it, and be sure to disable hibernation / fast startup. I'd also recommend using the mount options I mentioned above. Also worth nothing that nocase only works from 6.11 onwards due to a bug in prior kernels, which I emailed Konstantin about - and to which he did reply, so it's not like he ignores emails.

Also you should be aware that Konstantin isn't just some developer, he's the frikking CEO of Paragon Software, so it's very much understandable if he doesn't respomd to every single email (there could also be a spam filter in play).

[avis]

It is in fact a Windows 11 system partition that I tested on. I've also got some games installed on there which I access via Steam from Linux, so I have it mounted all the time, so yes, I've tested it for longer than 20 minutes.

It's in my fstab with the windows_names and nocase options too, for better compatibility and reducing chances of corruptions.

I would recommend creating a new partition and testing with it, and be sure to disable hibernation / fast startup. I'd also recommend using the mount options I mentioned above. Also worth nothing that nocase only works from 6.11 onwards due to a bug in prior kernels, which I emailed Konstantin about - and to which he did reply, so it's not like he ignores emails.

Also you should be aware that Konstantin isn't just some developer, he's the frikking CEO of Paragon Software, so it's very much understandable if he doesn't respomd to every single email (there could also be a spam filter in play).

I have always disabled hibernation.

Now run find /mnt/windows/Windows and get these errors. A ton of them.

People are truly weird. I have reproduced this issue with clean w10/w11 installations and I'm being doubted.

[stiiixy]

I have always disabled hibernation.

Now run find /mnt/windows/Windows and get these errors. A ton of them.

People are truly weird. I have reproduced this issue with clean w10/w11 installations and I'm being doubted.

Sorry...people are doubting your ability to have a bug free Windows experience since it arrived in 1985, but the moment you attempt to utilise a NTFS driver from within Linux to access a Windows petition you can't utilise said petition without issue? Am I hearing that correctly?