Date: Tue, 26 Aug 2008 05:37:41 +0200
From: Andreas Kotes <count@flatline.de>
To: Allan Haywood <ahaywood@datallegro.com>
Cc: David Chinner <dgc@sgi.com>, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS internal error
Message-ID: <20080826033741.GX21319@slop.flatline.de>
References: <20080310122216.GG14256@slop.flatline.de> <20080310223018.GA155407@sgi.com> <20080310225927.GP14256@slop.flatline.de> <20080310234539.GC155407@sgi.com> <20080311134746.GQ14256@slop.flatline.de> <20080312175050.GD14256@slop.flatline.de> <20080313000121.GU155407@sgi.com> <20080313071445.GA30874@slop.flatline.de> <20080313071744.GB30874@slop.flatline.de> <C87F050B4C904F44803B22B2F1B67A4462A4D93F@BE181.mail.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C87F050B4C904F44803B22B2F1B67A4462A4D93F@BE181.mail.lan>
User-Agent: Mutt/1.5.17+20080114 (2008-01-14)
Sender: xfs-bounce@oss.sgi.com
Errors-to: xfs-bounce@oss.sgi.com
Precedence: bulk

Hello,

I think that might have been an issue on our FS as well.

No, no resolution, no debugging advice, etc ..

We've basically had to ignore it - and it didn't surface a lot more, now
you mention it. We are working far less close to 100% than before,
though ... *thinking*

   Andreas

* Allan Haywood <ahaywood@datallegro.com> [20080825 20:58]:
> Sorry for top posting on this reply, but I was wondering if there was any resolution to your problem below. We seem to be running into a similar problem. A few hours before the error in this thread occurred the filesystem was filled up to 100%, we had to clean things up to continue running.
> 
> Any additional information would be great.
> 
> -----Original Message-----
> From: xfs-bounce@oss.sgi.com [mailto:xfs-bounce@oss.sgi.com] On Behalf Of Andreas Kotes
> Sent: Thursday, March 13, 2008 12:18 AM
> To: David Chinner
> Cc: xfs@oss.sgi.com
> Subject: Re: XFS internal error
> 
> * Andreas Kotes <count@flatline.de> [20080313 08:14]:
> > * David Chinner <dgc@sgi.com> [20080313 01:01]:
> > > On Wed, Mar 12, 2008 at 06:50:50PM +0100, Andreas Kotes wrote:
> > > > * Andreas Kotes <count-linux@flatline.de> [20080311 14:47]:
> > > > > I basically build a PXE image which does an xfs_repair -L /dev/sda2 from
> > > > > initrd - and the problem persists. Sigh. Exactly no change.
> > >
> > > Do you do this on every boot?
> >
> > no, I did this on a6b and a7b so far, where the problems I mentioned
> > occur, and only after I saw these in-memory problems. in general, XFS
> > proves to be realiable for us.
> >
> > would you recommend running an xfs_check before running an xfs_repair in
> > case of problems?
> 
> oh, btw - running xfs_check doesn't work most of the time, as the log
> usually contains entries, and isn't replayed before shutdown ..
> 
> I figure running this on every boot would leave me killing my log all of
> the time, if the shutdown didn't leave time to write the changes to
> disk? ;)