From: Oleg Drokin <green@namesys.com>
To: "Jos? A. Guzm?n" <jose@iteso.mx>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: quotas in 2.4.20
Date: Sat, 25 Jan 2003 12:09:49 +0300 [thread overview]
Message-ID: <20030125120949.A8569@namesys.com> (raw)
In-Reply-To: <1043463722.3e31fe2a3e267@correo.iteso.mx>
Hello!
On Fri, Jan 24, 2003 at 09:02:02PM -0600, Jos? A. Guzm?n wrote:
> I'm trying to get quotas working on 2.4.20.
> So far they seem to work ok with the dec-3-2002 patches from:
> ftp://ftp.namesys.com/pub/reiserfs-for-2.4/testing/quota-2.4.20/
> with CONFIG_QFMT_V2.
> However the patch from jan-22-2003 in:
> ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.20-pending/01-iput-deadlock-fix.diff
> does not apply on top of the testing/quota-2.4.20 patches.
Yup.
You do not need that patch if you are using quotas, as it is already in ;)
I will rediff quota patches against new 2.4.21-pre later.
> Also, when compiling a 2.4.20 kernel with testing/quota patches and the latest
> evms 1.2.1 patches, compilation stops with:
> fs/fs.o: In function `fsync_dev_lockfs':
> fs/fs.o(.text+0x31a8): undefined reference to `DQUOT_SYNC'
Hm, that's strange. Do evems guys touch quota code at all?
> Are the testing/quota patches recommended for a production box with 2.4.20?
> (Debian 3.0, quota 3.08)
Well, they seem to work well enough. There is no bugreport that I can assotiate with
this quota code for sure.
> Is there a way to get EVMS working with quotas?
Hm. What are evms guys thoughts on that issue?
Bye,
Oleg
next prev parent reply other threads:[~2003-01-25 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 3:02 quotas in 2.4.20 José A. Guzmán
2003-01-25 9:09 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 23:12 Jason Zebchuk
2002-12-03 9:48 ` Oleg Drokin
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=20030125120949.A8569@namesys.com \
--to=green@namesys.com \
--cc=jose@iteso.mx \
--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.