| To: | Keith Owens <kaos@xxxxxxx> |
|---|---|
| Subject: | Re: 2.6.17-rc1 did break XFS |
| From: | Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx> |
| Date: | Thu, 13 Apr 2006 16:17:53 +0200 (MEST) |
| Cc: | Nathan Scott <nathans@xxxxxxx>, dgc@xxxxxxxxxxxxxxxxx, Linux Kernel ML <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, stern@xxxxxxxxxxxxxxxxxxx, sekharan@xxxxxxxxxx |
| In-reply-to: | <9020.1144920230@kao2.melbourne.sgi.com> |
| References: | <9020.1144920230@kao2.melbourne.sgi.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
>notifier_chain_register() is running the existing chain to find the >place where XFS needs to be inserted, and the existing chain is >corrupt. Probably not an XFS problem. > Aye. I booted 2.6.17-rc1 for some minutes to test CSCAN - root filesystem is XFS - and did not have any such early oops. Since `updatedb` happened to run automatically by cron just after I started that laptop, I also would not say it being an XFS problem. I do use VMSPLIT_3G_OPT however. Jan Engelhardt -- |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: server crashing, Artur Makówka |
|---|---|
| Next by Date: | Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Jan Engelhardt |
| Previous by Thread: | TAKE 951944 - barriers on remount,ro, Nathan Scott |
| Next by Thread: | Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Jan Engelhardt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |