Bug 1165704 - [USS]:After deactivating a snapshot trying to access the remaining activated snapshots from NFS mount gives 'Invalid argument' error
Summary: [USS]:After deactivating a snapshot trying to access the remaining activated ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: snapshot
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: RHGS 3.0.3
Assignee: Vijaikumar Mallikarjuna
QA Contact: senaik
URL:
Whiteboard: USS
Depends On:
Blocks: 1162694 1166197 1175736
TreeView+ depends on / blocked
 
Reported: 2014-11-19 14:14 UTC by senaik
Modified: 2016-09-17 12:55 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.6.0.35-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1166197 (view as bug list)
Environment:
Last Closed: 2015-01-15 13:42:42 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0038 0 normal SHIPPED_LIVE Red Hat Storage 3.0 enhancement and bug fix update #3 2015-01-15 18:35:28 UTC

Description senaik 2014-11-19 14:14:33 UTC
Description of problem:
=======================
After deactivating a snapshot trying to access the remaining activated snapshots from NFS mount gives 'Invalid argument' error . 


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

How reproducible:
=================
3/3

Steps to Reproduce:
==================
1.Create a 2x2 dist-rep volume and start it 

2.Fuse and NFS mount the volume and enable USS on the volume 

3.Create IO on the volume and take few snapshots 

4.Activate all the snapshots 

5.cd to .snaps from fuse and nfs mount, all snapshots are listed

6.Deactivate one snapshot
 gluster snapshot deactivate vol0_snap1
Deactivating snap will make its data inaccessible. Do you want to continue? (y/n) y
Snapshot deactivate: vol0_snap1: Snap deactivated successfully

7.cd  to .snaps from nfs mount - it fails with Invalid argument error


List of snapshots when the snapshots were activated:
====================================================
[root@dhcp-0-97 .snaps]# ll
total 192
drwxr-xr-x. 13 root root   378 Nov 19 18:05 vol0_snap1
drwxr-xr-x. 31 root root 16384 Nov 19 18:10 vol0_snap10
drwxr-xr-x. 34 root root 16384 Nov 19 18:11 vol0_snap11
drwxr-xr-x. 34 root root 16384 Nov 19 18:11 vol0_snap12
drwxr-xr-x. 37 root root 16384 Nov 19 18:12 vol0_snap13
drwxr-xr-x. 39 root root 16384 Nov 19 18:13 vol0_snap14
drwxr-xr-x. 40 root root 16384 Nov 19 18:13 vol0_snap15
drwxr-xr-x. 42 root root 16384 Nov 19 18:14 vol0_snap16
drwxr-xr-x. 16 root root   480 Nov 19 18:06 vol0_snap2
drwxr-xr-x. 18 root root   514 Nov 19 18:06 vol0_snap3
drwxr-xr-x. 19 root root   582 Nov 19 18:07 vol0_snap4
drwxr-xr-x. 22 root root 16384 Nov 19 18:07 vol0_snap5
drwxr-xr-x. 24 root root 16384 Nov 19 18:08 vol0_snap6
drwxr-xr-x. 27 root root 16384 Nov 19 18:08 vol0_snap7
drwxr-xr-x. 28 root root 16384 Nov 19 18:09 vol0_snap8
drwxr-xr-x. 30 root root 16384 Nov 19 18:09 vol0_snap9

After deactivating one snapshot, ll on .snaps fails :
====================================================
[root@dhcp-0-97 .snaps]# ll
ls: reading directory .: Invalid argument
total 0
[root@dhcp-0-97 .snaps]# ll
ls: cannot open directory .: Invalid argument
[root@dhcp-0-97 .snaps]# ll
ls: cannot open directory .: Invalid argument
[root@dhcp-0-97 .snaps]# 



Actual results:
===============
After deactivating a snapshot accessing the remaining activated snapshots from NFS mount gives 'Invalid argument' error 


Expected results:
================
Even after deactivating few snapshots, the remaining activated snapshots should be listed under .snaps 


Additional info:

Comment 4 Vijaikumar Mallikarjuna 2014-11-26 11:42:12 UTC
Patch submitted: https://code.engineering.redhat.com/gerrit/37398

Comment 5 senaik 2014-12-10 10:26:14 UTC
Version : glusterfs 3.6.0.37
========

Repeated the steps as mentioned in Description and Comment3 , unable to reproduce the issue. 

Marking the bug as 'Verified'

Comment 7 errata-xmlrpc 2015-01-15 13:42:42 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.

https://rhn.redhat.com/errata/RHBA-2015-0038.html


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