Anoop,
I have summarily marked this for 3.10, but have a few requests here,
1) Can we open a spec for this?
2) We possibly need to understand backward compatibility issues/concerns
if any? I.e existing volumes would already have created .trashcan etc.
and how this change impacts those volumes.
Thanks,
Shyam
On 12/10/2016 10:02 AM, Anoop C S wrote:
Hi all,
As per the current design trash directory, namely .trashcan, will be created at the root when bricks associated with a volume become online and there is a restriction to delete this directory from the volume even when trash feature is disabled.
This proposal is targeted in a such a way that creation and subsequent enforcement on trash directory to happen only when feature is enabled for that volume.
Issue opened at [1].
[1] https://github.com/gluster/glusterfs/issues/65
Thanks,
--Anoop C S
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
