From: Oleg Drokin <green@namesys.com>
To: Philippe Gramoull? <philippe.gramoulle@mmania.com>
Cc: ReiserFS Mailing List <reiserfs-list@namesys.com>,
reiserfs-dev@namesys.com
Subject: Re: [PAID PRIORITY SUPPORT REQUEST] Quotas not fully working in 2.4.21-pre5
Date: Sat, 5 Apr 2003 11:42:00 +0400 [thread overview]
Message-ID: <20030405114200.A984@namesys.com> (raw)
In-Reply-To: <20030405024529.71d46842.philippe.gramoulle@mmania.com>
Hello!
On Sat, Apr 05, 2003 at 02:45:29AM +0200, Philippe Gramoull? wrote:
> Object: Can't set quotas with 2.4.21-pre5
> After we upgraded from 2.4.19-pre6 + quota patches , 2.4.21-pre5 + data-logging and quota
> patches, we can't set quotas anymore.
Have you enabled all the compatibility stuff in kernel config? (show the relevant part of .config please).
Everything was worked for me last time I tried (at the time of creatign those patches).
I will do more tests now and see what will happen.
What quotatools version do you have?
> here is an extract from 2 straces:
> quotactl(Q_SETQLIM|GRPQUOTA, "/dev/sdb1", 502242, {2048, 0, 0, 0, 0, 0, 0, 0}) = -1 EINVAL (Invalid argument)
> quotactl(Q_SETQLIM|GRPQUOTA, "/dev/sdb1", 32066, {2048, 0, 0, 0, 0, 0, 0, 0}) = -1 EINVAL (Invalid argument)
> This problem is really nasty as this filer is used for the paying services and now clients can use as much
> space as they want.
So, you mean that even old quota limits that were set previously are not enforced?
Bye,
Oleg
next prev parent reply other threads:[~2003-04-05 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 0:45 [PAID PRIORITY SUPPORT REQUEST] Quotas not fully working in 2.4.21-pre5 Philippe Gramoullé
2003-04-05 1:01 ` Philippe Gramoullé
2003-04-05 7:42 ` Oleg Drokin [this message]
2003-04-05 11:11 ` Philippe Gramoullé
2003-04-05 11:22 ` Oleg Drokin
2003-04-05 11:28 ` Philippe Gramoullé
2003-04-05 11:32 ` Oleg Drokin
2003-04-05 11:25 ` Philippe Gramoullé
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=20030405114200.A984@namesys.com \
--to=green@namesys.com \
--cc=philippe.gramoulle@mmania.com \
--cc=reiserfs-dev@namesys.com \
--cc=reiserfs-list@namesys.com \
/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.