2

I recently switched to Fedora 27 Beta (UEFI install, dual-boot with Win 10), and I changed my /etc/fstab to include the two following lines:

UUID=D0E24ECDE24EB78C /media/DownloadsBin  ntfs-3g  auto,user,rw,x-gvfs-show  0 0
UUID=4E565C9C565C869D /media/VMs           ntfs-3g  auto,user,rw,x-gvfs-show  0 0

It should have loaded the devices bearing the given UUIDs into /media/DownloadsBin and /media/VMs appropriately with rw permissions, right? Well, since these are Windows partitions, I had to mount them using NTFS-3g. I can see the files, but whenever I even try to create a new folder (e.g. using mkdir test), I get the error:

mkdir: cannot create directory ‘test’: Read-only file system

The strange part is a similar script worked before on Fedora 26, although I'm not sure if it's got something to do with Fedora 27 Beta (a bug?!) or if there's an error in my code. So, I've come to ask the experts for help!

NOTE : I really don't want to mess around with partition or the folder permissions, especially changing the owner, since Windows started complaining and stopped me from writing to the disk the last time I tried this! I'm hoping there's a better way I can share entire partitions between Win 10 and Fedora 27 Beta without pissing either operating system off?!


Upon further investigation, it turns out that the partitions might be mounted as read-only as confirmed by findmnt /media/(dir):

[somu@lappyPrime DownloadsBin]$ findmnt /media/DownloadsBin TARGET SOURCE FSTYPE OPTIONS /media/DownloadsBin /dev/sda5 fuseblk ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096 [somu@lappyPrime DownloadsBin]$ findmnt /media/VMs TARGET SOURCE FSTYPE OPTIONS /media/VMs /dev/sda6 fuseblk ro,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,allow_other,blksize=4096

Can anyone tell me what's going on?!

  • once mounted run mount -o remount rw /mountpoint – Alex Austin Oct 10 '17 at 22:37
  • Why do you use ntfs-3g and not ntfs? – Michael Hampton Jan 20 '18 at 17:51
  • @MichaelHampton ntfs-3g is the available option for read-write access to ntfs. ntfs is the kernel filesystem type, which only ever had experimental write support, I don't even know if it exists anymore because it's not very useful. – sourcejedi Jan 20 '18 at 21:11
  • What happens if you unmount the FS and mount it manually? Does it show any warning? Note, systemd did not save mount messages to the system log due to an oversight which I submitted a patch for a few days ago :). – sourcejedi Jan 20 '18 at 21:13
  • @sourcejedi Er, ntfs is still around, still has write support and still works. AFAIK ntfs-3g is the outdated filesystem. – Michael Hampton Jan 20 '18 at 21:16

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.