[Bugs] [Bug 1225546] Pass slave volume in geo-rep as read-only

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1225546



--- Comment #2 from Aravinda VK <avishwan at redhat.com> ---
(In reply to Patrick Ladd from comment #1)
> I have a customer that had end users mount the slave and make modifications
> to it.  Any write activity to the slave, as noted in the comments above,
> causes long term problems for geo-replication that may not be recoverable
> without a complete rebuild of the slave.
> 
> After some discussion with gluster engineers, it appears that gluster
> geo-rep itself mounts the slave volume to operate on it.  Therefore,
> implementation for this would have to have some way to restrict non-geo rep
> mounts to read only while still allowing the geo-rep process to mount rw and
> operate on the slave.  Maybe a "super secret" mount option that geo-rep uses
> to distinguish itself?  (Clearly being an open source project it won't
> really be secret but at least someone would have to consciously use it and
> accept the consequences)

Geo-replication mounts volumes using "-o aux-gfid-mount" option. In Gluster
code this can be identified as CLIENT_PID = -1 or CLIENT_PID = GSYNCD.

If you mount a Volume as read-only, it will not affect Geo-replication.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.