Partition in Thunar is read-only but in fstab it's read-write

drcouzelis · 2017-10-05 02:01:08

I have a partition mounted read-write on "/storage". When I use Thunar to copy a file anywhere on the partition, it fails with the popup message:

Stupid Thunar wrote:

"Error while copying to "blargittyblarg".
The destination is read only.

Here is my "/etc/fstab" file:

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/nvme0n1p2 LABEL=SYSTEM
UUID=264417d3-50f0-4404-af0d-bcee765a7c8f	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/nvme0n1p1 LABEL=ESP
UUID=A0DC-7E34      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/nvme0n1p3 LABEL=PERSONAL
UUID=b904bd91-c4db-44fe-8abc-18a36867f98e	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdb1 LABEL=STORAGE
UUID=4312f7f5-11d9-447f-b3b2-526832c29c39	/storage  	ext4      	rw,relatime,data=ordered	0 2

# /dev/sda1 LABEL=BACKUP
UUID=5f0e02ad-b806-4421-b6a4-e5fc4eeff439	/backups   	ext4      	rw,relatime,data=ordered	0 2

# Bind mounts, for convenience in accessing storage
/storage/drcouzelis/Music			/home/drcouzelis/Music		none	defaults,bind,ro	0 2
/storage/drcouzelis/Pictures			/home/drcouzelis/Pictures	none	defaults,bind,ro	0 2
/storage/drcouzelis/Shows			/home/drcouzelis/Shows		none	defaults,bind,ro	0 2
/storage/drcouzelis/Videos			/home/drcouzelis/Videos		none	defaults,bind,ro	0 2

What can I do to be able to use Thunar to read and write files to this partition?

circleface · 2017-10-05 02:23:26

You may need to change the permissions on the mount point to be able to write to the disk.

seth · 2017-10-05 09:02:12

check the output of "mount" on how the disk is actually mounted. In case of errors, it may re-mount as ro for data protection.

drcouzelis · 2017-10-05 16:48:09

Thank you for the suggestions.

circleface wrote:

You may need to change the permissions on the mount point to be able to write to the disk.

$ ls -ld /storage /storage/drcouzelis
drwxr-xr-x 4 root       root  4096 Oct  1 21:40 /storage
drwxr-xr-x 8 drcouzelis users 4096 Sep  7 08:25 /storage/drcouzelis

$ cd /storage/drcouzelis
$ touch me
# File is successfully created

I do have write permission from a terminal window, just not in Thunar. I apologize, I wasn't originally clear about that.

seth wrote:

check the output of "mount" on how the disk is actually mounted. In case of errors, it may re-mount as ro for data protection.

$ mount | grep "/dev/nvme0"
/dev/nvme0n1p2 on / type ext4 (rw,relatime,data=ordered)
/dev/nvme0n1p3 on /home type ext4 (rw,relatime,data=ordered)
/dev/nvme0n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)

$ mount | grep "/dev/sd"
/dev/sda1 on /backups type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /storage type ext4 (rw,relatime,data=ordered)
/dev/sdb1 on /home/drcouzelis/Shows type ext4 (ro,relatime,data=ordered)
/dev/sdb1 on /home/drcouzelis/Music type ext4 (ro,relatime,data=ordered)
/dev/sdb1 on /home/drcouzelis/Pictures type ext4 (ro,relatime,data=ordered)
/dev/sdb1 on /home/drcouzelis/Videos type ext4 (ro,relatime,data=ordered)

It appears to be a Thunar (maybe gvfs?) issue...

Any other suggestions?

seth · 2017-10-05 19:26:29

I guess it's irritated by the bind mounts then?

drcouzelis · 2017-10-06 12:38:41

seth wrote:

I guess it's irritated by the bind mounts then?

I poked around a bit more... I think you might be right.

I removed the bind mounts then restarted X and Thunar behaved as expected. Yay!

Then I re-added the bind mounts and restarted X and... Thunar still behaved as expected! Yay?

Anyway, I'll poke a bit more.

Does anyone have any suggestions for doing bind mounts differently? In a different order? With different settings? Or different software altogether?

unixman · 2017-10-06 14:00:43

# Bind mounts, for convenience in accessing storage

/storage/drcouzelis/Music			/home/drcouzelis/Music		none	defaults,bind,ro	0 2

Wild quess: How about "ro" above.

See section "Bind mounts" in 'man mount'

Last edited by unixman (2017-10-06 14:19:15)

drcouzelis · 2017-10-06 15:15:01

unixman wrote:

Wild quess: How about "ro" above.

I'm sorry, I don't understand what you mean.

Here is the man page, for easy reference:

   Bind mounts
       Since Linux 2.4.0 it is possible to remount part of the file hierarchy somewhere else.  The call is:

              mount --bind olddir newdir

       or by using this fstab entry:

              /olddir /newdir none bind

       After this call the same contents are accessible in two places.  One can also remount a single file
       (on a single file).  It's  also  possible  to use the bind mount to create a mountpoint from a regular
       directory, for example:

              mount --bind foo foo

       The  bind  mount  call  attaches  only  (part  of) a single filesystem, not possible submounts.  The
       entire file hierarchy including submounts is attached a second place by using:

              mount --rbind olddir newdir

       Note that the filesystem mount options will remain the same as those on the original mount point.

       mount(8) since v2.27 allows to change the mount options by passing the relevant options along
       with --bind.  For example:

              mount -o bind,ro foo foo

       This feature is not supported by the Linux kernel; it is implemented in userspace by an additional
       mount(2) remounting system call.   This  solution is not atomic. 

       The alternative (classic) way to create a read-only bind mount is to use the remount operation, for
       example:

              mount --bind olddir newdir
              mount -o remount,bind,ro olddir newdir  

       Note that a read-only bind will create a read-only mountpoint (VFS entry), but the original
       filesystem superblock will still be writable, meaning that the olddir will be writable, but the newdir
       will be read-only.

       It's also possible to change nosuid, nodev, noexec, noatime, nodiratime and relatime VFS entry
       flags by "remount,bind" operation. It's impossible to change mount options recursively (for
       example with -o rbind,ro).

seth · 2017-10-06 15:24:09

I think he considers the ro bind mount the "culprit" - it's probably the cause but also likely deliberate and should™ not be a problem at all (but seems to be for thunar)

Arch Linux

#1 2017-10-05 02:01:08

Partition in Thunar is read-only but in fstab it's read-write

#2 2017-10-05 02:23:26

Re: Partition in Thunar is read-only but in fstab it's read-write

#3 2017-10-05 09:02:12

Re: Partition in Thunar is read-only but in fstab it's read-write

#4 2017-10-05 16:48:09

Re: Partition in Thunar is read-only but in fstab it's read-write

#5 2017-10-05 19:26:29

Re: Partition in Thunar is read-only but in fstab it's read-write

#6 2017-10-06 12:38:41

Re: Partition in Thunar is read-only but in fstab it's read-write

#7 2017-10-06 14:00:43

Re: Partition in Thunar is read-only but in fstab it's read-write

#8 2017-10-06 15:15:01

Re: Partition in Thunar is read-only but in fstab it's read-write

#9 2017-10-06 15:24:09

Re: Partition in Thunar is read-only but in fstab it's read-write

Board footer