[Bugs] [Bug 1654115] New: [Geo-rep]: Faulty geo-rep sessions due to link ownership on slave volume
bugzilla at redhat.com
bugzilla at redhat.com
Wed Nov 28 04:51:03 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1654115
Bug ID: 1654115
Summary: [Geo-rep]: Faulty geo-rep sessions due to link
ownership on slave volume
Product: GlusterFS
Version: 5
Component: geo-replication
Severity: high
Priority: high
Assignee: bugs at gluster.org
Reporter: khiremat at redhat.com
CC: anrobins at redhat.com, avishwan at redhat.com,
bkunal at redhat.com, bugs at gluster.org, csaba at redhat.com,
rhinduja at redhat.com, rhs-bugs at redhat.com,
sankarshan at redhat.com, storage-qa-internal at redhat.com
Depends On: 1645916, 1646104
Blocks: 1646806
External Bug ID: Gluster.org Gerrit 21546
+++ This bug was initially created as a clone of Bug #1646104 +++
+++ This bug was initially created as a clone of Bug #1645916 +++
Description of problem:
Geo-rep session is Faulty with following tracebacks
Master Traceback:
[2018-11-05 07:12:37.31370] E [syncdutils(worker
/bricks/brick0/b0):338:log_raise_exception] <top>: FAIL:
Traceback (most recent call last):
File "/usr/local/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 322, in
main
func(args)
File "/usr/local/libexec/glusterfs/python/syncdaemon/subcmds.py", line 82, in
subcmd_worker
local.service_loop(remote)
File "/usr/local/libexec/glusterfs/python/syncdaemon/resource.py", line 1312,
in service_loop
till=e))
File "/usr/local/libexec/glusterfs/python/syncdaemon/master.py", line 599, in
crawlwrap
self.crawl()
File "/usr/local/libexec/glusterfs/python/syncdaemon/master.py", line 1555,
in crawl
self.changelogs_batch_process(changes)
File "/usr/local/libexec/glusterfs/python/syncdaemon/master.py", line 1455,
in changelogs_batch_process
self.process(batch)
File "/usr/local/libexec/glusterfs/python/syncdaemon/master.py", line 1290,
in process
self.process_change(change, done, retry)
File "/usr/local/libexec/glusterfs/python/syncdaemon/master.py", line 1237,
in process_change
failures = self.slave.server.meta_ops(meta_entries)
File "/usr/local/libexec/glusterfs/python/syncdaemon/repce.py", line 233, in
__call__
return self.ins(self.meth, *a)
File "/usr/local/libexec/glusterfs/python/syncdaemon/repce.py", line 215, in
__call__
raise res
OSError: [Errno 30] Read-only file system:
'.gfid/981277d0-bf2f-4a43-be9a-ec3eabf84955'
Slave Traceback:
[2018-11-05 07:12:37.30050] E [repce(slave f281/bricks/brick0/b0):122:worker]
<top>: call failed:
Traceback (most recent call last):
File "/usr/local/libexec/glusterfs/python/syncdaemon/repce.py", line 118, in
worker
res = getattr(self.obj, rmeth)(*in_data[2:])
File "/usr/local/libexec/glusterfs/python/syncdaemon/resource.py", line 765,
in meta_ops
cmd_ret = errno_wrap(os.chmod, [go, mode],
File "/usr/local/libexec/glusterfs/python/syncdaemon/syncdutils.py", line
546, in errno_wrap
return call(*arg)
OSError: [Errno 30] Read-only file system:
'.gfid/981277d0-bf2f-4a43-be9a-ec3eabf84955'
Version-Release number of selected component (if applicable):
mainline
How reproducible:
Always
Steps to Reproduce:
Use geo-replication to copy symbolic links with either the group or ownership
something other than root.
Actual results:
Geo-rep sessions with a status of "Faulty"
Expected results:
Completed geo-rep sessions.
--- Additional comment from Worker Ant on 2018-11-05 04:13:25 EST ---
REVIEW: https://review.gluster.org/21546 (geo-rep: Fix traceback with symlink
metadata sync) posted (#1) for review on master by Kotresh HR
--- Additional comment from Worker Ant on 2018-11-05 21:23:09 EST ---
REVIEW: https://review.gluster.org/21546 (geo-rep: Fix traceback with symlink
metadata sync) posted (#2) for review on master by Atin Mukherjee
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1646104
[Bug 1646104] [Geo-rep]: Faulty geo-rep sessions due to link ownership on
slave volume
https://bugzilla.redhat.com/show_bug.cgi?id=1646806
[Bug 1646806] [Geo-rep]: Faulty geo-rep sessions due to link ownership on
slave volume
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list