Well, merged into kernel some weeks before likely means that it will be a few weeks before the kernel.org with it is released, and it will take weeks to month or more after that before fedora updates has that kernel.
And merged into the kernel also means that there are almost certainly still going to be some sorts of bugs for a while.
And the management of access times and such means that you would have likely written to the metadata (if you read any files) if the implementation handles updating access times.
And there are now articles saying that code that was merged into the kernel has a bunch of patches waiting to be accepted, and the maintainer has not responded to any of those requests and that new NTFS code is suspected to have immediately been orphaned by the company that asked for it to be merged and agreed to help support it. The articles indicate the linux kernel is working though what is going on with the maintainer.
On Tue, Apr 26, 2022 at 10:28 AM Lily White lilywhite2005@outlook.com wrote:
I didn't mount as readonly, but I didn't write to it also. I'm speculating that the implementation on Fedora and macOS are broken in the same way so that they can actually read each other's broken output.
I thought that NTFS supported just got merged into the kernel some weeks before? Anyone know about the progress?
On 4/26/22 05:16, Patrick O'Callaghan wrote:
On Mon, 2022-04-25 at 10:41 -0500, Roger Heflin wrote:
On Mon, Apr 25, 2022 at 10:11 AM Lily White lilywhite2005@outlook.com wrote:
I got a spare drive and it does work (at least for now, this drive worked for a while before everything broke). So I sent my old drive back to Sandisk and I'll see if it was with that specific model.
I'll also wait for some time and see if wear and tear may cause problems.
What's interesting is that the broken drive works on both Fedora and macOS, but not Windows. That's why I didn't speculate the drive itself was broken before.
I am going to bet that the NTFS code is very similar on Fedora and MacOS. So likely it is a code bug or a usage bug (see comments below).
you did make sure to umount it on Linux/BSD before removing it right?
And if you hibernate the machine(any os) and remove the usb device while hibernated the filesystem may not be consistent, it has to be explicitly unmounted on both windows and fedora before removal so that all data is fully written.
In the past it was suggested to not use NTFS as a transfer drive and to use something simpler like FAT32 as that fs's format is better documented and simpler than NTFS. That may or may not still be the case.
Most NTFS installation on Linux use a user-space implementation via Fuse, which is known to have some limitations (IIRC it's fine for reading but might be problematic when writing). A new kernel-based implementation is apparently on the way and is said to have a higher degree of compatibility.
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
-- From LilyWhite with love _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
users@lists.stg.fedoraproject.org