Re: Is Microsoft Trying To Revive ReFS?

On 2025-03-29, Paul <nospam@needed.invalid> wrote:

On Fri, 3/28/2025 8:57 PM, Borax Man wrote:

["Followup-To:" header set to comp.os.linux.advocacy.]
On 2025-03-28, Farley Flud <fsquared@fsquared.linux> wrote:

On Thu, 27 Mar 2025 22:20:00 +0000, Lawrence D'Oliveiro wrote:
>

>
NTFS is certainly showing its age. But it’s not clear that ReFS is
really enough to take Windows forward.
>

>
Whatever the case, it will be another proprietary format that GNU/Linux
cannot (easily) access.
>
IIRC, it tooks many years befor GNU/Linux was able to correctly access
and write NTFS files.
>
I still would not trust the Linux kernel module for writing NTFS even
though it is regarded to be stable and free from error.
>
In the not-so-rare times that I must interchange files between Winblows
and GNU/Linux I will use either VFAT or EXFAT format.
>
>
>

 
Is there any particular experience that you had that made you distrust
the Linux NTFS driver?
 
I've found it quite robust, but that is just my experience.  Neverthess,
I do still choose exfat or if necessary, vfat for shared partitions.
 

>
There is more than one NTFS driver now. There is one in kernel
and one in FUSE. They're different. From different sources.
Your newest distro may be doing something you did not expect
or select yourself as a behavior.
>
One knows something about more reparse points than the other.
This means, when a reparse point is present, the label in the GUI
will attest to that fact. The other driver tended to produce
messages that were a bit deceptive about what was going on.
>
This has no impact on a USB stick with a few files on it. Most
of the bad behaviors are when using Linux to work on Windows OS volumes.
>
    Paul

Ahh, I see.  My experience has been somewhat limited.  Only really used
it to occasionally access my old Windows partition, an XP one.  Nothing
too heavy or demanding.  I think using NTFS-3g, the Fuse driver.  Still
like you, I would much rather trust a native Linux filesystem while
using Linux.