Bug 1344908
| Summary: | [geo-rep]: If the data is copied from .snaps directory to the master, it doesn't get sync to slave [First Copy] | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rahul Hinduja <rhinduja> | |
| Component: | geo-replication | Assignee: | Kotresh HR <khiremat> | |
| Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | rhgs-3.1 | CC: | amukherj, avishwan, bmohanra, csaba, khiremat, rcyriac, rhinduja | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.2.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-1 | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, enabling User Serviceable Snapshots (USS) caused a graph switch, which meant that when data was copied from the .snaps directory to the master volume, the first copy operation is not synchronized to the slave volume/s. The GFID access translator now correctly handles nameless lookups during the graph switch, and all data copied from the .snaps directory is correctly synced from the master volume to the slave volume/s.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1348904 (view as bug list) | Environment: | ||
| Last Closed: | 2017-03-23 05:36:09 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: | 1311843, 1332080, 1348904, 1349271, 1349274, 1351522, 1351530 | |||
|
Description
Rahul Hinduja
2016-06-12 12:03:21 UTC
RCA: When uss is option is toggled to enable it and a file is copied from .snaps to mount the immediate stat is resulting in ENOENT. Hence geo-rep is failing to sync the data. We need to investigate further on why toggling of option is resulting in ENOENT for a very brief interval of time. Upstream Patch http://review.gluster.org/14773 (master) Upstream mainline : http://review.gluster.org/14773 Upstream 3.8 : http://review.gluster.org/14776 And the fix is available in rhgs-3.2.0 as part of rebase to GlusterFS 3.8.4. Verified with the build: glusterfs-geo-replication-3.8.4-13.el7rhgs.x86_64 Entries copied from .snap folder after enabling uss gets synced to slave properly. Moving this bug to verified state. Trial 1: ++++++++ Master: ======= [root@dj .snaps]# cp -rf snap1_GMT-2017.02.05-16.15.32/thread0 /mnt/master/ [root@dj .snaps]# cd /mnt/master/ [root@dj master]# ls -l thread0/level00 total 20 -rw-r--r--. 1 root root 4291 Feb 5 2017 58969b38%%DAM0T9081Y -rw-r--r--. 1 root root 4707 Feb 5 2017 58969b38%%FIJEL0B9YQ -rw-r--r--. 1 root root 1760 Feb 5 2017 58969b38%%HKYMLOYL22 -rw-r--r--. 1 root root 2189 Feb 5 2017 58969b38%%MG8MVPGVB1 -rw-r--r--. 1 root root 1362 Feb 5 2017 58969b38%%YIRCIEM5M6 drwxr-xr-x. 3 root root 4096 Feb 5 2017 level10 [root@dj master]# Slave: ====== [root@dj ~]# cd /mnt/slave/ [root@dj slave]# [root@dj slave]# cd thread0/ [root@dj thread0]# [root@dj thread0]# cd level00/ [root@dj level00]# ll total 20 -rw-r--r--. 1 root root 4291 Feb 5 2017 58969b38%%DAM0T9081Y -rw-r--r--. 1 root root 4707 Feb 5 2017 58969b38%%FIJEL0B9YQ -rw-r--r--. 1 root root 1760 Feb 5 2017 58969b38%%HKYMLOYL22 -rw-r--r--. 1 root root 2189 Feb 5 2017 58969b38%%MG8MVPGVB1 -rw-r--r--. 1 root root 1362 Feb 5 2017 58969b38%%YIRCIEM5M6 drwxr-xr-x. 3 root root 4096 Feb 5 2017 level10 [root@dj level00]# Trial 2: ++++++++ Master: ======= [root@dj level00]# rm -rf 58969b38%%2OK1946N7U [root@dj level00]# pwd /mnt/master/thread1/level00 [root@dj level00]# cp -rf /mnt/master/.snaps/snap2_GMT-2017.02.05-16.44.39/thread1/level00/58969b38%%2OK1946N7U . [root@dj level00]# ls /mnt/master/thread1/level00/ 58969b38%%2OK1946N7U 58969b38%%C7ZEJOEPYZ 58969b38%%KO4QYTCMV0 58969b38%%QC6XY94T26 58969b38%%VPC2ZIAKPD level10 [root@dj level00]# ll /mnt/master/thread1/level00/ total 19 -rw-r--r--. 1 root root 3274 Feb 5 2017 58969b38%%2OK1946N7U -rw-r--r--. 1 root root 1656 Feb 5 2017 58969b38%%C7ZEJOEPYZ -rw-r--r--. 1 root root 3419 Feb 5 2017 58969b38%%KO4QYTCMV0 -rw-r--r--. 1 root root 4089 Feb 5 2017 58969b38%%QC6XY94T26 -rw-r--r--. 1 root root 1457 Feb 5 2017 58969b38%%VPC2ZIAKPD drwxr-xr-x. 3 root root 4096 Feb 5 2017 level10 [root@dj level00]# Slave: ====== [root@dj level00]# ll total 15 -rw-r--r--. 1 root root 1656 Feb 5 2017 58969b38%%C7ZEJOEPYZ -rw-r--r--. 1 root root 3419 Feb 5 2017 58969b38%%KO4QYTCMV0 -rw-r--r--. 1 root root 4089 Feb 5 2017 58969b38%%QC6XY94T26 -rw-r--r--. 1 root root 1457 Feb 5 2017 58969b38%%VPC2ZIAKPD drwxr-xr-x. 3 root root 4096 Feb 5 2017 level10 [root@dj level00]# ll total 19 -rw-r--r--. 1 root root 3274 Feb 5 2017 58969b38%%2OK1946N7U -rw-r--r--. 1 root root 1656 Feb 5 2017 58969b38%%C7ZEJOEPYZ -rw-r--r--. 1 root root 3419 Feb 5 2017 58969b38%%KO4QYTCMV0 -rw-r--r--. 1 root root 4089 Feb 5 2017 58969b38%%QC6XY94T26 -rw-r--r--. 1 root root 1457 Feb 5 2017 58969b38%%VPC2ZIAKPD drwxr-xr-x. 3 root root 4096 Feb 5 2017 level10 [root@dj level00]# Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html |