Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Segfault\s+of\s+xfs_repair\s+during\s+repair\s+of\s+a\s+xfs\s+filesystem\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Segfault\s+of\s+xfs_repair\s+during\s+repair\s+of\s+a\s+xfs\s+filesystem\s*$/: 51 ]

Total 51 documents matching your query.

21. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Arthur Corliss <corliss@xxxxxxxxxxxxxxxx>; Date: Mon, 5 Jan 2004 06:35:59 -0900 (AKST); iou; /archives/xfs/2004-01/msg00427.html (10,195 bytes)
22. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer krienke <rainer@xxxxxxxxxxx>; Date: Mon, 5 Jan 2004 20:22:44 +0100; for; /archives/xfs/2004-01/msg00436.html (10,570 bytes)
23. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Glen Overby <overby@xxxxxxx>; Date: Mon, 5 Jan 2004 23:36:43 -0600 (CST); tio; /archives/xfs/2004-01/msg00453.html (10,665 bytes)
24. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer Krienke <krienke@xxxxxxxxxxxxxx>; Date: Tue, 6 Jan 2004 09:05:41 +0100; fo; /archives/xfs/2004-01/msg00454.html (16,283 bytes)
25. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Tue, 6 Jan 2004 08:40:56 -0600 (CST); mon; /archives/xfs/2004-01/msg00456.html (11,864 bytes)
26. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Tue, 6 Jan 2004 08:46:12 -0600 (CST); ar/; /archives/xfs/2004-01/msg00457.html (9,769 bytes)
27. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer Krienke <krienke@xxxxxxxxxxxxxx>; Date: Tue, 6 Jan 2004 16:24:31 +0100; s a; /archives/xfs/2004-01/msg00458.html (13,580 bytes)
28. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer Krienke <krienke@xxxxxxxxxxxxxx>; Date: Tue, 6 Jan 2004 09:49:48 +0100; 965; /archives/xfs/2004-01/msg00461.html (14,065 bytes)
29. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer Krienke <krienke@xxxxxxxxxxxxxx>; Date: Wed, 7 Jan 2004 11:35:12 +0100; m d; /archives/xfs/2004-01/msg00469.html (11,856 bytes)
30. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx>; Date: Wed, 07 Jan 2004 09:58:34 -0500; m d; /archives/xfs/2004-01/msg00471.html (10,885 bytes)
31. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx>; Date: Wed, 07 Jan 2004 10:15:20 -0500; cy; /archives/xfs/2004-01/msg00472.html (11,351 bytes)
32. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Arthur Corliss <corliss@xxxxxxxxxxxxxxxx>; Date: Wed, 7 Jan 2004 06:42:38 -0900 (AKST); fs_; /archives/xfs/2004-01/msg00475.html (11,144 bytes)
33. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer Krienke <rainer@xxxxxxxxxxx>; Date: Sat, 10 Jan 2004 09:51:45 +0100; its; /archives/xfs/2004-01/msg00509.html (11,830 bytes)
34. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx>; Date: Mon, 12 Jan 2004 10:08:17 -0500; is; /archives/xfs/2004-01/msg00528.html (12,344 bytes)
35. Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer Krienke <krienke@xxxxxxxxxxxxxx>; Date: Mon, 5 Jan 2004 08:49:59 +0100; Hello, a happy new year to everyone on this list ... well for some of my xfs filesystems the year had a bad start. Due to a powerfail on some systems that possibly rebootet and later again crashed du; /archives/xfs/2004-01/msg00789.html (11,478 bytes)
36. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Eric Sandeen <sandeen@xxxxxxx>; Date: Mon, 5 Jan 2004 09:13:08 -0600 (CST); What was the failure when you first tried to mount? Unable to find a superblock immediately after repair? I have never seen this before, sounds very odd. BTW running repair twice in sucession will ke; /archives/xfs/2004-01/msg00790.html (13,168 bytes)
37. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx>; Date: Mon, 05 Jan 2004 10:17:27 -0500; Do you have write-caching disabled in your drives/raid controller. IIRC, XFS requires that it be disabled to ensure the transaction log works as advertised. This definately impacts speed, but ... Gre; /archives/xfs/2004-01/msg00791.html (9,785 bytes)
38. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Arthur Corliss <corliss@xxxxxxxxxxxxxxxx>; Date: Mon, 5 Jan 2004 06:35:59 -0900 (AKST); Some of the higher-end cards have battery backup for fast-write cache. You shouldn't have to disable it for those units. --Arthur Corliss Bolverk's Lair -- http://arthur.corlissfamily.org/ Digital Ma; /archives/xfs/2004-01/msg00793.html (10,323 bytes)
39. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Rainer krienke <rainer@xxxxxxxxxxx>; Date: Mon, 5 Jan 2004 20:22:44 +0100; Am Montag, 5. Januar 2004 16:35 schrieben Sie: The basis for storage are IFT 7250 Raids with IDE disks inside (external its running fibrechannel). The device is configures as raid level 5. I looked i; /archives/xfs/2004-01/msg00802.html (10,716 bytes)
40. Re: Segfault of xfs_repair during repair of a xfs filesystem (score: 1): Author: Glen Overby <overby@xxxxxxx>; Date: Mon, 5 Jan 2004 23:36:43 -0600 (CST); If this still happens, It might be useful to see how much was overwritten, and if you recognise the data. You can use xfs_db to read and print the superblock. xfs_db -r /dev/diskxyz sb 0 print - a fo; /archives/xfs/2004-01/msg00819.html (10,747 bytes)

Current List: 21 - 40
Page: [1] [2] [3]