Hello! You can report this to redhat bugzilla if they still support 5.x RHEL versions. On Tue, Aug 13, 2013 at 12:12 AM, Khoi Mai <KHOIMAI at up.com> wrote: > Further testing, > > I've found that in /etc/fstab on rhel 5.9 that the option for *"ro"* is > only enforced when*"noexec"* is also apart of the mounting option. > > /etc/fstab > hostname:/testcontent /mnt glusterfs *ro,noexec * 0 0 > mount -l > glusterfs#hostname:/testcontent on /mnt type fuse (*ro,noexec,* > nosuid,nodev,default_permissions,allow_other,max_read=131072) > [root at hostname mnt]# touch goofy > touch: cannot touch `goofy': Read-only file system > [root at hostname mnt]# > > > /etc/fstab > hostname:/testcontent /mnt glusterfs *ro* 0 0 > mount -l > glusterfs#hostname:/testcontent on /mnt type fuse (*ro* > ,default_permissions,allow_other,max_read=131072) > > [root at hostname mnt]# touch mickeymouse > [root at hostname mnt]# ls -l mickey* > -rw-r--r-- 1 root root 0 Aug 12 14:59 mickeymouse > [root at hostname mnt]# rm -f mickeymouse > [root at hostname mnt]# ls -l mickey* > ls: mickey*: No such file or directory > [root at hostname mnt]# > > Community is there a bugzilla or a fix for this behavior? My intentions > is to have my clients use the native fuse mount rather than NFS. > I've been able to replicate this behavior only on rhel 5.9 2.6.18-348.el5, > while I've had success on RHEL6 clients mounting options as "ro" > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130813/0d6f09d1/attachment.html>
