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.
Thanks.
-Allan Haywood
-----Original Message-----
From: xfs-bounce@xxxxxxxxxxx [mailto:xfs-bounce@xxxxxxxxxxx] On Behalf Of
Andreas Kotes
Sent: Thursday, March 13, 2008 12:18 AM
To: David Chinner
Cc: xfs@xxxxxxxxxxx
Subject: Re: XFS internal error
Hello,
* Andreas Kotes <count@xxxxxxxxxxx> [20080313 08:14]:
> * David Chinner <dgc@xxxxxxx> [20080313 01:01]:
> > On Wed, Mar 12, 2008 at 06:50:50PM +0100, Andreas Kotes wrote:
> > > * Andreas Kotes <count-linux@xxxxxxxxxxx> [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? ;)
Andreas
--
flatline IT services - Andreas Kotes - Tailored solutions for your IT needs
|