xfs
[Top] [All Lists]

Re: Xfs Access to block zero exception and system crash

To: Sagar Borikar <sagar_borikar@xxxxxxxxxxxxxx>
Subject: Re: Xfs Access to block zero exception and system crash
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sat, 28 Jun 2008 10:05:16 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <4864C001.2010308@xxxxxxxxxxxxxx>
Mail-followup-to: Sagar Borikar <sagar_borikar@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
References: <340C71CD25A7EB49BFA81AE8C839266701323BD8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080625084931.GI16257@xxxxxxxxxxxxxxxxxxxxx> <340C71CD25A7EB49BFA81AE8C839266701323BE8@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080626070215.GI11558@disturbed> <4864BD5D.1050202@xxxxxxxxxxxxxx> <4864C001.2010308@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.17+20080114 (2008-01-14)
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@xxxxxxxxxxxxx


<Prev in Thread] Current Thread [Next in Thread>