We have a set of 4 cores which seem to originate from 2 bugs as filed
and referenced below.
Bug 1: https://bugzilla.redhat.com/show_bug.cgi?id=1636570
Cleanup sequence issues in posix xlator. Mohit/Xavi/Du/Pranith are we
handling this as a part of addressing cleanup in brick mux, or should
we? Ins
== Overview
Today, we are announcing the availability of GCS (Gluster Container
Storage) 0.1. This initial release is designed to provide a platform for
community members to try out and provide feedback on the new Gluster
container storage stack. This new stack is a collaboration across a number
o
On Wed, Oct 10, 2018 at 4:20 AM Shyam Ranganathan
wrote:
> We have a set of 4 cores which seem to originate from 2 bugs as filed
> and referenced below.
>
> Bug 1: https://bugzilla.redhat.com/show_bug.cgi?id=1636570
> Cleanup sequence issues in posix xlator. Mohit/Xavi/Du/Pranith are we
> handlin
Md-cache has option "cache-posix-acl" that controls caching of posix ACLs
("system.posix_acl_access"/"system.posix_acl_default") and virtual glusterfs
ACLs ("glusterfs.posix.acl"/"glusterfs.posix.default_acl") now.
But, _posix_xattr_get_set does not fill virtual glusterfs ACLs when lookup
reque