Bug 1138382 - DHT + Snapshot :- If snapshot is taken when Directory is created only on hashed sub-vol; On restoring that snapshot Directory is not listed on mount point and lookup on parent is not healing
Summary: DHT + Snapshot :- If snapshot is taken when Directory is created only on hash...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: 3.6.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Shyamsundar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-04 17:06 UTC by Shyamsundar
Modified: 2014-09-05 15:33 UTC (History)
5 users (show)

Fixed In Version:
Clone Of: 1092433
Environment:
Last Closed: 2014-09-05 15:33:47 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shyamsundar 2014-09-04 17:06:39 UTC
+++ This bug was initially created as a clone of Bug #1092433 +++

+++ This bug was initially created as a clone of Bug #1090986 +++

Description of problem:
=======================
Take Snapshot when Directory is created only on  hashed sub-volume and not on others.
On restoring that snapshot, Directory is not listed on mount point. Lookup on parent Directory is not healing Directory on non-hashed sub-volume.


Version-Release number of selected component (if applicable):
=============================================================
3.5qa2-0.340.gitc193996.el6_5.x86_64


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



Steps to Reproduce:
1. create Distributed volume, start it and FUSE mount it.
2. create Directory from mount point and make sure you take a snap of volume when Directory is created only on hashed sub-volume and not on any other
3. stop volume and restore snap
4. mount volume again and list out content of parent Directory.
newly created Directory is not listed

[root@rhs-client18 new]# ls -l
total 0

5. verify Directory in backend.
Directory is present only on hashed sub-volume, not on other sub-volumes

server1:-
[root@rhs-client18 new]# ls -l
total 0

server2:-
[root@OVM5 brick3]# ls -l
total 0
drwxr-xr-x 2 root root 6 Apr 24 15:01 dir1

server3:-
[root@rhs-client18 new]# ls -l
total 0



Actual results:
===============
DHT self heal is not healing Directory entry and Directory is not visible on mount point

Expected results:
=================
Lookup on mount point should heal Directory entry on all up sub-volume

Additional info:

--- Additional comment from RHEL Product and Program Management on 2014-04-24 10:24:57 EDT ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Rachana Patel on 2014-04-29 05:26:27 EDT ---

Able to reproduce without taking snapshot. 
Steps:-
1) send Directory creation from one mount point.
2) When Directory is created on hashed and not not creates on other sub-volumes(non hashed), send lookup from other mount point

--> lookup is not healin Directory on other sub-volumes

Comment 1 Shyamsundar 2014-09-05 15:33:47 UTC
This is already fixed in release 3.6 branch, before merging as a part of bug #1092433.

Closing this bug as NOTABUG.


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