public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Tom <storm9c1@skymagik.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS appears to cause strange hang with md raid1 on reboot
Date: Wed, 30 Jan 2013 16:51:25 -0600	[thread overview]
Message-ID: <20130130225125.GO27055@sgi.com> (raw)
In-Reply-To: <42720.75.149.17.233.1359515780.squirrel@secure.skymagik.net>

Hi Tom,

On Tue, Jan 29, 2013 at 10:16:20PM -0500, Tom wrote:
> I've update the CentOS bug (http://bugs.centos.org/view.php?id=6217) with
> the following information:
> 
> 
> -- More detail about the hang including traceback --
> 
> Using 5.9 kernel (348) without md raid:
> Please stand by while rebooting the system...
> md: stopping all md devices.
> Synchronizing SCSI cache for disk sda:
> Restarting system.
> ..
> machine restart
> (reboots normally)
> 
> 
> With md raid1:
> Unmounting pipe file systems:
> Unmounting file systems:
> Please stand by while rebooting the system...
> md: stopping all md devices.
> md: md2 switched to read-only mode.
> md: md1 switched to read-only mode.
> (hang)
> 
> Traceback:
> INFO: task reboot:2063 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> reboot        D ffff810037df37e0     0  2063      1                  19
> (NOTLB)
>  ffff81005890ba08 0000000000000082 ffff81005890ba58 ffff81005beb1ea0
>  0000000000000001 0000000000000007 ffff810058d67040 ffff810037df37e0
>  000000596dd8a1e6 0000000000003df4 ffff810058d67228 000000008008d76f
> Call Trace:
>  [<ffffffff8002e4bc>] __wake_up+0x38/0x4f
>  [<ffffffff80223bce>] md_write_start+0xf2/0x108
>  [<ffffffff800a3bc2>] autoremove_wake_function+0x0/0x2e
>  [<ffffffff8000ab62>] get_page_from_freelist+0x380/0x442
>  [<ffffffff880b102c>] :raid1:make_request+0x38/0x5d8
>  [<ffffffff8001c839>] generic_make_request+0x211/0x228
>  [<ffffffff8002389f>] mempool_alloc+0x31/0xe7
>  [<ffffffff8001a98f>] vsnprintf+0x5d7/0xb54
>  [<ffffffff80033695>] submit_bio+0xe6/0xed

I think you should consider copying linux-raid@vger.kernel.org.

Did you have a chance to get the sysrq output?  It would be helpful to see the
other tasks on your machine.

Regards,
	Ben

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

  reply	other threads:[~2013-01-30 22:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 23:28 XFS appears to cause strange hang with md raid1 on reboot Tom
2013-01-29  0:05 ` Eric Sandeen
2013-01-29 21:47   ` Tom
2013-01-29 21:55     ` Eric Sandeen
2013-01-29 22:25       ` Tom
2013-01-29 22:39         ` Ben Myers
2013-01-30  8:54         ` Stan Hoeppner
2013-01-29 15:18 ` Ben Myers
2013-01-29 21:13   ` Tom
2013-01-30  3:16   ` Tom
2013-01-30 22:51     ` Ben Myers [this message]
2013-01-30 23:46     ` Dave Chinner
2013-01-31  2:30       ` Tom
2013-02-04 12:55         ` Dave Chinner
2013-02-05 18:22           ` Tom
2013-02-05 21:32             ` Dave Chinner
2013-02-05 23:05               ` Tom
2013-02-06  4:08               ` Tom
2013-02-06 23:51                 ` Dave Chinner
2013-02-07  4:18                   ` Tom
2013-01-31  7:35       ` Stefan Ring
  -- strict thread matches above, loose matches on Subject: below --
2013-01-31  2:34 Tom

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=20130130225125.GO27055@sgi.com \
    --to=bpm@sgi.com \
    --cc=storm9c1@skymagik.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