Ravishankar N ravishan...@redhat.com wrote:
The check can be done in metadata selfheal itself but I don't think AFR is
to blame if the user space app in NetBSD sends a setattr on the parent
dir.
It is not exactly the problem: When adding an entry, you must update
parent directory mtime/ctime.
On Sun, Dec 14, 2014 at 07:24:52PM +0530, Soumya Koduri wrote:
On 12/12/2014 11:06 PM, Niels de Vos wrote:
Hi,
I started to look into getting some form of support for ACLs in gfapi.
After a short discussion with Shyam, some investigation showed that our
current implementation of ACLs
Here is a proposal: we know that at the end of conservative merge, we
should end up with the situation where directory ctime/mtime is the
ctime of the most recently added children.
Won't the directory mtime change as the result of a rename or unlink?
Neither of those would be reflected in the
With the changes present in [1] and [2],
A short explanation of the change would be, we encode the subvol ID in
the d_off, losing 'n + 1' bits in case the high order n+1 bits of the
underlying xlator returned d_off is not free. (Best to read the commit
message for [1] :) )
Although not
- Is there a new connection from glusterfsd (upcall xlator) to
a client accessing a file? If so, how does the upcall xlator reuse
connections when the same client accesses multiple files, or does it?
No. We are using the same connection which client initiates to send-in
fops.
So . . . about that new functionality. The core idea of data
classification is to apply step 6c repeatedly, with variants of DHT that
do tiering or various other kinds of intelligent placement instead of
the hash-based random placement we do now. NUFA and switch are
already examples of
Hi all,
Later today we will have an other Gluster Community Bug Triage meeting.
Meeting details:
- location: #gluster-meeting on Freenode IRC
- date: every Tuesday
- time: 12:00 UTC, 13:00 CET (in your terminal, run: date -d 12:00 UTC)
- agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
