From: Eric Sandeen <sandeen@sandeen.net>
To: Tom <storm9c1@skymagik.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS appears to cause strange hang with md raid1 on reboot
Date: Mon, 28 Jan 2013 18:05:34 -0600 [thread overview]
Message-ID: <5107124E.70607@sandeen.net> (raw)
In-Reply-To: <32271.192.104.24.222.1359415698.squirrel@secure.skymagik.net>
On 1/28/13 5:28 PM, Tom wrote:
>
> Dear XFS folks,
>
> I have been using XFS for many years, starting on IRIX and then on RedHat
> 7.2, and now on CentOS/RHEL and Ubuntu. Last time I posted to this
> mailing list was 12 years ago. :-) I've been a happy customer!
>
> I understand that RedHat does not formally support XFS as a root filesystem
> on RHEL.
That's correct. However, I have run xfs root on Centos5, and am
currently running xfs root on RHEL6. On md raid1 in both instances. ;)
> However, up until now, I've been using it very successfully for
> years on both CentOS and Ubuntu. On CentOS, I've successfully patched
> Anaconda since CentOS 5.6 to allow XFS root file system support directly
> from Anaconda (on both bare metal and Xen VMs). Prior to that, I had code
> in %post that would simply migrate an ext3 fs to XFS. And I always run
> md raid1 (except with Xen, since I use mirroring on the dom0). I never use
> hardware RAID since I want to keep my provisioning as generic as possible.
>
> I've deployed many servers using XFS this way and it has always been
> superior for my workloads.... and superior to ext3, and ext4.
>
> ....until CentOS 5.9 came out. Now any systems that are running the stock
> CentOS 5.9 kernel (including 5.X systems upgraded to this kernel) hang
> on reboot. If I downgrade to the 5.8 kernel, the problem is resolved.
Just to be absolutely sure, do you have any xfs-kmod or kmod-xfs installed?
If so, remove it.
> I have taken an engineering approach to testing this problem in efforts
> to help resolve it. I filed a bug with CentOS, but it's probably not
> going to go anywhere upstream since RedHat probably won't support XFS on
> the root filesystem (why I still don't understand, since I fixed the
> issues with Anaconda for myself and can Kickstart systems with XFS all
> day long).
It's for non-technical reasons.
> Therefore I hope anyone here can help. In fact, I was specifically hoping
> to catch Eric Sandeen's attention since this seems like a pretty serious
> regression. It's further aggravated by the fact that RedHat stays behind
> with kernel version and backports modern fixes. I scanned over the
> 2.6.18-348.el5 (stock 5.9 kernel) changelog, and I see a few suspicious
> things, but I'm not sure.
>
> Much more detail is available here (CentOS bug id 0006217) including steps
> to reproduce the problem. Also testing with and without md raid.
> http://bugs.centos.org/view.php?id=6217
so it's hanging on the way down I guess?
I see: "md: md1 switched to read-only mode"
Was that there before?
> The one thing I haven't provided is a traceback. I can provide that if it
> would be helpful.
of course it would be . . .
I don't see anything obvious between the two kernels you mention, and I
can't spend a ton of time digging into this, since most of my day is
taken up supporting the RHEL customers who pay my salary, nudge nudge. ;)
I'd look at the kernel changelogs for xfs & md, and see if anything
seems plausible. Maybe diff the sources & see what changed, etc.
-Eric
> I am not in a big hurry for help, on the contrary I just want to open up
> a dialog since perhaps others might be suffering from this. And I want to
> help resolve it if I can.
>
> Any insight is appreciated.
>
> -- Tom
>
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2013-01-29 0:05 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 [this message]
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
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=5107124E.70607@sandeen.net \
--to=sandeen@sandeen.net \
--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 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.