All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Braam <Peter.Braam@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Moving forward on Quotas
Date: Thu, 05 Jun 2008 06:45:36 -0700	[thread overview]
Message-ID: <C46D3C11.5835%peter.braam@sun.com> (raw)
In-Reply-To: <20080605122708.GR6283@lore>

Well, this protocol hasn't been published yet; why not include the server
side uid / gid then?

But more seriously, how is this encoded in such a way that the OST can trust
the information - it must be in the capability too?

Peter


On 6/5/08 5:27 AM, "Johann Lombardi" <johann@sun.com> wrote:

> On Thu, Jun 05, 2008 at 04:09:41AM -0700, Peter Braam wrote:
>> Quota are determined by the owner of the file, not by the uid of the
>> process.
> 
> In my understanding, the client is not aware of the server-side uid/gid and
> the file owner returned to the client is translated too. Please let me know
> if I misunderstood how the uid/gid mapping feature works.
> 
>> We have been propagating owners / gid of files from MDS to OSS for this
>> reason.
>> 
>> I don't understand the issue.
> 
> The problem is that the owner / group is propagated to the OSTs through the
> client the first time it sends a bulk write rpc (by setting the
> OBD_MD_FLUID/GID flags) and those identifiers - supplied by the client -
> must be translated too.
> 
> Johann
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel

  reply	other threads:[~2008-06-05 13:45 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080605083957.GQ6283@lore>
2008-06-05 11:09 ` [Lustre-devel] Moving forward on Quotas Peter Braam
2008-06-05 12:27   ` Johann Lombardi
2008-06-05 13:45     ` Peter Braam [this message]
2008-06-06  7:33       ` Johann Lombardi
2008-06-06 12:21         ` Peter Braam
2008-06-09  8:52           ` Yong Fan
2008-06-09 15:37             ` Peter Braam
2008-06-09 16:09               ` Yong Fan
2008-06-10 13:54           ` Yong Fan
2008-06-10 16:51             ` Peter Braam
     [not found] <92825021-D566-4805-9297-5EFBD3260D73@Sun.COM>
2008-06-01  2:44 ` Peter Braam
     [not found] <18490.63940.619731.992500@gargle.gargle.HOWL>
2008-05-26 23:28 ` Peter Braam
2008-05-28  8:06   ` Johann Lombardi
2008-06-01  2:32     ` Peter Braam
2008-06-02 12:22       ` Johann Lombardi
2008-06-02 23:24       ` Andreas Dilger
2008-06-03  8:49         ` Landen tian
2008-06-04  1:24           ` Peter Braam
2008-06-04  7:05             ` Landen tian
2008-06-04  8:26         ` Johann Lombardi
2008-05-28 14:29   ` Ricardo M. Correia
2008-05-28 14:54     ` Nikita Danilov
2008-05-28 15:14       ` Ricardo M. Correia
2008-05-28 16:22         ` Nikita Danilov
2008-05-28 17:05           ` Ricardo M. Correia
2008-05-28 20:06             ` Nikita Danilov
2008-05-28 21:07               ` Ricardo M. Correia
2008-05-28 21:11                 ` Nikita Danilov
2008-05-28 21:33                   ` Ricardo M. Correia
2008-05-29  8:39                     ` Nikita Danilov
     [not found]                       ` <18496.11672.844774.815457@gargle.gargle.HOWL>
2008-05-31 15:31                         ` Ricardo M. Correia
2008-05-31 15:49                           ` Ricardo M. Correia
     [not found]                         ` <1212247447.21348.70.camel@localhost>
2008-05-31 16:19                           ` Nikita Danilov
2008-05-31 17:19                             ` Ricardo M. Correia
2008-05-31 19:11                               ` Nikita Danilov
2008-06-01  2:36                 ` Peter Braam
2008-06-01  3:17                   ` Mike Shapiro
2008-06-01  2:26       ` Peter Braam
2008-06-01  4:53         ` Jeff Bonwick
2008-06-01 13:58           ` Nikita Danilov
2008-06-03  0:50             ` Matthew Ahrens
2008-06-03  7:49               ` Nikita Danilov
2008-06-04 23:50                 ` Matthew Ahrens
2008-05-28 15:24   ` Nikita Danilov
2008-05-31 10:25     ` Peter Braam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C46D3C11.5835%peter.braam@sun.com \
    --to=peter.braam@sun.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.