David Chinner wrote: On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote: Hi, since some weeks i try to get my new hardware running: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz Intel DP965LT Mainbo
David Chinner wrote: On Tue, Mar 27, 2007 at 06:16:04PM +0200, Oliver Joa wrote: Hi, since some weeks i try to get my new hardware running: Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz Intel DP965LT Mainbo
What is the corruption message in the log from XFS? Can you please post that? Without it we really can't help you. That's really only an issue for crashes, not runtime failures. I/O errors. That's wh
David Chinner wrote: [...] What is the corruption message in the log from XFS? Can you please post that? Without it we really can't help you. Also, please check to see if there are any I/O errors in
Oliver Joa wrote: Ok, here is a test: test:/# find / -xdev | cpio -padm /test/ cpio: /usr/src/linux-2.6.20.2/Documentation/networking/NAPI_HOWTO.txt: Structure needs cleaning 3648371 blocks test:/# T
Eric Sandeen wrote: [...] For one reason or another, xfs has detected a corrupted on-disk inode format which it cannot recognize, and shuts down. It is likely the result of something which has gone
So we have a corrupt inode. The error tells me that the corrupted inode is either a regular file, directory or link. Unfortunately it doesn't tell us the inode number that is corrupted. Once the file
Oliver Joa wrote: eason or another, xfs has detected a corrupted on-disk inode format which it cannot recognize, and shuts down. It is likely the result of something which has gone wrong previously.
Oliver Joa wrote: eason or another, xfs has detected a corrupted on-disk inode format which it cannot recognize, and shuts down. -- Oh, one other thing that may not apply in your case, but may. Does
As far as I can remember, barrier does not mean that data is fixed on disk. It is only a command that forces all the writes before the barrier to be performed before all the writes after the barrier
David Chinner wrote: [...] Next time you get a shutdown, can you unmount the filesystems and run xfs_check and then "xfs_repair -n" on the filesystem. These will tell you the inode numbers that are
What is the corruption message in the log from XFS? Can you please post that? Without it we really can't help you. That's really only an issue for crashes, not runtime failures. I/O errors. That's wh
David Chinner wrote: [...] What is the corruption message in the log from XFS? Can you please post that? Without it we really can't help you. Also, please check to see if there are any I/O errors in
Oliver Joa wrote: Ok, here is a test: test:/# find / -xdev | cpio -padm /test/ cpio: /usr/src/linux-2.6.20.2/Documentation/networking/NAPI_HOWTO.txt: Structure needs cleaning 3648371 blocks test:/# T
Eric Sandeen wrote: [...] For one reason or another, xfs has detected a corrupted on-disk inode format which it cannot recognize, and shuts down. It is likely the result of something which has gone
So we have a corrupt inode. The error tells me that the corrupted inode is either a regular file, directory or link. Unfortunately it doesn't tell us the inode number that is corrupted. Once the file
Oliver Joa wrote: eason or another, xfs has detected a corrupted on-disk inode format which it cannot recognize, and shuts down. It is likely the result of something which has gone wrong previously.
Oliver Joa wrote: eason or another, xfs has detected a corrupted on-disk inode format which it cannot recognize, and shuts down. -- Oh, one other thing that may not apply in your case, but may. Does
As far as I can remember, barrier does not mean that data is fixed on disk. It is only a command that forces all the writes before the barrier to be performed before all the writes after the barrier