public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Tue, 26 Aug 2008 05:37:41 +0200	[thread overview]
Message-ID: <20080826033741.GX21319@slop.flatline.de> (raw)
In-Reply-To: <C87F050B4C904F44803B22B2F1B67A4462A4D93F@BE181.mail.lan>

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? ;)

      reply	other threads:[~2008-08-26  3:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <470831E6.4030704@fastmail.co.uk>
2007-10-08  0:14 ` XFS internal error David Chinner
2007-10-08  1:54   ` Max Waterman
2007-10-08  2:32     ` Barry Naujok
2007-10-08  2:48       ` Max Waterman
2008-03-10 12:22   ` Andreas Kotes
2008-03-10 22:30     ` David Chinner
2008-03-10 22:59       ` Andreas Kotes
2008-03-10 23:45         ` David Chinner
2008-03-11 13:47           ` Andreas Kotes
2008-03-12 17:50             ` Andreas Kotes
2008-03-13  0:01               ` David Chinner
2008-03-13  7:14                 ` Andreas Kotes
2008-03-13  7:17                   ` Andreas Kotes
2008-08-25 18:58                     ` Allan Haywood
2008-08-26  3:37                       ` Andreas Kotes [this message]

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=20080826033741.GX21319@slop.flatline.de \
    --to=count@flatline.de \
    --cc=ahaywood@datallegro.com \
    --cc=dgc@sgi.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