Bug 1065635 - dist-geo-rep: Deletes are not synced to slave
Summary: dist-geo-rep: Deletes are not synced to slave
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: pre-release
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-15 10:05 UTC by M S Vishwanath Bhat
Modified: 2023-09-14 02:03 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-05-18 10:47:22 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description M S Vishwanath Bhat 2014-02-15 10:05:34 UTC
Description of problem:
Deletes are not being synced to slave.

Version-Release number of selected component (if applicable):
[root@mustang ~]# gluster --version
glusterfs 3.5.0beta3 built on Feb 15 2014 13:24:29
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.


How reproducible:
Twice out of as many tries

Steps to Reproduce:
1. Create and start a geo-rep session.
2. Untar linux kernel and wait for them to get synced to slave.
3. Now run rm -rf /mnt/master/*

Actual results:
Deletes are not synced to slave.

Expected results:
Deletes should be synced to slave.

Additional info:

I see few crashes which are same as the one seen in https://bugzilla.redhat.com/show_bug.cgi?id=1065631 But I saw them earlier during creates as well. So not sure if both the related somehow.


Pretty straightforward test case. Not attaching any logs.

Comment 1 Kotresh HR 2014-03-14 10:18:39 UTC
libgfchangelog is not loaded into ldconfig cache. So geo-rep always used
xsync FS crawl which does not handle deletes and rename. 
Load libgfchangelog and try. It should work.

Comment 2 Aravinda VK 2015-05-18 10:47:22 UTC
This bug is getting closed because a release has been made available that
should address the reported issue. In case the problem is still not fixed with
glusterfs-3.7.0, please open a new bug report.

Comment 3 Red Hat Bugzilla 2023-09-14 02:03:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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