public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Michael Weissenbacher <mw@dermichi.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS hang during xfs_fsr run
Date: Fri, 5 Mar 2010 00:15:11 +1100	[thread overview]
Message-ID: <20100304131511.GH14317@discord.disaster> (raw)
In-Reply-To: <4B8FA2CD.6010904@dermichi.com>

On Thu, Mar 04, 2010 at 01:08:45PM +0100, Michael Weissenbacher wrote:
> Hi Dave!
>> Can you run the trace through ksymoops so that we get function names
>> rather than numbers that don't mean anything?
> I've never done that before. Could you point me to an howto about this?

I've never needed to use it myself, so all I'd be doing is reading
the man page and doing a google search to answer your question. It's
way past my bed time here, so I'll leave that to you for the
moment - try searching for "ksymoops howto"....

>> Also, can you tell us what kernel version and distro you are
>> running, as well as the version of xfs_fsr? These will help tell us
>> if it is a new or known problem.
> The Kernel version is 2.6.33 vanilla (self-compiled), Distro is Gentoo  
> Linux, xfs_fsr Version is 3.1.1 (also self-compiled).

Ok, so it's all pretty recent then.

> Please let me know if you need anything else.

Was there anything else in the logs prior to the oops messages
that might indicate errors were occurring?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-03-04 13:13 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 10:10 XFS hang during xfs_fsr run Michael Weissenbacher
2010-03-04 11:20 ` Dave Chinner
2010-03-04 12:08   ` Michael Weissenbacher
2010-03-04 13:15     ` Dave Chinner [this message]
2010-03-04 13:46       ` Christoph Hellwig
2010-03-04 14:20         ` Michael Weissenbacher
2010-03-04 14:30           ` Christoph Hellwig
2010-03-04 17:14             ` Michael Weissenbacher
2010-03-04 22:26           ` Dave Chinner
2010-03-05  9:04             ` Michael Weissenbacher
2010-03-06 21:20             ` Michael Weissenbacher
2010-03-08  0:06               ` Dave Chinner
2010-03-08 12:17                 ` Michael Weissenbacher
2010-03-08 18:09                   ` Eric Sandeen
2010-03-09  9:14                     ` Michael Weissenbacher
2010-03-09 11:38                       ` Dave Chinner
2010-03-09 12:09                         ` Michael Weissenbacher
2010-03-10  8:46                     ` Michael Weissenbacher
2010-03-11 23:39                       ` Dave Chinner
2010-03-12  9:45                         ` Michael Weissenbacher
2010-03-12 10:00                           ` Christoph Hellwig
2010-03-12 10:36                             ` Michael Weissenbacher
2010-03-12 11:56                             ` Dave Chinner
2010-03-12 14:27                               ` Christoph Hellwig
2010-03-13  0:25                                 ` Dave Chinner
2010-04-16  8:10 ` Michael Monnerie
2010-04-16 10:50   ` Michael Weissenbacher

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=20100304131511.GH14317@discord.disaster \
    --to=david@fromorbit.com \
    --cc=mw@dermichi.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