Bug 1065631
Summary: | dist-geo-rep: gsyncd in one of the node crashed with "OSError: [Errno 2] No such file or directory" | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | M S Vishwanath Bhat <vbhat> | ||||||
Component: | geo-replication | Assignee: | bugs <bugs> | ||||||
Status: | CLOSED EOL | QA Contact: | |||||||
Severity: | high | Docs Contact: | |||||||
Priority: | high | ||||||||
Version: | pre-release | CC: | avishwan, bugs, gluster-bugs, mzywusko, vbhat, vshankar | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2015-10-22 15:40:20 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: | |||||||||
Attachments: |
|
Description
M S Vishwanath Bhat
2014-02-15 09:34:35 UTC
Created attachment 863570 [details]
gsync log from another "Active" node
MS, Anything in geo-rep mount logs? Please attach those too. MS, From the logs, geo-replication is running in xsync mode as the main crawl loop. It seems that a brick got killed (or a crash), due to which geo-replication daemon started running in xsync mode. As this mode cannot handle deletes (and renames), that's why the deletes were not propagated to the slave. For the OSError backtrace, I would need the geo-rep mount logs. The deletes were done once all data were synced. And at that point all the gsyncd were up. The testcase is very simple and reproducible every time. I don't have the setup now. You should be able to reproduce is in the dev environment itself. pre-release version is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it. |