From: Dave Chinner <david@fromorbit.com>
To: Sagar Borikar <sagar_borikar@pmc-sierra.com>
Cc: xfs@oss.sgi.com
Subject: Re: Xfs Access to block zero exception and system crash
Date: Sat, 28 Jun 2008 10:05:16 +1000 [thread overview]
Message-ID: <20080628000516.GD29319@disturbed> (raw)
In-Reply-To: <4864C001.2010308@pmc-sierra.com>
On Fri, Jun 27, 2008 at 03:55:05PM +0530, Sagar Borikar wrote:
>
> Dave,
>
> I also got continuous exceptions
>
>
> XFS internal error XFS_WANT_CORRUPTED_RETURN at line 296 of file
> fs/xfs/xfs_alloc.c. Caller 0x802962c0
corrupt alloc btree. xfs_repair won't report errors in this btree;
it simply rebuilds it. xfs_check will report errors in it, though.
> So memory was also not available for pdflush threads to flush the data
> back to disks. But when
nothing to do with memory availabilty, I think.
FWIW, can you send the output of xfs_growfs -n <mntpt> and details
of the partitioning and volume config?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-06-28 0:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-24 7:03 Xfs Access to block zero exception and system crash Sagar Borikar
2008-06-25 6:48 ` Sagar Borikar
2008-06-25 8:49 ` Dave Chinner
2008-06-26 6:46 ` Sagar Borikar
2008-06-26 7:02 ` Dave Chinner
2008-06-27 10:13 ` Sagar Borikar
2008-06-27 10:25 ` Sagar Borikar
2008-06-28 0:05 ` Dave Chinner [this message]
2008-06-28 16:47 ` Sagar Borikar
2008-06-29 21:56 ` Dave Chinner
2008-06-30 3:37 ` Sagar Borikar
[not found] ` <20080630034112.055CF18904C4@bby1mta01.pmc-sierra.bc.ca>
2008-06-30 6:07 ` Sagar Borikar
2008-06-30 10:24 ` Sagar Borikar
2008-07-01 6:44 ` Dave Chinner
2008-07-02 4:18 ` Sagar Borikar
2008-07-02 5:13 ` Dave Chinner
2008-07-02 5:35 ` Sagar Borikar
2008-07-02 6:13 ` Nathan Scott
2008-07-02 6:56 ` Dave Chinner
2008-07-02 11:02 ` Sagar Borikar
2008-07-03 4:03 ` Eric Sandeen
2008-07-03 5:14 ` Sagar Borikar
2008-07-03 15:02 ` Eric Sandeen
2008-07-04 10:18 ` Sagar Borikar
2008-07-04 12:27 ` Dave Chinner
2008-07-04 17:30 ` Sagar Borikar
2008-07-04 17:35 ` Eric Sandeen
2008-07-04 17:51 ` Sagar Borikar
2008-07-05 16:25 ` Eric Sandeen
2008-07-06 17:24 ` Sagar Borikar
2008-07-06 19:07 ` Eric Sandeen
2008-07-07 3:02 ` Sagar Borikar
2008-07-07 3:04 ` Eric Sandeen
2008-07-07 3:07 ` Sagar Borikar
2008-07-07 3:11 ` Eric Sandeen
2008-07-07 3:17 ` Sagar Borikar
2008-07-07 3:22 ` Eric Sandeen
2008-07-07 3:42 ` Sagar Borikar
[not found] ` <487191C2.6090803@sandeen .net>
[not found] ` <4871947D.2090701@pmc-sierr a.com>
2008-07-07 3:47 ` Eric Sandeen
2008-07-07 3:58 ` Sagar Borikar
2008-07-07 5:19 ` Eric Sandeen
2008-07-07 5:58 ` Sagar Borikar
2008-07-06 4:19 ` Dave Chinner
2008-07-04 15:33 ` Eric Sandeen
2008-06-28 0:02 ` Dave Chinner
[not found] <4872E0BC.6070400@pmc-sierra.com>
[not found] ` <4872E33E.3090107@sandeen.net>
2008-07-08 5:03 ` Sagar Borikar
2008-07-09 16:57 ` Sagar Borikar
2008-07-10 5:12 ` Sagar Borikar
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=20080628000516.GD29319@disturbed \
--to=david@fromorbit.com \
--cc=sagar_borikar@pmc-sierra.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