nfs and quota

[Damien Mascré]

Hello,

Is there a way to use netware quota while mounting
netware nfs exports on a linux workstation ??

TIA,

Damien.

[Dan Nelson]

Damien Mascré wrote:
> Is there a way to use netware quota while mounting
> netware nfs exports on a linux workstation ??

NFS clients should still be bound by the quota settings. You should get
either "No space left on device" or "Disc quota exceeded" errors.

I don't think Novell has implemented the rquotad protocol, though, so
the Unix "quota" command won't show anything.

--
Dan Nelson
dne...@allantgroup.com

[Dan Nelson]

Damien Mascré wrote:

> I am using the independent mode to export the netware volumes, so
> netware knows nothing about which quotas are assigned to users.

Actually it should. Independent mode only deals with trustees/file
permission mapping. User and Group ownership should map correctly
(assuming you have filled in the uid and gid fields under the Unix
Profile tab for all your users in ConsoleOne).

> Forgive my ignorance, but if there is no rquotad protocol.. how do the
> clients know about quotas ?? using the aquota.{user,group} residing at
> the root of the exported volume ??

At the most basic level, clients know about quotas when they receive
EDQUOT (Disc quota exceeded) errors while writing files :) If both
sides support the rquotad protocol, clients can view their current
status with the "quota" command.

quota.user/quota.group files are implementation details of how Unix
systems manage quotas, and since Netware stores its quota database
elsewhere, you won't see them on Netware volumes.

--
Dan Nelson
dne...@allantgroup.com

[Madhan]

I dont think NetWare NFS is connection based, which would have enforced
the NetWare quota - so it may not enforce NetWare quotas. Moreover
there is no single standard for rquotad - which make such a thing
difficult to implement in a interoperable fashion.

Regards,
Madhan.

[Damien Mascré]

Dan Nelson wrote:

>> Forgive my ignorance, but if there is no rquotad protocol.. how do the
>> clients know about quotas ?? using the aquota.{user,group} residing
>> at the root of the exported volume ??
>
> At the most basic level, clients know about quotas when they receive
> EDQUOT (Disc quota exceeded) errors while writing files :) If both
> sides support the rquotad protocol, clients can view their current
> status with the "quota" command.
>
> quota.user/quota.group files are implementation details of how Unix
> systems manage quotas, and since Netware stores its quota database
> elsewhere, you won't see them on Netware volumes.

thanks for all the informations (dan and madhan).
I will test to see how it works here and give you feedback afterwards.

--
damien

[Damien Mascré]

Dan Nelson wrote:

>> I am using the independent mode to export the netware volumes, so
>> netware knows nothing about which quotas are assigned to users.
>
> Actually it should. Independent mode only deals with trustees/file
> permission mapping. User and Group ownership should map correctly
> (assuming you have filled in the uid and gid fields under the Unix
> Profile tab for all your users in ConsoleOne).

I am using nw 5.1 sp6 with nfs 3.0 sp5 with the nfsserv.nlm patch
and edir 8.6.2.

I did some tests :

I have a user called "guy" with uid/gid set to 102004.
I mounted an independant-mode exported volume on a linux workstation,
created directories and files owned by that user: it worked (I mean, the
ownership on nfs side is okay, and on netware side, it is owned by
nfsuser). The chown/chmod commands work fine.
Then I launched nwadmin to set quota for the "guy" user on the exported
volume (netware side).. I created a bunch of files on behalf of "guy" to
exceed the quota, but I succeeded to exceed the quota setting.

I tried to change the export mode to nfs-netware mode and restart the
nfs server.. and nothing worked but mounting the directory : chown/chmod
failed (so I can't test more things) with input/output error (-1).

I can't even know which nds-user are seen to be correctly mapped to
unix-user using the listnfs.nlm tool since it doesn't even launch,
telling me the "searchRoots" symbol can't be resolved by the loader.

TIA,

damien

[Brad Doster]

In article <sYQkb.5152$S13....@prv-forum3.provo.novell.com>, Damien

Mascré wrote:
> on netware side, it is owned by
> nfsuser
>

Then NetWare would look at nfsuser's restrictions, not guy's
restrictions.

> The chown/chmod commands work fine.
>

In my experience, chown does NOT change the NetWare owner. The NetWare
owner is set at file creation time and does not follow changes made
from the Unix side.

But I'm using Native File Access on NW 6 -- it is nearly identical to
the NFS product, but there may be some differences in how things are
handled.

bd
NSC Volunteer SysOp
www.InsightNetSolutions.net