Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+internal\s+error\s+XFS_WANT_CORRUPTED

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+internal\s+error\s+XFS_WANT_CORRUPTED_GOTO\s*$/: 32 ]

Total 32 documents matching your query.

1. blem (score: 1): Author: >; Date: Thu, 29 May 2008 15:48:38 +0200; anuel Florac | Intellique -; /archives/xfs/2008-05/msg00446.html (8,432 bytes)
2. routines (score: 1): Author: xx>; Date: Thu, 29 May 2008 15:48:38 +0200; arly what to do :) -- -- Emmanuel Florac | Intellique -; /archives/xfs/2008-05/msg00930.html (8,432 bytes)
3. XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>; Date: Thu, 19 Apr 2007 14:28:24 +0100; We've had a couple of occurrnces of xfs shutdowns on one of our fileservers. The latest had the message: Apr 19 10:35:00 fs3 kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1745 of file f; /archives/xfs/2007-04/msg00099.html (11,414 bytes)
4. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Fri, 20 Apr 2007 00:18:27 +1000; So you've got a corrupted freespace btree. What is the filesystem hosted on - a normal block device, iscsi, nbd? What kernel? Are there any I/O errors in the log? What we you running at the time of t; /archives/xfs/2007-04/msg00100.html (8,518 bytes)
5. RE: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>; Date: Thu, 19 Apr 2007 15:36:58 +0100; It's an Infortrend SATA RAID5 array, with a fibre channel connection to the server. The filesystem is build on an LVM volume. Kernel is 2.6.13-15-smp running on an x86_64 dual CPU Xeon server with hy; /archives/xfs/2007-04/msg00101.html (9,962 bytes)
6. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Fri, 20 Apr 2007 08:10:59 +1000; OK. That's a relatively old kernel. It's possible that what you are seeing has been fixed since that kernel was released. Not uncommon - we do that all the time ;) Ok, so that makes it kind of hard t; /archives/xfs/2007-04/msg00102.html (9,270 bytes)
7. XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>; Date: Thu, 19 Apr 2007 14:28:24 +0100; We've had a couple of occurrnces of xfs shutdowns on one of our fileservers. The latest had the message: Apr 19 10:35:00 fs3 kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1745 of file f; /archives/xfs/2007-04/msg00304.html (11,414 bytes)
8. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Fri, 20 Apr 2007 00:18:27 +1000; So you've got a corrupted freespace btree. What is the filesystem hosted on - a normal block device, iscsi, nbd? What kernel? Are there any I/O errors in the log? What we you running at the time of t; /archives/xfs/2007-04/msg00305.html (8,518 bytes)
9. RE: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: "Burbidge, Simon A" <s.burbidge@xxxxxxxxxxxxxx>; Date: Thu, 19 Apr 2007 15:36:58 +0100; It's an Infortrend SATA RAID5 array, with a fibre channel connection to the server. The filesystem is build on an LVM volume. Kernel is 2.6.13-15-smp running on an x86_64 dual CPU Xeon server with hy; /archives/xfs/2007-04/msg00306.html (9,962 bytes)
10. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Fri, 20 Apr 2007 08:10:59 +1000; OK. That's a relatively old kernel. It's possible that what you are seeing has been fixed since that kernel was released. Not uncommon - we do that all the time ;) Ok, so that makes it kind of hard t; /archives/xfs/2007-04/msg00307.html (9,270 bytes)
11. XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Paul Slootman <paul@xxxxxxxxxx>; Date: Mon, 14 Aug 2006 16:17:31 +0200; That showed the following message in phase 3 because of the xfs_db action: imap claims a free inode 261 is in use, correcting imap and clearing inode and then in phase 4: entry "lost+found.x" at bloc; /archives/xfs/2006-08/msg00107.html (23,158 bytes)
12. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Paul Slootman <paul@xxxxxxxxxx>; Date: Tue, 15 Aug 2006 13:54:42 +0200; [snip] After all that, again, tonight: Aug 15 01:11:57 boes kernel: Filesystem "md6": XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c. Caller 0xffffffff880577d3 Aug 15 01:; /archives/xfs/2006-08/msg00117.html (11,046 bytes)
13. XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author:; Date: Mon, 14 Aug 2006 16:17:31 +0200; That showed the following message in phase 3 because of the xfs_db action: imap claims a free inode 261 is in use, correcting imap and clearing inode and then in phase 4: entry "lost+found.x" at bloc; /archives/xfs/2006-08/msg00359.html (23,158 bytes)
14. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author:; Date: Tue, 15 Aug 2006 13:54:42 +0200; [snip] After all that, again, tonight: Aug 15 01:11:57 boes kernel: Filesystem "md6": XFS internal error xfs_trans_cancel at line 1150 of file fs/xfs/xfs_trans.c. Caller 0xffffffff880577d3 Aug 15 01:; /archives/xfs/2006-08/msg00369.html (11,046 bytes)
15. XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Louis-David Mitterrand <vindex+lists-xfs@xxxxxxxxxxx>; Date: Thu, 29 May 2008 15:48:38 +0200; Hi, I found this in a server's dmesg: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 4518 of file fs/xfs/xfs_bmap.c. Caller 0xffffffff803fc46b Pid: 28612, comm: rsync Not tainted 2.6.25.4-1-pyrrh; /archives/xfs/2008-05/msg01414.html (8,432 bytes)
16. XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Nitin Arora <nitin.arora.del@xxxxxxxxx>; Date: Wed, 24 Jun 2009 17:26:32 +0530; Hi, I am using linux kernel 2.6.18 with XFS support. I have formatted USB hard drive with XFS. When I try to copy (i.e. cp 1.avi 2.avi) a big file (size : 1.3 GB) from one location to another on the; /archives/xfs/2009-06/msg00296.html (9,244 bytes)
17. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Wed, 24 Jun 2009 14:40:52 +0200; If possible, can you simply try upgrading your ancient kernel to something newer? Actual is 2.6.30, with many many bugs fixed, not only in XFS. mfg zmi -- // Michael Monnerie, Ing.BSc -- http://it-ma; /archives/xfs/2009-06/msg00297.html (8,289 bytes)
18. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Nitin Arora <nitin.arora.del@xxxxxxxxx>; Date: Wed, 24 Jun 2009 18:48:27 +0530; Hi Michael, thanks for the reply. upgrading kernel on our hardware architecture requires quite a lot effort. So I am looking for some solution specific to XFS. If some patch can help in this regard t; /archives/xfs/2009-06/msg00298.html (10,484 bytes)
19. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Wed, 24 Jun 2009 08:23:42 -0500; http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=71a8c87fb300b601eacf7a86cc6c6322fe827bfd fixed a longstanding in-memory extent corruption, but that's my only guess at; /archives/xfs/2009-06/msg00299.html (9,943 bytes)
20. Re: XFS internal error XFS_WANT_CORRUPTED_GOTO (score: 1): Author: Nitin Arora <nitin.arora.del@xxxxxxxxx>; Date: Thu, 25 Jun 2009 15:36:23 +0530; Hi, I have tried the patch provided in that link but unfortunately it doesn't solve that problem. I have run xfs_repair on the corrupted partition and got the following output. Phase 1 - find and ver; /archives/xfs/2009-06/msg00308.html (15,034 bytes)

Current List: 1 - 20
Page: [1] [2]