Bug 1040934 - [SNAPSHOT] : Snap volume is not read only
Summary: [SNAPSHOT] : Snap volume is not read only
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: snapshot
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.0.0
Assignee: Sachin Pandit
QA Contact: senaik
URL:
Whiteboard: SNAPSHOT
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 11:23 UTC by senaik
Modified: 2016-09-17 13:05 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.4.1.0.snap.feb05.2014git-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-22 19:30:13 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1278 0 normal SHIPPED_LIVE Red Hat Storage Server 3.0 bug fix and enhancement update 2014-09-22 23:26:55 UTC

Description senaik 2013-12-12 11:23:31 UTC
Description of problem:
======================
After mounting a snap volume, file creation is possible . 

Version-Release number of selected component (if applicable):
=============================================================
glusterfs 3.4.0.snap.dec03.2013git


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

Steps to Reproduce:
==================
1.Create a distribute replicate volume and start it 

2.Mount the volume and create files

3.Create a snap of the volume 
gluster snapshot create volume1 -n SNAP1 -d "this is snap of volume1"
snapshot create: SNAP1: snap created successfully

4. Mount the snap volume and create files 
mount -t glusterfs 10.70.43.74:/volume1/snaps/SNAP1 /mnt/snap_mnt/

[root@snapshot-02 snap_mnt]# touch file{4..10}
[root@snapshot-02 snap_mnt]# ll
total 2
-rw-r--r--. 1 root root 34 Dec 12 06:10 file1
-rw-r--r--. 1 root root  0 Dec 12 09:53 file10
-rw-r--r--. 1 root root 37 Dec 12 07:35 file2
-rw-r--r--. 1 root root 18 Dec 12 07:40 file3
-rw-r--r--. 1 root root  0 Dec 12 09:53 file4
-rw-r--r--. 1 root root  0 Dec 12 09:53 file5
-rw-r--r--. 1 root root  0 Dec 12 09:53 file6
-rw-r--r--. 1 root root  0 Dec 12 09:53 file7
-rw-r--r--. 1 root root  0 Dec 12 09:53 file8
-rw-r--r--. 1 root root  0 Dec 12 09:53 file9



Actual results:
==============
file creation is successful on the snap volume 


Expected results:
================
Snap volume should be read only . 


Additional info:

Comment 2 Sachin Pandit 2014-02-06 07:20:43 UTC
Read only Translator was not inserted in server side.
This issue is fixed in patch 
http://review.gluster.org/#/c/6694/

Comment 3 Rahul Hinduja 2014-02-07 12:02:19 UTC
Verified with: glusterfs-3.4.1.0.snap.feb05.2014git-1.el6.x86_64

Creation of 

[root@wingo 1040934]# touch file{4..10}
touch: cannot touch `file4': Read-only file system
touch: cannot touch `file5': Read-only file system
touch: cannot touch `file6': Read-only file system
touch: cannot touch `file7': Read-only file system
touch: cannot touch `file8': Read-only file system
touch: cannot touch `file9': Read-only file system
touch: cannot touch `file10': Read-only file system
[root@wingo 1040934]# 
[root@wingo 1040934]# mkdir a
mkdir: cannot create directory `a': Read-only file system
[root@wingo 1040934]# 
[root@wingo 1040934]# cp hosts hosts.tmp
cp: cannot create regular file `hosts.tmp': Read-only file system
[root@wingo 1040934]# 
[root@wingo 1040934]# 
[root@wingo 1040934]# cp /etc/hosts hosts
cp: overwrite `hosts'? y
cp: cannot create regular file `hosts': Read-only file system
[root@wingo 1040934]# 
[root@wingo 1040934]# ls
etc  etc.1  host.conf  hosts  hosts.allow  hosts.deny
[root@wingo 1040934]# rm -rf hosts
rm: cannot remove `hosts': Read-only file system
[root@wingo 1040934]# 

Moving the bug to verified state.

Comment 5 Nagaprasad Sathyanarayana 2014-04-21 06:18:03 UTC
Marking snapshot BZs to RHS 3.0.

Comment 6 Nagaprasad Sathyanarayana 2014-05-19 10:56:38 UTC
Setting flags required to add BZs to RHS 3.0 Errata

Comment 9 errata-xmlrpc 2014-09-22 19:30:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1278.html


Note You need to log in before you can comment on or make changes to this bug.