All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Kotes <count@flatline.de>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error
Date: Thu, 13 Mar 2008 08:14:45 +0100	[thread overview]
Message-ID: <20080313071445.GA30874@slop.flatline.de> (raw)
In-Reply-To: <20080313000121.GU155407@sgi.com>

Hallo Dave,

* 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?

Br,

   Andreas

-- 
flatline IT services - Andreas Kotes - Tailored solutions for your IT needs

  reply	other threads:[~2008-03-13  7:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-07  1:09 XFS internal error Max Waterman
2007-10-08  0:14 ` 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 [this message]
2008-03-13  7:17                   ` Andreas Kotes
2008-08-25 18:58                     ` Allan Haywood
2008-08-26  3:37                       ` Andreas Kotes
  -- strict thread matches above, loose matches on Subject: below --
2006-08-26 16:06 Gerardo Exequiel Pozzi
2006-08-26 17:05 ` Jeffrey Hundstad

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=20080313071445.GA30874@slop.flatline.de \
    --to=count@flatline.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.