| 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@pmc-sierra.com> |
| Mail-followup-to: | Sagar Borikar <sagar_borikar@xxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <340C71CD25A7EB49BFA81AE8C839266701323BD8@BBY1EXM10.pmc_nt.nt.pmc-sierra.bc.ca> <20080625084931.GI16257@build-svl-1.agami.com> <340C71CD25A7EB49BFA81AE8C839266701323BE8@BBY1EXM10.pmc_nt.nt.pmc-sierra.bc.ca> <20080626070215.GI11558@disturbed> <4864BD5D.1050202@pmc-sierra.com> <4864C001.2010308@pmc-sierra.com> |
| 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 |
| Previous by Date: | Re: Xfs Access to block zero exception and system crash, Dave Chinner |
|---|---|
| Next by Date: | Re: rfc: kill ino64 mount option, Dave Chinner |
| Previous by Thread: | Re: Xfs Access to block zero exception and system crash, Sagar Borikar |
| Next by Thread: | RE: Xfs Access to block zero exception and system crash, Sagar Borikar |
| Indexes: | [Date] [Thread] [Top] [All Lists] |