From: Dave Chinner <david@fromorbit.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, 6 Feb 2013 08:32:06 +1100 [thread overview]
Message-ID: <20130205213206.GP2667@dastard> (raw)
In-Reply-To: <11083.192.104.24.222.1360088562.squirrel@secure.skymagik.net>
On Tue, Feb 05, 2013 at 01:22:42PM -0500, Tom wrote:
> In a previous message, Dave Chinner wrote:
> >
> > Which doesn't tell us why the filesystem was not unmounted. We need to
> > know why/how the unmount failed to solve the problem, so you'll need to
> > do some debugging of the unmount to try to work that out...
> >
>
> Thanks Dave.
>
> I can work on that tonight.
>
> Oddly, since the problem is kernel related (308 doesn't do it, 348 does),
> the system shuts down the same way no matter what kernel I'm using. So
> what would be the difference? The umounts and running processes shouldn't
> change. Just seems to me that some resource isn't being released. And
> only with kernel 348 and XFS. Quite puzzling..........
>
> Any suggestions on how I would debug this?
Find out if the unmount is returning an error first. If there is no
error, then you need to find what is doing bind mounts on your
system and make sure they are unmounted properly before the final
unmount is done. If lazy unmount is being done, make it a normal
unmount an see where the unmount is getting stcuk or taking time to
complete by using sysrq-w if it gets delayed for any length of time.
FWIW, because this is a old, old kernel, event tracing is not
available, so the single most useful tool for tracking this down is
not available...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-05 21:32 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
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 [this message]
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=20130205213206.GP2667@dastard \
--to=david@fromorbit.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