| To: | gbakos@xxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: XFS internal error xfs_da_do_buf(2) |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Wed, 30 Nov 2005 09:33:02 -0600 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.SOL.4.58.0511291220440.4474@titan.cfa.harvard.edu> |
| References: | <Pine.SOL.4.58.0511291220440.4474@titan.cfa.harvard.edu> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) |
Gaspar Bakos wrote:
This is an old system, RH9.0 with 2.4.22 kernel, running XFS from 2003-10-10.
( I was not able to update this system since the installation due to realtime-linux patches and various special kernel drivers we use for robotic control. In any case, it has been working fine for two years...) You could run S.M.A.R.T. to see if the drive is dying, and of course look in your logs for any IO errors. Run memchk etc if you think the memory might be suspect. It could be an xfs bug too. hard to say. Basically this error means that xfs read something which it did not expect to find (think bad magic number). I'd first try an xfs_repair. You should probably get a repair binary that is less than 2 years old :) -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: RHEL4 2.6.9-22EL xfs module src.rpm for testing, Eric Sandeen |
|---|---|
| Next by Date: | fixing SELINUX-support in XFS-2.6.14, Sami Farin |
| Previous by Thread: | XFS internal error xfs_da_do_buf(2), Gaspar Bakos |
| Next by Thread: | TAKE 946205 - make some xlog helpers real functions instead of macros, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |