public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Sven Geggus <lists@fuchsschwanzdomain.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS oops in vanilla 2.6.24
Date: Mon, 4 Feb 2008 09:25:25 +1100	[thread overview]
Message-ID: <20080203222525.GX155407@sgi.com> (raw)
In-Reply-To: <20080203222034.GA7460@diesel.geggus.net>

On Sun, Feb 03, 2008 at 11:20:34PM +0100, Sven Geggus wrote:
> David Chinner schrieb am Sonntag, den 03. Februar um 23:13 Uhr:
> 
> > How long after mount does this happen? Does it happen when listing a specific
> > directory? i.e. do you have a reproducable test case for it?
> 
> Well, it happens very soon after mounting the device. Typically when
> doing ls or something trivial like this. Unfortunately this is not
> really reproducable but it does happen reproducable on one specific
> device here sooner or later when booting into 2.6.24.

Ok. Can you use xfs_metadump to grab an image of the filesystem that you
are using to reproduce this and put it up somewhere on the web so I can
try to reproduce it locally?

> I run xfs-repair just to make shure that the filesystem is not
> corrupted. Works fine when booting 2.6.23.8 which I have been using
> before.

Good - that saves me from having to ask. ;)

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

      parent reply	other threads:[~2008-02-03 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fnqmbl$ubh$1@ultimate100.geggus.net>
     [not found] ` <1201778591.28547.291.camel@lappy>
2008-02-03 22:13   ` XFS oops in vanilla 2.6.24 David Chinner
     [not found]     ` <20080203222034.GA7460@diesel.geggus.net>
2008-02-03 22:25       ` David Chinner [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=20080203222525.GX155407@sgi.com \
    --to=dgc@sgi.com \
    --cc=lists@fuchsschwanzdomain.de \
    --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