From: seth vidal <skvidal@phy.duke.edu>
To: nfs@lists.sourceforge.net
Subject: troubling interaction with quotas and nfs
Date: 09 Apr 2002 00:19:07 -0400 [thread overview]
Message-ID: <1018325948.2639.67.camel@milo> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
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?
thanks
-sv
--
GPG Public Key: http://www.phy.duke.edu/~skvidal/skvidal.gpg
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-04-09 4:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 4:19 seth vidal [this message]
2002-04-09 4:45 ` troubling interaction with quotas and nfs Neil Brown
2002-04-09 15:19 ` seth vidal
2002-04-10 3:16 ` Andrew Ryan
2002-04-12 3:04 ` Neil Brown
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=1018325948.2639.67.camel@milo \
--to=skvidal@phy.duke.edu \
--cc=nfs@lists.sourceforge.net \
/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.