[Top] [All Lists]

Re: XFS appears to cause strange hang with md raid1 on reboot

To: <sandeen@xxxxxxxxxxx>
Subject: Re: XFS appears to cause strange hang with md raid1 on reboot
From: "Tom" <storm9c1@xxxxxxxxxxxx>
Date: Tue, 29 Jan 2013 16:47:59 -0500 (EST)
Cc: <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
Importance: Normal
In-reply-to: <5107124E.70607@xxxxxxxxxxx>
References: <32271.> <5107124E.70607@xxxxxxxxxxx>
In a previous message, Eric Sandeen wrote:
> 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. ;)


Try it with 5.9 and md raid1.  I bet you won't be running it very
much longer.  ;-)

Unless of course you can't reproduce it.

> Just to be absolutely sure, do you have any xfs-kmod or kmod-xfs
> installed? If so, remove it.

No kmod.  I only use the kmod on 32-bit platforms.  As you know, it is
not needed on 64-bit.

This system is a freshly kickstarted system with only about 200 packages
installed (minimal base system just for stability testing):

[root@test9][/root]# rpm -qa | fgrep xfs
[root@test9][/root]# rpm -qa | fgrep kmod
[root@test9][/root]# uname -a
Linux test9.xxxx.xxx 2.6.18-348.el5 #1 SMP Tue Jan 8 17:53:53 EST 2013 x86_6
4 x86_64 x86_64 GNU/Linux

>> (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.

Hmmm, yeah, well I do understand.  ;-)  Just drives me nuts.

> so it's hanging on the way down I guess?
> I see:  "md: md1 switched to read-only mode"
> Was that there before?

Yes.  It's the very last thing printed when using any newer 5.X system.
Then it's supposed to physically reboot or shutdown.  But this is where it
hangs.  I will reply back to the xfs list (to a message from Ben) later
tonight with some more output from the serial console including a

I'll also add these details in the open CentOS bug.

> 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.
> ;)

Any help is appreciated.  Finding this bug may possibly help
ferret out another more possibly nefarious bug, which is why I don't
need instant gratification here.  I'm only looking to assist with the
solution, not cause more stress.

The "company" that I work for from 9-5 has an extensive RHEL 5.X and 6.X
deployment with Satellite, channels, full support, the whole nine yards.
They don't color outside the lines as I do -- they use ext3 for the root
filesystem instead.  Their loss.  :-)

So don't worry, said "company" "gives" plenty to the "cause".  ;-)

However, after 5pm, I do unrelated personal work and projects unrelated
to said "company", and one of those things is working with CentOS and
Ubuntu.  Using XFS quite extensively.

> I'd look at the kernel changelogs for xfs & md, and see if anything
> seems plausible.  Maybe diff the sources & see what changed, etc.

Yeah, I took a half-hearted look already.  But didn't diff any source
code yet.  I saw a freeze/thaw change and a few other md changes that
were suspect.  But haven't had a chance to dig deeper.

Thanks again.

-- Tom

<Prev in Thread] Current Thread [Next in Thread>