public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: KELEMEN Peter <Peter.Kelemen@cern.ch>
To: xfs@oss.sgi.com
Subject: Re: 2.6.24-rc3 oopses while mounting fs
Date: Tue, 4 Dec 2007 10:42:29 +0100	[thread overview]
Message-ID: <20071204094229.GC2074@luba> (raw)
In-Reply-To: <47549B1A.4070508@sgi.com>

* Timothy Shimmin (tes@sgi.com) [20071204 11:11]:

Timothy,

Thanks for the recommendations.

> Often it is simplest to save the log using the -C option to a
> file.  -C filename [...] The log can then be analysed in various
> ways later.

I did that (I played with it and did the same thing with dd(1),
too).

> If you want to save the filesystem away for possible metadata
> debugging later, then xfs_metadump is your friend.

I'll check this out.  I watched Barry implement the thing but we
were stuck in the past for a while with xfsprogs-2.6.x.

Peter

-- 
    .+'''+.         .+'''+.         .+'''+.         .+'''+.         .+''
 Kelemen Péter     /       \       /       \     Peter.Kelemen@cern.ch
.+'         `+...+'         `+...+'         `+...+'         `+...+'

      parent reply	other threads:[~2007-12-04  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 13:45 2.6.24-rc3 oopses while mounting fs KELEMEN Peter
2007-11-28 23:56 ` Lachlan McIlroy
2007-11-30 22:31   ` KELEMEN Peter
2007-12-03  3:24     ` Lachlan McIlroy
2007-12-03 22:02       ` KELEMEN Peter
2007-12-04  0:11         ` Timothy Shimmin
2007-12-04  7:08           ` Lachlan McIlroy
2007-12-04  9:57             ` KELEMEN Peter
2007-12-05  5:47             ` Lachlan McIlroy
2007-12-05  6:38               ` Timothy Shimmin
2007-12-05  7:04                 ` Lachlan McIlroy
2007-12-04  9:42           ` KELEMEN Peter [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=20071204094229.GC2074@luba \
    --to=peter.kelemen@cern.ch \
    --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