| To: | <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS appears to cause strange hang with md raid1 on reboot |
| From: | "Tom" <storm9c1@xxxxxxxxxxxx> |
| Date: | Tue, 5 Feb 2013 13:22:42 -0500 (EST) |
| Cc: | <storm9c1@xxxxxxxxxxxx>, <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Importance: | Normal |
| In-reply-to: | <20130204125510.GL2667@dastard> |
| References: | <32271.192.104.24.222.1359415698.squirrel@xxxxxxxxxxxxxxxxxxx> <20130129151833.GF27055@xxxxxxx> <42720.75.149.17.233.1359515780.squirrel@xxxxxxxxxxxxxxxxxxx> <20130130234650.GE32297@xxxxxxxxxxxxxxxxxx> <45702.75.149.17.233.1359599410.squirrel@xxxxxxxxxxxxxxxxxxx> <20130204125510.GL2667@dastard> |
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? -- Tom |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 0/4] xfstests: seek data/hole and hole punching improvements, Mark Tinguely |
|---|---|
| Next by Date: | Re: XFS appears to cause strange hang with md raid1 on reboot, Dave Chinner |
| Previous by Thread: | Re: XFS appears to cause strange hang with md raid1 on reboot, Dave Chinner |
| Next by Thread: | Re: XFS appears to cause strange hang with md raid1 on reboot, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |