Announcement

Collapse
No announcement yet.

NTFS Driver Lands Some Late Feature Enhancements For Linux 6.12

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • avis
    replied
    Originally posted by stiiixy View Post

    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?
    I don't understand what you're trying to say.

    The mentioned log spam from the NTFS driver is harmless but extremely annoying and causes a ton of wear and tear.

    Leave a comment:


  • Yndoendo
    replied
    Originally posted by stiiixy View Post

    I thought that project stopped updating years ago?
    One of the recent builds still works with Windows 10 Embedded for update deployment. Other features where not needed for the project.

    Leave a comment:


  • stiiixy
    replied
    Originally posted by smitty3268 View Post

    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.
    I don't understand why I am surprised at people being surprised at Linus doing his job for thirty years.

    Leave a comment:


  • stiiixy
    replied
    Originally posted by avis View Post

    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?

    Leave a comment:


  • avis
    replied
    Originally posted by [deXter] View Post

    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.

    Leave a comment:


  • [deXter]
    replied
    Originally posted by avis View Post

    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).

    Leave a comment:


  • smitty3268
    replied
    Originally posted by erniv2 View Post
    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.

    Leave a comment:


  • ssokolow
    replied
    Originally posted by Danny3 View Post

    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).

    Leave a comment:


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

    Leave a comment:


  • Danny3
    replied
    Originally posted by archkde View Post

    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.

    Leave a comment:

Working...
X