From: Bernd Schubert <bernd-schubert@gmx.de>
To: Jan Kara <jack@suse.cz>
Cc: reiserfs-list@namesys.org, linux-kernel@vger.kernel.org
Subject: Re: quota problem with 2.6.15.7
Date: Tue, 5 Sep 2006 12:08:43 +0200 [thread overview]
Message-ID: <200609051208.43857.bernd-schubert@gmx.de> (raw)
In-Reply-To: <20060905091924.GC3830@atrey.karlin.mff.cuni.cz>
Hello Jan,
On Tuesday 05 September 2006 11:19, Jan Kara wrote:
> Hello,
>
> > I just wanted to enable quotas on one of our server systems and got an
> > oops. This is an opteron system with a kernel in 64bit mode.
> > As you can see, the filesystem is reiserfs.
>
> Hmm, is this reproducible? Any chances of trying out some newer
> kernel?
[trace deleted]
> Hmm, the trace looks strange... It is definitely mixed with some old
> data. We definitely reached reiserfs_quota_on() but didn't reach
> vfs_quota_on() so it seems we crashed somewhere in path_lookup() (also
> link_path_walk() in the beginning of the trace suggests that). That's
> generic VFS code so maybe this is nothing quota specific. So this looks
> quite hard to debug if there's no reasonable way of reproducing it.
Its reproducible, I hoped it wouldn't happen again after a reboot, but
unfortunately it did. Trying a newer kernel, hmm, usually a problem on server
systems. I will try to test quotas on another amd64 system first(*).
Thanks for your help,
Bernd
(*) Which would be easy, if there wouldn't be a 64bit kernel, 32bit glibc,
nfsclient inode truncation bug, which forces me to run all of our amd64
nfsroot-clients with a 32bit kernel, http://lkml.org/lkml/2005/2/28/172.
Well, my fault that I still didn't submit a glibc bug report.
--
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
next prev parent reply other threads:[~2006-09-05 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-02 13:57 quota problem with 2.6.15.7 Bernd Schubert
2006-09-05 9:19 ` Jan Kara
2006-09-05 10:08 ` Bernd Schubert [this message]
2006-10-06 11:55 ` Bernd Schubert
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=200609051208.43857.bernd-schubert@gmx.de \
--to=bernd-schubert@gmx.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox