From: klaus thorn <klaus@trillke.net>
To: Jan Kara <jack@ucw.cz>
Cc: reiserfs-list@namesys.com, edv@trillke.net
Subject: Re: Status of quota support for reiserfs on 2.6.x kernels
Date: Tue, 28 Dec 2004 21:55:03 +0100 [thread overview]
Message-ID: <20041228205503.GA17689@trillke.net> (raw)
In-Reply-To: <20041215133805.GE25999@atrey.karlin.mff.cuni.cz>
Thanks for your patch and your comments!
On Wed, Dec 15, 2004 at 02:38:06PM +0100, Jan Kara wrote:
> > I tried to use quota with 2.6.7 and got two serious problems
> I suggest trying some newer kernel - either 2.6.10-rc3-mm1 or
> just plain 2.6.10-rc3 with attached patch applied (the patch fixes the
> deadlock you seem to hit).
It tried the latter on another server and the filesystem was accessible
at all time but other problems occured (maybe not quota-related) that made
my co-admins downgrade to 2.6.9:
1. suddenly, after running the patched kernel for days,
su, sudo and authentication through courier webmailer was not possible,
ssh-root-login went fine. After reboot problem was gone but pam_rootok.so
was missing (file system curruption?)
2. after a few hours stress-testing the quota-partition:
kernel crash: code ff 21 e2 8b 0a ...
... 76 60 e0 ff 6a 00
kernel BUG at lib/kernel_lock:120!
invalid operand: 0000
Do you think they are quota-related or related to you quota-fixall patch?
Is your fix appliable for vanilla 2.6.10 or is it already integrated or is there a newer patch?
--
klaus thorn klaus@trillke.net
next prev parent reply other threads:[~2004-12-28 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 9:53 Status of quota support for reiserfs on 2.6.x kernels Philippe Gramoullé
2004-11-23 13:06 ` Christian Mayrhuber
2004-11-23 13:13 ` Philippe Gramoullé
2004-11-23 14:01 ` Jan Kara
2004-12-15 0:29 ` Klaus Thorn
2004-12-15 6:16 ` B S Srinidhi
2004-12-15 6:19 ` Christian Mayrhuber
2004-12-15 13:38 ` Jan Kara
2004-12-28 20:55 ` klaus thorn [this message]
2005-01-04 17:52 ` Jan Kara
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=20041228205503.GA17689@trillke.net \
--to=klaus@trillke.net \
--cc=edv@trillke.net \
--cc=jack@ucw.cz \
--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.