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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+corruption\s+on\s+SoftRAID5\s*$/: 38 ]

Total 38 documents matching your query.

1. XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Thu, 28 Jun 2001 19:32:53 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B9D0457306 for <linux-xfs@oss.sgi.com>; Thu, 28 Jun 2001 19:37:12 +0200 (CEST) Organization: Sauter AG; /archives/xfs/2001-06/msg01091.html (9,719 bytes)
2. Re: XFS corruption on SoftRAID5 (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Thu, 28 Jun 2001 16:48:41 -0500; First rule of bug reporting, which version of the kernel are you using? Oh, and what type of NFS servers? Details, details please. Steve; /archives/xfs/2001-06/msg01101.html (10,561 bytes)
3. Re: XFS corruption on SoftRAID5 (score: 1): Author: "Bryan J. Smith" <b.j.smith@xxxxxxxx>; Date: Thu, 28 Jun 2001 19:45:16 -0400; Ouch! Talk about a performance bottleneck (using ATA drives as "slaves"). And I don't want to even get started with the Promise cards and drivers themselves. Er, by this time, you could have spend a; /archives/xfs/2001-06/msg01109.html (10,084 bytes)
4. Re: XFS corruption on SoftRAID5 (score: 1): Author: Andrew Klaassen <ak@xxxxxxx>; Date: Thu, 28 Jun 2001 19:46:27 -0400; Hmm. I hope not - we've just deployed 300G of IDE drive (using an onboard controller, no less) on a box running 2.4.2-SGI_XFS_1.0.1_PR1 over software RAID 5, and plan to deploy 300G more once we've h; /archives/xfs/2001-06/msg01111.html (9,164 bytes)
5. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 08:59:36 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 7F47C57306; Fri, 29 Jun 2001 09:03:57 +0200 (CEST) Cc: linux-xfs <linux-xfs@xxxxxxxxxxx> Organization:; /archives/xfs/2001-06/msg01122.html (11,680 bytes)
6. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 09:09:44 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id E767557306; Fri, 29 Jun 2001 09:14:04 +0200 (CEST) Cc: linux-xfs <linux-xfs@xxxxxxxxxxx> Organization:; /archives/xfs/2001-06/msg01123.html (11,393 bytes)
7. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 09:25:52 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id C24B357306; Fri, 29 Jun 2001 09:30:12 +0200 (CEST) Cc: linux-xfs <linux-xfs@xxxxxxxxxxx> Organization:; /archives/xfs/2001-06/msg01124.html (9,873 bytes)
8. Re: XFS corruption on SoftRAID5 (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Fri, 29 Jun 2001 09:27:12 +0200; I said PR1-PR3. I thought it's just the naming for the RH Kernels 1.0.1 release. Okay, they are linux servers. kernel 2.2.16 and 2.0.36!. Just believe me, they are not the problem. Sorry Now, don't w; /archives/xfs/2001-06/msg01125.html (10,866 bytes)
9. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 10:29:10 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 3462F57306; Fri, 29 Jun 2001 10:33:31 +0200 (CEST) Cc: Steve Lord <lord@xxxxxxx>, linux-xfs <linux-xfs; /archives/xfs/2001-06/msg01126.html (12,074 bytes)
10. Re: XFS corruption on SoftRAID5 (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Fri, 29 Jun 2001 11:01:44 +0200; Until today, it seemed to be XFS related. Oh. I thought you noticed it earlier. kernel bugs. You're right. But on this list we have all those people using big disks and raid volumes. So if the proble; /archives/xfs/2001-06/msg01127.html (12,264 bytes)
11. Re: XFS corruption on SoftRAID5 (score: 1): Author: "Orn E. Hansen" <oe.hansen@xxxxxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 14:21:56 +0200; föstudagur 29. júní 2001 09:27, Seth Mos skrifađi: Garbled characters, and corrupted filesystem... but no ide reported errors? Sounds like what I got once, when I put a filesystem on a drive that was; /archives/xfs/2001-06/msg01128.html (9,713 bytes)
12. Re: XFS corruption on SoftRAID5 (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 29 Jun 2001 12:28:06 -0400; It is perfectly fine to ask questions like that here. FWIW, almost all the XFS corruption bugs (with RAID or otherwise) I've seen so far have been incorrect IDE hdparm tuning or bad cabling. -- Mart; /archives/xfs/2001-06/msg01129.html (10,017 bytes)
13. Re: XFS corruption on SoftRAID5 (score: 1): Author: Andrew Klaassen <ak@xxxxxxx>; Date: Fri, 29 Jun 2001 13:06:41 -0400; My question is really OT for this list, but how might one go about checking for bad cabling? Is there any software that can find it consistently? Andrew Klaassen; /archives/xfs/2001-06/msg01130.html (9,665 bytes)
14. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 18:48:10 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B794857306; Fri, 29 Jun 2001 18:56:51 +0200 (CEST) Cc: Steve Lord <lord@xxxxxxx>, linux-xfs <linux-xfs; /archives/xfs/2001-06/msg01139.html (13,412 bytes)
15. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 18:54:27 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 1E0CA57306; Fri, 29 Jun 2001 19:03:08 +0200 (CEST) Cc: Seth Mos <knuffie@xxxxxxxxx>, Steve Lord <lord@; /archives/xfs/2001-06/msg01140.html (10,193 bytes)
16. Re: XFS corruption on SoftRAID5 (score: 1): Author: Seth Mos <knuffie@xxxxxxxxx>; Date: Fri, 29 Jun 2001 22:29:56 +0200 (CEST); If the cable is not correct some cards will report it. The promise controllers can report if a IDE cable is 80 pins or not. And the kernel sometimes also gives back errors. I have seen it once alread; /archives/xfs/2001-06/msg01142.html (9,694 bytes)
17. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <Simon.Matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 21:52:17 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 9724457306; Fri, 29 Jun 2001 22:02:45 +0200 (CEST) Cc: linux-xfs <linux-xfs@xxxxxxxxxxx> References: <; /archives/xfs/2001-06/msg01145.html (10,043 bytes)
18. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 19:02:24 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id D02D857306; Fri, 29 Jun 2001 19:11:05 +0200 (CEST) Cc: linux-xfs <linux-xfs@xxxxxxxxxxx> Organization:; /archives/xfs/2001-06/msg01146.html (10,801 bytes)
19. Re: XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <Simon.Matter@xxxxxxxxxxxxxxxx>; Date: Fri, 29 Jun 2001 22:53:29 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 9F04157306; Fri, 29 Jun 2001 23:03:58 +0200 (CEST) Cc: Andrew Klaassen <ak@xxxxxxx>, linux-xfs <linux-; /archives/xfs/2001-06/msg01148.html (10,642 bytes)
20. XFS corruption on SoftRAID5 (score: 1): Author: Simon Matter <simon.matter@xxxxxxxxxxxxxxxx>; Date: Thu, 28 Jun 2001 19:32:53 +0200; from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B9D0457306 for <linux-xfs@oss.sgi.com>; Thu, 28 Jun 2001 19:37:12 +0200 (CEST) Organization: Sauter AG; /archives/xfs/2001-06/msg02261.html (9,719 bytes)

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