From: David Chinner <dgc@sgi.com>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: David Chinner <dgc@sgi.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.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: Thu, 7 Jun 2007 23:05:05 +1000 [thread overview]
Message-ID: <20070607130505.GE85884050@sgi.com> (raw)
In-Reply-To: <BAY103-DAV7076D9B4230E07680B724B2260@phx.gbl>
On Thu, Jun 07, 2007 at 09:44:51AM +0200, Marco Berizzi wrote:
> Hi David.
> Three months ago I wrote the message below.
> I had built various 2.6.20.x and 2.6.21.x
> vanilla kernel with all the debug options
> enabled and linux had never crashed.
> On june 4, I have builded linux 2.6.21.3 without
> any debugging options and after 2 days linux
> has starting print these errors:
>
> Jun 6 09:47:09 Pleiadi kernel: =======================
> Jun 6 09:47:09 Pleiadi kernel: 0x0: 28 f1 45 d4 22 53 35 11 09 80 37 5a
> 47 8a 22 ee
> Jun 6 09:47:09 Pleiadi kernel: Filesystem "sda8": XFS internal error
> xfs_da_do_buf(2) at line 2086 of file fs/xfs/xfs_da_btree.c. Caller
> 0xc01b2301
> Jun 6 09:47:09 Pleiadi kernel: [<c01b21f7>] xfs_da_do_buf+0x70c/0x7b1
> Jun 6 09:47:09 Pleiadi kernel: [<c01b2301>] xfs_da_read_buf+0x30/0x35
> Jun 6 09:47:09 Pleiadi kernel: [<c01b2301>] xfs_da_read_buf+0x30/0x35
These above stack trace is the sign of a corrupted directory.
Chopping out the rest of the top posting (please don't do that)
we get down to 3 months ago:
> > On Mon, Mar 19, 2007 at 11:32:27AM +0100, Marco Berizzi wrote:
> > > Marco Berizzi wrote:
> > > Here is the relevant results:
> > >
> > > Phase 2 - found root inode chunk
> > > Phase 3 - ...
> > > agno = 0
> > > ...
> > > agno = 12
> > > LEAFN node level is 1 inode 1610612918 bno = 8388608
> >
> > Hmmm - single bit error in the bno - that reminds of this:
> >
> > http://oss.sgi.com/projects/xfs/faq.html#dir2
> >
> > So I'd definitely make sure that is repaired....
Where we saw signs of on disk directory corruption. Have you run
xfs_repair successfully on the filesystem since you reported
this?
If you did clean up the error, does xfs_repair report the same sort
of error again?
Have you run a 2.6.16-rcX or 2.6.17.[0-6] kernel since you last
reported this problem?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-06-07 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 11:34 XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller 0xc01b00bd 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 [this message]
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
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=20070607130505.GE85884050@sgi.com \
--to=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.com \
--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