Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx1.redhat.com ([209.132.183.28]:59226 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756767Ab3J2BcI (ORCPT ); Mon, 28 Oct 2013 21:32:08 -0400 Message-ID: <526F0E49.10801@redhat.com> Date: Mon, 28 Oct 2013 18:24:25 -0700 From: Anand Avati MIME-Version: 1.0 To: "Myklebust, Trond" CC: Wheeler Ric , Dr Fields James Bruce , Christoph Anton Mitterer , Mailing List Linux NFS , Dickson Steve Subject: Re: XATTRs in NFS? References: <20131028180838.GG31322@fieldses.org> <526EC3F7.3090601@gmail.com> <526EFFCC.2060506@redhat.com> <18F0636D-7CE0-42C1-9249-325DF69516D4@netapp.com> <526F0893.5030700@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-nfs-owner@vger.kernel.org List-ID: On 10/28/2013 06:26 PM, Myklebust, Trond wrote: > > That battle may have been fought and won within the glusterfs community, but why should we wave the white flag without a discussion? I don't see how what he described above has anything to do with user defined attributes. He's describing how he wants to export quota information and xtime through a private xattr interface that is currently unique to glusterfs. How is that not a private syscall interface? > Exposing quota informtion is use "from the top". Note the other point I mention about using NFS volumes as "gluster bricks" where we store xattrs as dumb and persistent key/values associated with file/dir inodes (fresh/stale info for replication, hash ranges for dirs, quota acconting info per-dir, xtime per dir). > Which of the mainstream filesystems have their own private xattr namespaces like the above? > Why should NFS need to worry? As long as it acts like a pass-through (like every other call it supports). Avati