Ralf Ertzinger wrote:
Hi,
apologies if this is not the right avenue of apporach, I've been unable
to find out how to register on the forums to raise an issue there.
Please point me in the right direction if a different venue is more
appropriate for bug reports.
Yes, the forum has had to be closed for lack of a
volunteer to manage it.
I'm working on a project where a media with some data has to be prepared
on a Linux system to be read by a windows system. The media must not be
written to by the windows system, so I'm using SD cards (which have a
physical write protect switch).
It appears that a file system created by ntfs-3g on Linux (using
2017.3.23) cannot be read by windows from a read only medium. I'm using
the below test case:
On the linux system:
- Create MBR label on SD card
- Create partition (with parted), using fstype ntfs
- Create file system on partition with mkntfs
- Remove SD card from machine, and write protect using the physical
write switch
Looks good to me. AFAIK, the ntfs layout does not have
any provision for marking read-only.
On insertion into a Windows 10 system the following occurs:
- There are errors about errors on the NTFS file system in the event log
(unfortunately I do not have the exact details, can deliver later)
- The partition is shown as "RAW" in Disk Management, but is assigned a
drive letter
- chkdsk.exe recognizes the file system as NTFS, and reports no errors
So the ntfs layout is valid. I suppose you started chkdsk.exe
with writing enabled.
When allowing write access to the SD card windows successfully
recognizes the file system and mounts it.
Is this expected behaviour?
I do not know, as I do not have such device and AFAIK
this has not been reported before.
Windows is probably disoriented because it cannot write
something it wants to. I think of updating the file access
time when a file is being read, or resetting the journal
(which Linux clears to make sure Windows does not apply
it to data modified by Linux), both of which meaning that
read-only mounting was not designed.
Did you try to plug the sd to Windows with writing enabled,
then make a safe unplug, disable writing, and plug again ?
Resetting the journal the Windows way when unmounting
from Linux is a complex task (and dangerous to data).
If this has to be overcome, I would turn to a specific utility
(which has to be designed).
Jean-Pierre
_______________________________________________
ntfs-3g-devel mailing list
ntfs-3g-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel