Fwd: [zfs-discuss] [Fwd: ZFS user/group quotas & space accounting [PSARC/2009/204 FastTrack timeout 04/08/2009]]

[Nicolas Williams]

On Wed, Apr 01, 2009 at 07:43:58AM -0400, James Carlson wrote:
> Mike Gerdts writes:
> > >> Has there been any thought to using a UID resolution mechanism similar
> > >> to that used by ps?  That is, if "zfs get ... <dataset>" is run in the
> > >> global zone and the dataset is deleted to a non-global zone, display
> > >> the UID rather than a possibly mistaken username.
> > >
> > > That seems like a good idea to me.  You should send that comment to the
> > > ARC case record (send an e-mail to psarc-ext at sun.com with
> > > "PSARC/2009/204" somewhere in the Subject: header).
> > 
> > Indeed, that might be a good idea.  I wasn't aware of that convention.
> > Though note that this only applies to "zfs userspace" -- we would
> > simply say that if the fs is zoned, that implies the -n option.  We
> > could also disallow them from doing "zfs get userused at name
> > pool/zoned/fs", just make it an error to prevent them from seeing
> > something other than what they intended.
> 
> It looks like a small thing, but I suggest running that by the TX
> team.  On a TX system, the user names to UID mappings are all the
> same.

Yes, but this is an artifact of how TX provides name services for zones.
I think what you mean is that since the namespaces are the same in all
TX zones and the TX g-z zfs(1) should not eschew ID->name resolution
when run in the TX g-z and applied to datasets delegated to other zones.

But I don't think that's worthwhile: suppose TX someday adds support for
non-TX exclusive IP zones[*], then we'd have to go back and fix zfs(1).

[*] Running at a specific label from the TX p.o.v, and using no
    multilevel services from the g-z, except, perhaps, X11 displays
    shared via shm and Unix domain sockets.

Nico
--