Bug 1139172

Summary: DHT + SNAPSHOT :- fop (which involves more than one brick )and snapshot race might result in inconsistent state of volume after snapshot restore
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rachana Patel <racpatel>
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: high Docs Contact:
Priority: medium    
Version: rhgs-3.0CC: mzywusko, rgowdapp, rhs-bugs, smohan
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: dht-snapshot
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-16 18:01:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1087818, 1105082, 1118779, 1252244, 1324381    

Description Rachana Patel 2014-09-08 10:00:31 UTC 
Description of problem:
=======================
fop (which involves more than one brick )and snapshot creation race might result in inconsistent state of volume after snapshot restore


Version-Release number of selected component (if applicable):
=============================================================
3.6.0.28-1.el6rhs.x86_64



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


Steps to Reproduce:
===================
If snapshot creation and fop (mkdir, rmdir, rename etc. - fop  which involves more than one brick to complete that operation ) is executed same time then on restoring that snap volume might have in-consistence state.

e.g
dir1 is hasing to sub-volume S0 and
'mkdir dir1' and snapshot creation is executed at same time.
In this case one possibility is:-

time    S0	S1	S2
t0

t1	 snap		snap

t2	dir1

t3  	dir1	dir1	dir1	

t4		snap


on restoring this snap at time tr
time    S0	S1	S2
tr		dir1


Only S1 sub-volume will have Directory and it will not be healed by lookup as Directory is present on only non-hashed sub-volume.



Additional info:
================
This is true for other operations also, creating this bug to track all such possibilities of fop and snapshot race.
Comment 6 Nithya Balachandran 2018-02-23 09:52:19 UTC 
*** Bug 1118780 has been marked as a duplicate of this bug. ***