Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Corrupt\s+XFS\s+\-Filesystems\s+on\s+new\s+Hardware\s+and\s+Kernel\s*$/: 22 ]

Total 22 documents matching your query.

1. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Wed, 11 Apr 2007 09:36:52 +0200
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
/archives/xfs/2007-04/msg00053.html (8,383 bytes)

2. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Wed, 11 Apr 2007 09:36:52 +0200
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
/archives/xfs/2007-04/msg00258.html (8,383 bytes)

3. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 28 Mar 2007 22:31:41 +1100
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
/archives/xfs/2007-03/msg00191.html (9,818 bytes)

4. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Wed, 28 Mar 2007 14:42:00 +0200
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
/archives/xfs/2007-03/msg00192.html (13,607 bytes)

5. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 28 Mar 2007 09:56:27 -0500
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
/archives/xfs/2007-03/msg00193.html (11,077 bytes)

6. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Wed, 28 Mar 2007 21:56:07 +0200
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
/archives/xfs/2007-03/msg00194.html (14,723 bytes)

7. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Thu, 29 Mar 2007 10:46:48 +1100
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
/archives/xfs/2007-03/msg00195.html (14,299 bytes)

8. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Linda Walsh <lkml@xxxxxxxxx>
Date: Wed, 28 Mar 2007 17:21:32 -0700
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.
/archives/xfs/2007-03/msg00196.html (11,813 bytes)

9. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Linda Walsh <lkml@xxxxxxxxx>
Date: Wed, 28 Mar 2007 19:34:38 -0700
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
/archives/xfs/2007-03/msg00197.html (11,189 bytes)

10. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Jan Kara <jack@xxxxxxx>
Date: Thu, 29 Mar 2007 11:34:00 +0200
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
/archives/xfs/2007-03/msg00198.html (10,846 bytes)

11. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Jens Axboe <jens.axboe@xxxxxxxxxx>
Date: Thu, 29 Mar 2007 13:14:07 +0200
A barrier write guarentees both data before barrier is on disk, as well as the barrier itself when completion is signalled. -- Jens Axboe
/archives/xfs/2007-03/msg00200.html (11,139 bytes)

12. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Fri, 30 Mar 2007 15:45:00 +0200
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
/archives/xfs/2007-03/msg00229.html (16,597 bytes)

13. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Wed, 28 Mar 2007 22:31:41 +1100
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
/archives/xfs/2007-03/msg00421.html (9,818 bytes)

14. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Wed, 28 Mar 2007 14:42:00 +0200
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
/archives/xfs/2007-03/msg00422.html (13,607 bytes)

15. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Wed, 28 Mar 2007 09:56:27 -0500
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
/archives/xfs/2007-03/msg00423.html (11,077 bytes)

16. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Oliver Joa <oliver@xxxxxxxx>
Date: Wed, 28 Mar 2007 21:56:07 +0200
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
/archives/xfs/2007-03/msg00424.html (14,723 bytes)

17. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: David Chinner <dgc@xxxxxxx>
Date: Thu, 29 Mar 2007 10:46:48 +1100
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
/archives/xfs/2007-03/msg00425.html (14,299 bytes)

18. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Linda Walsh <lkml@xxxxxxxxx>
Date: Wed, 28 Mar 2007 17:21:32 -0700
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.
/archives/xfs/2007-03/msg00426.html (11,813 bytes)

19. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Linda Walsh <lkml@xxxxxxxxx>
Date: Wed, 28 Mar 2007 19:34:38 -0700
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
/archives/xfs/2007-03/msg00427.html (11,189 bytes)

20. Re: Corrupt XFS -Filesystems on new Hardware and Kernel (score: 1)
Author: Jan Kara <jack@xxxxxxx>
Date: Thu, 29 Mar 2007 11:34:00 +0200
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
/archives/xfs/2007-03/msg00428.html (10,846 bytes)


This search system is powered by Namazu