Bug 123620

I guess it s a problem of firewall on the NFS server.

Stop the iptables and u will see that it works.

The problems now is that i can't make bind the rpc.rquotad to a
specific port

i modified the /etc/init.d/nfs file
to launch rpc.rquotad on a specific port as it s writtent in the man
pages but it didn't work :(

None of the NFS servers have firewalls or filtering running.  I've 
also tried temporarily switching off the iptables filtering on the 
client box but still no change.

Then have u checked that the rpc.rquotad is running on the server

what does the rpcinfo -p servername give?

   program vers proto   port
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100007    3   udp  32774  ypbind
    100007    2   udp  32774  ypbind
    100007    1   udp  32774  ypbind
    100007    3   tcp  32771  ypbind
    100007    2   tcp  32771  ypbind
    100007    1   tcp  32771  ypbind
    100024    1   udp  32778  status
    100024    1   tcp  32772  status
    100133    1   udp  32778
    100133    1   tcp  32772
    100021    1   udp   4045  nlockmgr
    100021    2   udp   4045  nlockmgr
    100021    3   udp   4045  nlockmgr
    100021    4   udp   4045  nlockmgr
    100021    1   tcp   4045  nlockmgr
    100021    2   tcp   4045  nlockmgr
    100021    3   tcp   4045  nlockmgr
    100021    4   tcp   4045  nlockmgr
    100005    1   udp  32791  mountd
    100005    2   udp  32791  mountd
    100005    3   udp  32791  mountd
    100005    1   tcp  32773  mountd
    100005    2   tcp  32773  mountd
    100005    3   tcp  32773  mountd
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100011    1   udp  55201  rquotad

I'm seeing the exact same behavior with a NetApp NFS filer.  "rquotad"
is present in the output of "rpcinfo -p".  All iptables rules have
been flushed on the client machine and there is no firewall in between
the client and the NFS server.

NFS quota reporting in this environment (using the NetApp filer)
worked properly with all previous RedHat distributions.  I'll be
rolling out FC2 to a number of our labs soon.  I'd love to figure out
a fix for this problem.

Created attachment 101105 [details]
Fix for NFS quota checking

Looks like its a bug in the quota-tools 3.10 release, if you download and
compile 3.11 or later it goes away ...

From 3.11's changelog:
"quota-tools should again use old RPC protocol when needed" (Jan Kara)

Attached patch backports changes from the 3.11 release and appears to work
correctly with our Solaris 9 fileserver

Tried Simon Thompson's patch FC2 client, SGI Irix 6.5.24 NFS server:

Before patch:
> quota
quota: Error while getting quota from
zeus:/store/homes/students/llalonde for 7262: Invalid argument
Disk quotas for user llalonde (uid 7262): none

After patch:
> quota -v
Disk quotas for user llalonde (uid 7262): none

Here's the quota information from a RedHat 9 client:
> quota
Disk quotas for user llalonde (uid 7262):
     Filesystem  blocks   quota   limit   grace   files   quota  
limit   grace
zeus:/store/homes/students/llalonde
                 759984  7500000 8000000            9609       0       0

All is still not right with suggested patch...

quota-tools version 3.12 works with FC2 and IRIX 6.5.24 NFS server:

> quota llalonde
Disk quotas for user llalonde (uid 7262):
     Filesystem  blocks   quota   limit   grace   files   quota  
limit   grace
zeus:/store/homes/students/llalonde
                 759984  7500000 8000000            9609       0       0

Forgot to add myself to CC list

Created attachment 101866 [details]
srpm based on the released fc2 quota package, updated to quota-tools-3.12 

This is an srpm based on the released fc2 quota package, updated to
quota-tools-3.12.  quota-tools-3.12 fixes the quota reporting problem seen in
quota package that was release with fc2.

Works well for me, YMMV.

Ben

We had the same problem using a Tru64 nfs server, but the attachment 
id=101866 fixed it. Why is this not in Fedora Core 2 updates, it 
seems to harm a lot of people? 

Yes, please get this into updates.  We have the same problem with
Solaris8, Solaris9, and NetApp filers.

-J

*** Bug 131052 has been marked as a duplicate of this bug. ***

I had the same problem with Soalris nfs servers; the quota 3.12 update
seems to fix it. Thanks! Would be nice if this would make it into the
official updates.

This whould be fixed in the quota-3.12-5 rpm available in rawhide.

Thanks Steve. Can we get that package from rawhide released as an update?

So, again, a problem fixed in rawhide that probably should have been released as
an update but wasn't. Marking as resolved:rawhide, though.