Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_repair\s+crashing\s+$versions\s+3\.1\.4\s+and\s+3\.1\.5$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*xfs_repair\s+crashing\s+$versions\s+3\.1\.4\s+and\s+3\.1\.5$\s*$/: 8 ]

Total 8 documents matching your query.

1. xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Anisse Astier <anisse@xxxxxxxxx>; Date: Mon, 18 Apr 2011 21:24:22 +0200; Hi, (first of all, I'm not subscribed to the list, Please cc-me on all replies) On an ARM NAS, using kernel 2.6.36.2 I managed to crash my root xfs partition. xfs_repair cannot then repair this parti; /archives/xfs/2011-04/msg00223.html (89,091 bytes)
2. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 19 Apr 2011 18:27:05 +1000; Something has corrupted the log.... Yup. Quite likely, zeroing the log effectively corrupts the filesystem. ..... Hmmm. The very next line doesn't appear before the segfault, making me think that it'; /archives/xfs/2011-04/msg00234.html (11,462 bytes)
3. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Anisse Astier <anisse@xxxxxxxxx>; Date: Tue, 19 Apr 2011 13:07:37 +0200; I have no idea. I did not succeed in getting a stacktrace. CPU is an ARM9, and I used Debian armel squeeze & wheezy xfsprogs binaries. Regards, Anisse; /archives/xfs/2011-04/msg00235.html (8,802 bytes)
4. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Thu, 21 Apr 2011 14:26:06 -0500; Perhaps you could try removing or fixing the printf Dave suspects, rebuild repair, and run it again? -Eric; /archives/xfs/2011-04/msg00302.html (10,162 bytes)
5. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Anisse Astier <anisse@xxxxxxxxx>; Date: Fri, 22 Apr 2011 13:09:20 +0200; Yep, I figured that much, it just took me a while to get up & running another system capable of building xfsprogs. Now that I have that, and that I commented the do_warn, xfs_repair is still running; /archives/xfs/2011-04/msg00324.html (11,165 bytes)
6. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 4 May 2011 05:11:41 -0400; Any updates? In the meantime I cooked up a little patch (below) to add format string checking to the repair-internal varargs printing helpers, which produces a lot of warnings. A lot of that is diffe; /archives/xfs/2011-05/msg00077.html (10,327 bytes)
7. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Anisse Astier <anisse@xxxxxxxxx>; Date: Wed, 4 May 2011 12:24:03 +0200; Well, Dave had it all figured, and replacing %u by %llu fixes indeed the problem. Just for future reference, the stack of crashing process: format=0xbe9a7676 "27", ap=<value optimized out>) at vfprin; /archives/xfs/2011-05/msg00078.html (13,517 bytes)
8. Re: xfs_repair crashing (versions 3.1.4 and 3.1.5) (score: 1): Author: Anisse Astier <anisse@xxxxxxxxx>; Date: Fri, 6 May 2011 00:46:44 +0200; Before: Building repair [DEP] [CC] agheader.o [CC] attr_repair.o [CC] avl.o [CC] avl64.o [CC] bmap.o [CC] btree.o [CC] dino_chunks.o [CC] dinode.o [CC] dir.o [CC] dir2.o [CC] globals.o [CC] incore.o; /archives/xfs/2011-05/msg00105.html (18,764 bytes)

Current List: 1 - 8
Page: [1]