Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1098200 - [SNAPSHOT]: Stale options (Snap volume) needs to be removed from volume info
[SNAPSHOT]: Stale options (Snap volume) needs to be removed from volume info
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: snapshot (Show other bugs)
3.0
x86_64 Linux
low Severity low
: ---
: RHGS 3.1.0
Assigned To: Vijaikumar Mallikarjuna
Rahul Hinduja
SNAPSHOT
:
Depends On:
Blocks: 1098910 1202842 1223636
  Show dependency treegraph
 
Reported: 2014-05-15 09:15 EDT by Rahul Hinduja
Modified: 2016-09-17 08:55 EDT (History)
8 users (show)

See Also:
Fixed In Version: glusterfs-3.7.0-3.el6rhs
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1098910 (view as bug list)
Environment:
Last Closed: 2015-07-29 00:31:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description Rahul Hinduja 2014-05-15 09:15:26 EDT
Description of problem:
=======================

With initial design where the snap volume used to be displayed in gluster volume info , we used "Snap Volume: yes/on" to distinguish the volume whether its a snap volume or the original volume. But with new design the snap volumes are not listed in the volume info, hence this entry (snap volume:) doesn't make sense to show.

For example:

root@snapshot09 ~]# gluster v i 
 
Volume Name: vol0
Type: Distributed-Replicate
Volume ID: d666aeaa-58bc-4e5a-9542-d98d1d095cdb
Status: Started
Snap Volume: no
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: snapshot09.lab.eng.blr.redhat.com:/brick0/b0
Brick2: snapshot10.lab.eng.blr.redhat.com:/brick0/b0
Brick3: snapshot11.lab.eng.blr.redhat.com:/brick0/b0
Brick4: snapshot12.lab.eng.blr.redhat.com:/brick0/b0
Options Reconfigured:
features.barrier: disable
nfs.drc: off



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

glusterfs-3.6.0.1-1.el6rhs.x86_64


How reproducible:
=================
1/1


Steps to Reproduce:
===================
1. Create a volume
2. list the volume using "gluster volume info"


Actual results:
===============
Snap Volume: no



Expected results:
==================

This particular option is not required anymore.
Comment 2 Vijaikumar Mallikarjuna 2014-05-30 03:58:39 EDT
Patch https://code.engineering.redhat.com/gerrit/26011 posted
Comment 6 senaik 2015-06-23 04:08:17 EDT
Version : glusterfs-3.7.1-4.el6rhs.x86_64

Snap volume entry removed from gluster v info. Marking the bug 'Verified'

gluster v info 
 
Volume Name: vol1
Type: Distributed-Replicate
Volume ID: d0122a4a-ed80-481e-b5d3-6491f3fa7ae6
Status: Started
Number of Bricks: 5 x 2 = 10
Transport-type: tcp
Bricks:
Brick1: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick6/b6
Brick2: inception.lab.eng.blr.redhat.com:/rhs/brick11/b11
Brick3: inception.lab.eng.blr.redhat.com:/rhs/brick7/b7
Brick4: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick7/b7
Brick5: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick7/b7
Brick6: rhs-arch-srv4.lab.eng.blr.redhat.com:/rhs/brick7/b7
Brick7: inception.lab.eng.blr.redhat.com:/rhs/brick8/b8
Brick8: rhs-arch-srv2.lab.eng.blr.redhat.com:/rhs/brick8/b8
Brick9: rhs-arch-srv3.lab.eng.blr.redhat.com:/rhs/brick8/b8
Brick10: inception.lab.eng.blr.redhat.com:/rhs/brick9/b9
Options Reconfigured:
features.barrier: disable
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
features.uss: enable
performance.readdir-ahead: on
snap-max-soft-limit: 90
snap-max-hard-limit: 3
Comment 8 errata-xmlrpc 2015-07-29 00:31:45 EDT
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/RHSA-2015-1495.html

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