Re: troubling interaction with quotas and nfs

[seth vidal <skvidal@phy.duke.edu>]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Tue, 2002-04-09 at 00:45, Neil Brown wrote:
> On  April 9, skvidal@phy.duke.edu wrote:
> > Hi all,
> >  I'm running red hat 7.2 with the 2.4.9-31 kernel.
> > Its an ext3 file system, exported for nfsv3 udp and nfsv2 clients.
> > 
> > nothing fancy at all.
> > 
> > I have quotas set for my users. If a user hits their hard quota and the
> > process continues to attempt to write to a file in their  quota'd space
> > - the process load on the server shoots through the roof. 
> > 
> > I can reliably recreate this by setting a hard quota, having the system
> > hit the hard quota and continue to attempt to write to that file - the
> > server becomes terribly unhappy.
> > 
> > I never saw this problem on older 2.2.X servers and I'm not sure why I'm
> > seeing it now.
> > 
> > Any places I should be looking first?
> > 
> 
> tcpdump?
> The server should return nfserr_dquot (69 == 0x45) and the client
> should return this to the application.
> But it sounds like the client is repeating the request for some
> reason.
> 
> You could also 
>    echo 32 > /proc/sys/sunrpc/nfsd_debug
> and watch for
>     "nfsd: write complete err=%d"
> messages in the kernel log.  These will tell you whether nfsd thinks
> it got an error for the write.
> 

It appears to return -122

However, the program will exit correctly if it catches that problem. But
the system does not respond well if there is a continued attempt to
write a lot of data when the quota is filled.

That doesn't seem to make sense.

-sv


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]