On Thu, 2012-11-15 at 18:51 +0100, Tigran Mkrtchyan wrote:
>
> On Wed, Nov 14, 2012 at 4:03 PM, Myklebust, Trond
> <Trond.Myklebust@xxxxxxxxxx> wrote:
> On Wed, 2012-11-14 at 11:47 +0100, Tigran Mkrtchyan wrote:
> > That's bad news.... Currently we use 'magic files' to
> set/get user
> > specific metadata like number of events, space reservation
> and
> > different file retention policies. The hope was that all
> could be done
> > with named attributes.
> >
> > Tigran.
> >
>
>
> The setting and querying of retention policies is already
> covered in the
> NFSv4.1 protocol without any need for any additions. Space
> reservation
> is already covered in NFSv4.2 (as are security labels -
> another common
> hobby-horse for xattr advocates). Why don't you implement
> those instead
> of wishing for a completely different way of doing the same
> thing?
>
>
>
> Be cause the only tool which I have on the client side is set/get
> xattr.
You're not writing a client; you're writing a server.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
