On 04/23/2015 02:46 PM, Soumya Koduri wrote:
Hi Shyam/Niels,
To re-iterate the issues,
a) at present, when two clients access same file, we send
'cache_invalidation' upcall notification to the first client in the
fop cbk path of the second client. This may affect brick latency esp.,
for the
FYI. There is a new proposal on NFSv4 xattr support that is being
debated upon in the IETF working group.
If anyone has any thoughts/comments/concerns, now would be a good time
to express them in the IETF NFSv4 working group ML. As I understand it,
the authors are also looking for any strong
enablement
and checkpatch warnings fixed
Date: Sat, 21 Mar 2015 01:04:30 +0100
From: GerritHub supp...@gerritforge.com
Reply-To: ffilz...@mindspring.com
To: Anand Subramanian ana...@redhat.com
CC: onnfrhvruutnzhnaq.-g...@noclue.notk.org
From Frank Filz ffilz...@mindspring.com
A good place to start would be : https://forge.gluster.org/projects
Please take a look to see if any of the listed projects interests you.
Anand
On 08/06/2014 12:06 AM, Vipul Nayyar wrote:
Hello,
I'm Vipul. I'm currently in my final year of computer engineering and
would like some
+-- snap01_20140503_0800
+-- snap02_20140503_1400
Last 7 days
7-21 days
21-60 days
60-180days
180days
*From: *Anand Subramanian ansub...@redhat.com
*To: *gluster-de...@nongnu.org, gluster-users
gluster-us...@gluster.org
*Cc: *Anand Avati aav...@redhat.com
*Sent
Thanks for the detailed explanation Nithya.
Is it possible that multiple reasons maybe attached to the same
message_id and log-string? In that case I think its good to have a
provision for embedding a rc in the gf_msg ie. a reason code. Then the
documentation can also contain the reason
