From: Roman Kagan <rkagan@mail.ru>
To: nfs@lists.sourceforge.net
Subject: quota ignored on NFS
Date: Sat, 15 Jan 2005 01:31:25 +0300 [thread overview]
Message-ID: <1105741885.2328.32.camel@localhost> (raw)
Hi,
I'm having trouble using disk quota with NFS mounted filesystems.
When the filesystem accessed locally on the server, the quota works
fine, i.e. nothing can be written over quota.
However, when the same filesystem is accessed over NFS, an user on the
client can write as much as he wants as though the quota system is
bypassed somehow.
Both the server and the client are on 2.6.10 (was the same at least with
2.6.[89]). The filesystem is ext2 with v2 quota, both NFSv2 and NFSv3,
both tcp and udp (mis)behave the same.
Is that a known problem? Any hints at the solution are appreciated.
Thanks,
Roman.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-01-14 22:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1105741885.2328.32.camel@localhost \
--to=rkagan@mail.ru \
--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.