From: Nathan Scott <nathans@sgi.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>, linux-xfs@oss.sgi.com
Subject: Re: xfs corruption or not
Date: Fri, 4 Jun 2004 15:29:54 +1000 [thread overview]
Message-ID: <20040604052953.GE13756@frodo> (raw)
In-Reply-To: <40BFDB13.7000901@cornell.edu>
On Thu, Jun 03, 2004 at 08:14:43PM -0600, Ivan Gyurdiev wrote:
> ...
> errors. I also did an xfs_repair on the system, which corrected problems..
>
> However, thunderbird still generates the following oops, and then it
> becomes unkillable. Do you think this is most likely due to:
> - memory is still defective
> - there's corruption on-disk which isn't fixed
> or
> - this is an actual bug in xfs
>
> Note that there's no input/output errors after the oops, and only
> thunderbird causes this (so far).
Do you know if the kernel was low on memory at the time? (any
signs of allocation failures in your system log?)
This looks like a memory allocation failure which hasn't been
gracefully handled (or approriately retried) in XFS - there's
a few patches being worked on to improve this, but they aren't
ready to be merged in just yet.
> EFLAGS: 00010206 (2.6.6-1.406)
> EIP is at xfs_bmbt_set_all+0x2f/0x5c [xfs]
> Process thunderbird-bin (pid: 3799, threadinfo=04b32000 task=041aadf0)
> [<0a8c48f7>] xfs_bmap_insert_exlist+0x97/0xae [xfs]
> [<0a8c1cc7>] xfs_bmap_add_extent_hole_delay+0x42f/0x485 [xfs]
cheers.
--
Nathan
next prev parent reply other threads:[~2004-06-04 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 2:14 xfs corruption or not Ivan Gyurdiev
2004-06-04 5:29 ` Nathan Scott [this message]
2004-06-04 6:39 ` Ivan Gyurdiev
2004-06-07 10:39 ` Ivan Gyurdiev
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=20040604052953.GE13756@frodo \
--to=nathans@sgi.com \
--cc=ivg2@cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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 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.