Bug 1131968

Description of problem:
=======================

When a snapshot of a volume is created, it is readonly volume. If you mount the volume to the client it doesn't allow writes, but its attributes are rw which contradicts the functionality.

For example, snap1 is the snapshoted volume

#mount the snap volume

[root@wingo ~]# mount -t glusterfs inception.lab.eng.blr.redhat.com:/snaps/snap1/vol1 /mnt/snap1
[root@wingo ~]# 

#cd to the mount
[root@wingo ~]# cd /mnt/snap1

#Try to create a dir
[root@wingo snap1]# mkdir a
mkdir: cannot create directory `a': Read-only file system
[root@wingo snap1]# 

Note: The snap volume is mounted as readonly file system

#Look for the mount attributes

[root@wingo ~]# mount | grep snap1
inception.lab.eng.blr.redhat.com:/snaps/snap1/vol1 on /mnt/snap1 type fuse.glusterfs (rw,default_permissions,allow_other,max_read=131072)

The mount attributes are rw which means it is allowed to read and write as well. It should be ro(readonly)

Version-Release number of selected component (if applicable):
=============================================================

glusterfs-3.6.0.27-1.el6rhs.x86_64


How reproducible:
=================
always


Steps to Reproduce:
===================
1. Create a snapshot of a volume
2. Mount the snap volume to the client
3. Grep for mount attributes

Actual results:
===============

mount attributes are shown as (rw)

Expected results:
=================
mount attributes should show (ro)