| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: XFS backtrace with kernel 2.6.6 |
| From: | "Kevin P. Fleming" <kpfleming@xxxxxxxxxxxxxxxxxxxx> |
| Date: | Thu, 20 May 2004 18:17:20 -0700 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040521105124.B653735@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Organization: | Back To Basics Network Management |
| References: | <40AD491A.7020805@xxxxxxxxxxxxxxxxxxxx> <20040521105124.B653735@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.6 (Windows/20040502) |
Nathan Scott wrote: A corrupt directory block from the look of it - did xfs_repair find anything? Any kind of disk or block layer errors in your logs? I was not able to take the system down to try xfs_repair, but I can do that tomorrow. No other errors in the logs at all, just about 10 of these in order (captured via a serial console, so I'm pretty sure nothing got missed). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS backtrace with kernel 2.6.6, Nathan Scott |
|---|---|
| Next by Date: | Re: Bug#249429: xfslibs-dev: xfs/swab.h not ISO-C(++) compliant (fwd), Nathan Scott |
| Previous by Thread: | Re: XFS backtrace with kernel 2.6.6, Nathan Scott |
| Next by Thread: | [Bug 200] xfs_check should set the exit code to non-zero if the filesystem does not check out, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |