Bug 1332381 - Filesystem unavailable VM disks unavailable post geo-replication of those disks
Summary: Filesystem unavailable VM disks unavailable post geo-replication of those disks
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: geo-replication
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 06:06 UTC by SATHEESARAN
Modified: 2018-08-14 11:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-03 06:15:08 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description SATHEESARAN 2016-05-03 06:06:39 UTC
Description of problem:
-----------------------
Sharded-Gluster volume is used as a backend for RHEV data domain.
This domain was providing additional disks to the app vms.
This disk was formatted with XFS and contained 308 files.

This gluster volume is geo-replicated and storage (data) domain is re-created at the slave location.

When this disk was attached to the VM, there were no filesystems available on it

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHGS 3.1.3 nightly ( glusterfs-3.7.1-3.el7rhgs )
RHEV 3.6.5.3-0.1.el6

How reproducible:
-----------------
Always/Consistent

Steps to Reproduce:
-------------------
1. Create a RHEV Data domain backed by sharded-gluster volume 
2. Create disks from this domain and attach it to the app vm
3. Format the disk with XFS, mount it and add some files to the mount
4. Create geo-rep checkpoint & Geo-replicate the sharded-gluster volume
5. Restore the data domain on the slave location and attach the disks to the VM

Actual results:
---------------
No filesystem found on the disks those are attached to the VM

Expected results:
-----------------
The filesystems and files should be intact

Comment 1 SATHEESARAN 2016-05-03 06:15:08 UTC
Sorry for this bug, the issue was a mistake from my side.
Wrong set of disks mounted


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