[Bugs] [Bug 1501238] New: [SNAPSHOT] Unable to mount a snapshot on client
bugzilla at redhat.com
bugzilla at redhat.com
Thu Oct 12 09:10:29 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1501238
Bug ID: 1501238
Summary: [SNAPSHOT] Unable to mount a snapshot on client
Product: GlusterFS
Version: 3.12
Component: snapshot
Keywords: Regression, ZStream
Severity: urgent
Priority: urgent
Assignee: bugs at gluster.org
Reporter: rkavunga at redhat.com
CC: amukherj at redhat.com, bugs at gluster.org,
rhs-bugs at redhat.com, rkavunga at redhat.com,
storage-qa-internal at redhat.com, vpapnoi at redhat.com
Depends On: 1500816, 1501235
+++ This bug was initially created as a clone of Bug #1501235 +++
+++ This bug was initially created as a clone of Bug #1500816 +++
Description of problem:
Mounting an activated snapshot to a client by giving the command "mount -t
glusterfs 10.70.42.243:/snaps/test0/bravo /mnt/test0/" fails.
Here, test0 is the snapshot name and bravo is the volume name
Info of the volume:
[root at dhcp42-243 ~]# gluster v info
Volume Name: bravo
Type: Distributed-Replicate
Volume ID: 575514e1-fd58-4205-a418-d551a3463280
Status: Started
Snapshot Count: 254
Number of Bricks: 2 x 3 = 6
Transport-type: tcp
Bricks:
Brick1: 10.70.42.243:/bricks/brick0/bravo
Brick2: 10.70.42.206:/bricks/brick0/bravo
Brick3: 10.70.43.53:/bricks/brick0/bravo
Brick4: 10.70.43.152:/bricks/brick0/bravo
Brick5: 10.70.43.141:/bricks/brick0/bravo
Brick6: 10.70.42.9:/bricks/brick0/bravo
Options Reconfigured:
nfs.disable: on
transport.address-family: inet
features.barrier: disable
features.uss: enable
changelog.changelog: on
cluster.enable-shared-storage: enable
auto-delete: enable
Output of the mount command:
[root at dhcp43-240 ~]# mount -t glusterfs 10.70.42.243:/snaps/test0/bravo
/mnt/test0/
Mount failed. Please check the log file for more details.
Version-Release number of selected component (if applicable):
master
How reproducible: 2/2
Steps to Reproduce:
1. Create and start a volume.
2. Mount the volume on a client and do some I/O's at the mount point.
3. Create a snapshot and activate it.
4. Mount the snapshot on client using the command "mount -t glusterfs <node
ip>:/snaps/<snapname>/<volname> /mnt/<mountname>"
Actual results:
Mount fails with output : Mount failed. Please check the log file for more
details.
Expected results:
Should be mounted successfully.
Additional info:
Output of the log file from the failed mount is attached.
Looking at the log file it seems that the issue is related to the subdir mount.
--- Additional comment from Worker Ant on 2017-10-12 05:08:52 EDT ---
REVIEW: https://review.gluster.org/18506 (mount/fuse : Fix parsing of vol_id
for snapshot volume) posted (#1) for review on master by mohammed rafi kc
(rkavunga at redhat.com)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1500816
[Bug 1500816] [SNAPSHOT] Unable to mount a snapshot on client
https://bugzilla.redhat.com/show_bug.cgi?id=1501235
[Bug 1501235] [SNAPSHOT] Unable to mount a snapshot on client
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list