All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: William Moss <bill.m.moss@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfsdump
Date: Sun, 18 Dec 2011 19:50:30 -0600	[thread overview]
Message-ID: <4EEE9866.2030603@sandeen.net> (raw)
In-Reply-To: <CAEt9JqzmcRT2g6z1k3t5eFM7e1rvrrHQRf_enpvJx+HXgwOERA@mail.gmail.com>

On 12/17/11 11:22 AM, William Moss wrote:
> Since approx. kernel 2.6.35 (kernel.org <http://kernel.org>) I have
> been having a problem with xfsdump(8) with my custom compiled kernels
> but not with the one that comes with openSUSE. During a differential
> dump (1..9) it will lock up, become a kernel stuck process that
> cannot be killed, while determining the files that need to be dumped.
> This has not occurred with dump level zero nor with the kernel as
> supplied from openSUSE. I have played with the kernel options that
> seem relevant to xfs (a find for xfs as well as ACPI, etc.) and
> nothing seems to effect the problem. Other than this, everything
> works fine and the kernel has better performance and support in the
> areas that I compile it for with respect to my hardware. I was hoping
> that you could inform me as to what options for the kernel might
> cause this problem. Note that a reboot or even an 'init 0 --- init 3'
> will clear the problem for at least one more differential dump.
> 
> openSUSE: 11.4 CPU : AMD 64 AM2 socket RAM: 4GB DDR2 Drives: SATA/3
> Boot is a 650GB WD, /usr/local is a 1.5TB WD
> 
> Kernel: 3.1.4 I compile the kernel with the AMD64 optimization turned
> on.

If the kernel thread is really stuck, sysrq-D (or echo d > /proc/sysrq-trigger)
will show where the thread is; that'd at least provide some more concrete
information if the thread is really stuck somewhere.

-Eric

> Thank you!
> 
> 
> _______________________________________________ xfs mailing list 
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs

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

      reply	other threads:[~2011-12-19  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 17:22 xfsdump William Moss
2011-12-19  1:50 ` Eric Sandeen [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=4EEE9866.2030603@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=bill.m.moss@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.