Bug 1157667 - [DATA LOSS]- DHT- rename from multiple mount ends in data loss
Summary: [DATA LOSS]- DHT- rename from multiple mount ends in data loss
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribute
Version: 2.1
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On: 1141368 1142650 1166570
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-27 13:02 UTC by Rachana Patel
Modified: 2015-11-27 10:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1142650
Environment:
Last Closed: 2015-11-27 10:43:58 UTC
Embargoed:


Attachments (Terms of Use)

Comment 1 Rachana Patel 2014-10-27 13:09:22 UTC
ersion:-
========
3.4.0.69rhs-1.el6rhs.x86_64


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


Steps to Reproduce:
===================
1. create, start and mount distributed volume. 
2. create few files inside it

[root@localhost new]# ls -l
total 0
-rw-r--r-- 1 root root 0 Oct 27 12:43 a
-rw-r--r-- 1 root root 0 Oct 27 12:43 b
-rw-r--r-- 1 root root 0 Oct 27 12:43 c
-rw-r--r-- 1 root root 0 Oct 27 12:43 d


3. start renaming files from multiple mount
while true; do cd /mnt/m1/new; mv -f a b; mv -f c d; mv -f b a; mv -f d c; cd / ; done

4. break loop after some time and check files

[root@localhost new]# ls -l
total 0

verify file on backend

[root@localhost new]# ls -l /rhs/brick1/*/new
/rhs/brick1/m1/new:
total 0

/rhs/brick1/m2/new:
total 0
-rw-r--r-- 2 root root 0 Oct 27 13:53 b

/rhs/brick1/m3/new:
total 0

/rhs/brick1/m4/new:
total 0


[root@localhost new]# ls -l /rhs/brick1/m*/new
/rhs/brick1/m1/new:
total 0

/rhs/brick1/m2/new:
total 0

/rhs/brick1/m3/new:
total 0

/rhs/brick1/m4/new:
total 0


Actual results:
===============
file a and b are not present on mount as well as backend

Expected results:
===============
at least one file a or b should present.


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