public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Volker <mail@blafoo.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: OOM on quotacheck (again?)
Date: Tue, 02 Oct 2012 22:49:27 +0200	[thread overview]
Message-ID: <506B5357.6060609@blafoo.org> (raw)
In-Reply-To: <20121002200946.GP23520@dastard>

Hi,

>> If its of any interest, i can supply the stack-traces.
> 
> Yes, it is of interest, can you post everything you found out about
> the problem? (dmesg, stack traces, repair output, etc).

Everything posted here is from a single server and its chronologically
top to bottom. Without having checked each and every stacktrace, it
looked quite similar on the other servers.

http://pastebin.com/PXquE4sM

Sidenote:
The xfs_repair would not finish without supplying -P, otherwise the
repair hang in phase 6 (might be related to this bug:
http://oss.sgi.com/archives/xfs-masters/2011-01/msg00009.html)

Hope it helps! Since we have about 300 servers left to go from 2.6.37 to
3.6, i'd be happy to do some testing as long we are not gambling with
our customers data :-)

- volker



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

  reply	other threads:[~2012-10-02 20:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 14:12 OOM on quotacheck (again?) blafoo
2012-09-19 20:59 ` Dave Chinner
2012-09-20  9:32   ` Volker
2012-09-24 13:21     ` Dave Chinner
2012-09-24 14:47       ` Volker
2012-10-02 16:29         ` Volker
2012-10-02 20:09           ` Dave Chinner
2012-10-02 20:49             ` Volker [this message]
2012-10-02 22:15               ` Dave Chinner
2012-10-04 14:19                 ` Volker

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=506B5357.6060609@blafoo.org \
    --to=mail@blafoo.org \
    --cc=david@fromorbit.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