From: Michael Weissenbacher <mw@dermichi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: XFS hang during xfs_fsr run
Date: Thu, 04 Mar 2010 15:20:39 +0100 [thread overview]
Message-ID: <4B8FC1B7.3070505@dermichi.com> (raw)
In-Reply-To: <20100304134641.GA26871@infradead.org>
Hi Christoph/Dave!
> Also when you next rebuilt the kernel please make sure to include
> CONFIG_KALLSYMS in the configuration, possibly CONFIG_KALLSYMS_ALL too.
> This will help greatly with decoding any kind of warning / oops.
Thanks for this information. Unfortunately my current kernel was built
without CONFIG_KALLSYMS. I'm now recompiling with CONFIG_KALLSYMS and
CONFIG_KALLSYMS_ALL set. I reckon that my old traces can't be
ksymoops'ed even if i enable that kernel option now? I will see if i can
get a fresh trace then (even though i hope it won't happen again).
> Was there anything else in the logs prior to the oops messages
> that might indicate errors were occurring?
Unfortunately everything in the logs is dandy until the error happens.
It seems that xfs_fsr randomly stops at some files and then locks up the
whole /var partition. I searched for the inode numbers where xfs_fsr
stopped and one time it was "/var/log/xfs_fsr.log" and the other time it
was "/var/spool/imap/x/user/xxxx/cyrus.cache" (username obfuscated).
Whats's interesting is that i have the no-defrag flag set on the whole
/var/log directory and still it seemed to hang on that log file.
cheers,
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-03-04 14:19 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
2010-03-04 13:46 ` Christoph Hellwig
2010-03-04 14:20 ` Michael Weissenbacher [this message]
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=4B8FC1B7.3070505@dermichi.com \
--to=mw@dermichi.com \
--cc=hch@infradead.org \
--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