From: "Marco Berizzi" <pupilla@hotmail.com>
To: "David Chinner" <dgc@sgi.com>
Cc: "David Chinner" <dgc@sgi.com>, <linux-kernel@vger.kernel.org>,
<xfs@oss.sgi.com>, "Marco Berizzi" <pupilla@hotmail.com>
Subject: Re: XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller 0xc01b00bd
Date: Tue, 12 Jun 2007 09:14:27 +0200 [thread overview]
Message-ID: <BAY103-DAV164930BAD25A9841FEF442B2190@phx.gbl> (raw)
In-Reply-To: <20070612061440.GQ86004887@sgi.com>
David Chinner wrote:
> On Fri, Jun 08, 2007 at 03:59:39PM +0200, Marco Berizzi wrote:
> > David Chinner wrote:
> > > Where we saw signs of on disk directory corruption. Have you run
> > > xfs_repair successfully on the filesystem since you reported
> > > this?
> >
> > yes.
> >
> > > If you did clean up the error, does xfs_repair report the same
sort
> > > of error again?
> >
> > I have run xfs_repair this morning.
> > Here is the report:
>
> <reports no on disk errors>
>
> > > Have you run a 2.6.16-rcX or 2.6.17.[0-6] kernel since you last
> > > reported this problem?
> >
> > No. I have run only 2.6.19.x and 2.6.21.x
> >
> > After the xfs_repair I have remounted the file system.
> > After few hours linux has crashed with this message:
> > BUG: at arch/i386/kernel/smp.c:546 smp_call_function()
> > I have also the monitor bitmap.
>
> This is sounding like memory corruption is no corruption is being
> found on disk by xfs_repair. Have you run memtest86 on that box to
> see if it's got bad memory?
Yes. I have run memtest for one week:
no errors.
I have also changed the mother board,
scsi controller and ram. Only the cpu
and the 2 hot swap scsi disks were
not replaced. IMHO this isn't an
hardware problem, because the kernel
with debugging options enabled didn't
crash for a long time (>1 month). Just
for record, at this moment this box is
running 2.6.22-rc4 with no debug
options enabled. I will keep you
informed.
Thanks everybody for the support.
next prev parent reply other threads:[~2007-06-12 7:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 11:34 Marco Berizzi
2007-03-16 1:25 ` David Chinner
[not found] ` <BAY103-DAV13EC09E9BCB3E8C9D5EEA2B2710@phx.gbl>
2007-03-16 19:59 ` David Chinner
2007-03-17 13:00 ` Marco Berizzi
[not found] ` <BAY103-DAV9C465F21C87A900314523B2760@phx.gbl>
2007-03-20 6:46 ` David Chinner
2007-06-07 7:44 ` Marco Berizzi
2007-06-07 13:05 ` David Chinner
2007-06-08 13:59 ` Marco Berizzi
2007-06-10 7:05 ` Satyam Sharma
2007-06-10 12:20 ` Marco Berizzi
2007-06-10 22:54 ` Satyam Sharma
2007-06-12 6:14 ` David Chinner
2007-06-12 7:14 ` Marco Berizzi [this message]
2007-06-19 10:36 ` Marco Berizzi
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=BAY103-DAV164930BAD25A9841FEF442B2190@phx.gbl \
--to=pupilla@hotmail.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.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
all inboxes | Powered by JetHome®