| To: | Simon Matter <simon.matter@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS filesystem shutdown |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | 10 Dec 2003 15:15:03 -0600 |
| Cc: | Mike Brodbelt <m.brodbelt@xxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1432.10.1.200.117.1071040970.squirrel@imap01.ch.sauter-bc.com> |
| Organization: | Eric Conspiracy Secret Labs |
| References: | <3FD5ED83.7000500@acu.ac.uk> <1432.10.1.200.117.1071040970.squirrel@imap01.ch.sauter-bc.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Wed, 2003-12-10 at 01:22, Simon Matter wrote: > > xfs_vnodeops.c > > Return address = 0x01ef8ba > > File system sd (8,8): I/O error detected. > ^^^^^^^^^ > I'm not an expert for those error messages but I guess it unfortunately a > hardware error, isn't it? Did you check dmesg output when this happened? I'm always happy to blame hardware, believe me. :) But error 22 is "EINVAL" on x86, so I suppose it's possible that xfs did something wrong like request a block off the end of the device, and the driver said "no, I can't do that - EINVAL," which xfs interpreted as an I/O error... -Eric -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc. 651-683-3102 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Repair XFS, Norman Zhang |
|---|---|
| Next by Date: | Re: [Bug 209] Kernel 2.4.20-xfs memory leaks, Eric Sandeen |
| Previous by Thread: | Re: XFS filesystem shutdown, Mike Brodbelt |
| Next by Thread: | [Bug 209] Kernel 2.4.20-xfs memory leaks, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |