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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Linux\s+XFS\s+filesystem\s+corruption\s+$XFS_WANT_CORRUPTED_GOTO$\s*$/: 27 ]

Total 27 documents matching your query.

1. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 3 Mar 2008 17:29:27 -0800 (PST); I ran xfs_metadump (with -g -o -w options) on the partition and in addition to the file output this was written to stder: xfs_metadump: suspicious count 22 in bmap extent 9 in dir2 ino 940064492 xfs; /archives/xfs/2008-03/msg00034.html (12,252 bytes)
2. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 3 Mar 2008 17:43:03 -0800 (PST); Unfortunately, mounting triggered another XFS_WANT_CORRUPTED_GOTO error: XFS mounting filesystem sda1 Starting XFS recovery on filesystem: sda1 (logdev: internal) XFS internal error XFS_WANT_CORRUPTE; /archives/xfs/2008-03/msg00035.html (16,562 bytes)
3. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: "Barry Naujok" <bnaujok@xxxxxxx>; Date: Tue, 04 Mar 2008 12:36:57 +1100; I ran xfs_metadump (with -g -o -w options) on the partition and in addition to the file output this was written to stder: xfs_metadump: suspicious count 22 in bmap extent 9 in dir2 ino 940064492 xfs_; /archives/xfs/2008-03/msg00036.html (13,422 bytes)
4. tition (score: 1): Author: f@xxxxxxx>; Date: Mon, 3 Mar 2008 17:29:27 -0800 (PST); not making /dev/sde1? Have you tried a manual mknod of the device? On Mon, 3 Mar 2008, Jeff Breidenbach wrote: I have no special reason to believe this is xf; /archives/xfs/2008-03/msg00423.html (12,252 bytes)
5. corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: xxxxxxxxx>; Date: Mon, 3 Mar 2008 17:43:03 -0800 (PST); o check /proc/partitions for sde1...) -Eric; /archives/xfs/2008-03/msg00424.html (16,562 bytes)
6. corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: xxxxxxxxx>; Date: Tue, 04 Mar 2008 12:36:57 +1100; and in addition to the file output this was written to stder: xfs_metadump: suspicious count 22 in bmap extent 9 in dir2 ino 940064492 xfs; /archives/xfs/2008-03/msg00425.html (13,422 bytes)
7. Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 25 Feb 2008 14:20:52 -0800 (PST); A RAID5 (3ware card w/ 8 drive cage) filesystem on our cluster login node shut down the other night with this error: kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file fs/xfs/xfs; /archives/xfs/2008-02/msg00353.html (9,359 bytes)
8. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Mon, 25 Feb 2008 14:40:17 -0800; ksymoops might be good so we can see what the actual backtrace was. Are you hitting http://oss.sgi.com/projects/xfs/faq.html#dir2 ? -Eric; /archives/xfs/2008-02/msg00354.html (10,022 bytes)
9. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 25 Feb 2008 23:54:57 -0800 (PST); Thanks for the reply. Presumably not - i'm using 2.6.17.11, and that information indicates the bug was fixed in 2.6.17.7. I've attached the output from running ksymoops on messages.1. First crash/tra; /archives/xfs/2008-02/msg00372.html (9,174 bytes)
10. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Wed, 27 Feb 2008 14:44:04 -0800 (PST); I'm still hoping for some help with this. Is any more information needed in addition to the ksymoops output previously posted? In particular i'd like to know if just remounting the filesystem (to re; /archives/xfs/2008-02/msg00378.html (9,946 bytes)
11. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: "Barry Naujok" <bnaujok@xxxxxxx>; Date: Thu, 28 Feb 2008 14:16:33 +1100; I'm still hoping for some help with this. Is any more information needed in addition to the ksymoops output previously posted? In particular i'd like to know if just remounting the filesystem (to rep; /archives/xfs/2008-02/msg00383.html (11,937 bytes)
12. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Fri, 29 Feb 2008 20:09:15 -0800 (PST); Thanks Barry. Couple of follow-up questions: For "making an entire of the device", i presume you mean using dd, since it's an unmounted filesystem? Also, I noted that my system's older xfsprogs 2.6.1; /archives/xfs/2008-02/msg00415.html (12,645 bytes)
13. Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 25 Feb 2008 14:20:52 -0800 (PST); A RAID5 (3ware card w/ 8 drive cage) filesystem on our cluster login node shut down the other night with this error: kernel: XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1563 of file fs/xfs/xfs; /archives/xfs/2008-02/msg00769.html (9,359 bytes)
14. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Mon, 25 Feb 2008 14:40:17 -0800; ksymoops might be good so we can see what the actual backtrace was. Are you hitting http://oss.sgi.com/projects/xfs/faq.html#dir2 ? -Eric; /archives/xfs/2008-02/msg00770.html (10,022 bytes)
15. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 25 Feb 2008 23:54:57 -0800 (PST); Thanks for the reply. Presumably not - i'm using 2.6.17.11, and that information indicates the bug was fixed in 2.6.17.7. I've attached the output from running ksymoops on messages.1. First crash/tra; /archives/xfs/2008-02/msg00788.html (9,174 bytes)
16. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Wed, 27 Feb 2008 14:44:04 -0800 (PST); I'm still hoping for some help with this. Is any more information needed in addition to the ksymoops output previously posted? In particular i'd like to know if just remounting the filesystem (to re; /archives/xfs/2008-02/msg00794.html (9,946 bytes)
17. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: "Barry Naujok" <bnaujok@xxxxxxx>; Date: Thu, 28 Feb 2008 14:16:33 +1100; I'm still hoping for some help with this. Is any more information needed in addition to the ksymoops output previously posted? In particular i'd like to know if just remounting the filesystem (to rep; /archives/xfs/2008-02/msg00799.html (11,937 bytes)
18. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Fri, 29 Feb 2008 20:09:15 -0800 (PST); Thanks Barry. Couple of follow-up questions: For "making an entire of the device", i presume you mean using dd, since it's an unmounted filesystem? Also, I noted that my system's older xfsprogs 2.6.1; /archives/xfs/2008-02/msg00831.html (12,645 bytes)
19. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 3 Mar 2008 17:29:27 -0800 (PST); Barry, I ran xfs_metadump (with -g -o -w options) on the partition and in addition to the file output this was written to stder: xfs_metadump: suspicious count 22 in bmap extent 9 in dir2 ino 9400644; /archives/xfs/2008-03/msg00812.html (12,675 bytes)
20. Re: Linux XFS filesystem corruption (XFS_WANT_CORRUPTED_GOTO) (score: 1): Author: slaton <slaton@xxxxxxxxxxxx>; Date: Mon, 3 Mar 2008 17:43:03 -0800 (PST); Unfortunately, mounting triggered another XFS_WANT_CORRUPTED_GOTO error: XFS mounting filesystem sda1 Starting XFS recovery on filesystem: sda1 (logdev: internal) XFS internal error XFS_WANT_CORRUPTE; /archives/xfs/2008-03/msg00813.html (17,037 bytes)

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