From: tabris <tabris@tabris.net>
To: Vladimir Saveliev <vs@namesys.com>
Cc: Andrew Morton <akpm@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at fs/inode.c:1116 with 2.6.10-rc{2-mm4,3-mm1}[repost]
Date: Sun, 2 Jan 2005 05:15:33 -0500 [thread overview]
Message-ID: <200501020515.35586.tabris@tabris.net> (raw)
In-Reply-To: <200412280146.27438.tabris@tabris.net>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Tuesday 28 December 2004 1:46 am, tabris wrote:
> On Friday 24 December 2004 10:54 am, Vladimir Saveliev wrote:
> > Hello
> >
> > On Fri, 2004-12-24 at 18:31, tabris wrote:
> > > On Friday 24 December 2004 3:09 am, Andrew Morton wrote:
> > > > tabris <tabris@tabris.net> wrote:
> > > > > Attached are the BUG reports for 2.6.10-rc2-mm4 (multiple
> > > > > BUG reports) and one from 2.6.10-rc3-mm1, plus dmesg from
> > > > > 2.6.10-rc3-mm1.
> > > >
> > > > Are you using quotas?
> > >
> > > Yes, I am using quotas.
> > >
> > > > What filesystem types are in use?
> > >
> > > I'm using reiserFS and XFS mostly, with one ext2 partition
> > > (/boot, mounted -o sync)
> >
> > Would you please try to reproduce this problem with:
> > http://marc.theaimsgroup.com/?l=reiserfs&m=110381606727976&q=p3
>
> Using the patch mentioned above, 14 hours uptime and no BUG yet.
> more stress testing needed however before I can declare all is well.
5 days uptime, appears to be fixed. Thanks for the patch.
>
--
tabris
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-02 10:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 0:23 kernel BUG at fs/inode.c:1116 with 2.6.10-rc{2-mm4,3-mm1}[repost] tabris
2004-12-24 8:09 ` Andrew Morton
2004-12-24 15:31 ` tabris
2004-12-24 15:54 ` Vladimir Saveliev
2004-12-24 18:45 ` Andrew Morton
2004-12-28 6:46 ` tabris
2005-01-02 10:15 ` tabris [this message]
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=200501020515.35586.tabris@tabris.net \
--to=tabris@tabris.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox