SCSI-UW(160) is out.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of D. Carlos
Knowlton
Sent: Wednesday, June 30, 1999 11:57 AM
To: Linux-Raid
Subject: U-DMA-66 IDE / RAID
Hey Guys,
I am building a server that I want to use Linux RAID on.
Greetings!
Since others are putting in their two cents worth, here is mine...
"Jonathan F. Dill" wrote:
Hi folks,
I was just searching through the archives for help on a RAID problem and
the posts were helpful, so I decided to "give something back" to the
group.
Chris R. Brown
Knock over a bank to buy SCSI?!? A year ago I bought a brand new 5x2GB
U2 SCSI array in a tower enclosure with a Symbios Logic U2 controller
card (drives are all HP) for $350 on onsale.com. At the time, a 10GB
UDMA drive cost almost the same...
--
Jeremy StanleyTrend CMHS
On Thu, Jul 01, 1999 at 09:50:15AM -0400, Stanley, Jeremy wrote:
Knock over a bank to buy SCSI?!? A year ago I bought a brand new 5x2GB
U2 SCSI array in a tower enclosure with a Symbios Logic U2 controller
card (drives are all HP) for $350 on onsale.com. At the time, a 10GB
UDMA drive cost
Aha. I thought that 400 sounded a bit too good to be true... C'est la
vie.
--
Jeremy StanleyTrend CMHS
I.S.Network Engineer http://www.trendcmhs.org
The opinions expressed herein do not necessarily
represent those of Trend CMHS or Trend Foundation.
"I program my
Personally I dont mind waiting a little longer, if it means that the final
bugs will be ironed out and especially if it is marked as 'stable' and
goes into the kernel tree. I take it we're pretty close to that?
I still have a production box running a 2.1.114 kernel, and the raid5
patches at that
Tom Livingston wrote:
I should have mentioned that I finally solved these problems by buying
custom length cables similar to what are required for udma-66. These cables
all have a ground line in between each data line... doubling the number of
wires in the cable and canceling out some of the
I'd also be happy to wait, but I think it would be nice to have a little
more info on the list about the current status... especially if it's
likley to be merged with 2.2 (Not so much 2.3) because I'd definitely wait
longer to have a merged version,..
Just to throw the cat among the pigeons
Following the lead from ([EMAIL PROTECTED]), I edited
/usr/src/linux/drivers/block/md.c, and changed the TWO occurrances of
"current-priority = 0" to "current-priority = 1", and resync started
working just fine. As a nice side effect, I can reboot the system cleanly
now (was hanging up
Currently the latest kernel that works with the patches is 2.2.7
On Thu, 1 Jul 1999, P Mancuso wrote:
Following the lead from ([EMAIL PROTECTED]), I edited
/usr/src/linux/drivers/block/md.c, and changed the TWO occurrances of
"current-priority = 0" to "current-priority = 1", and resync
Date: Thu, 1 Jul 1999 16:46:48 +0100 (BST)
Currently the latest kernel that works with the patches is 2.2.7
I know that. What I'm saying is that if you apply those patches, AND you
manually change those two lines I mentioned in md.c, it works on 2.2.9 also.
At least it looks like it's
There were changes made in 2.2.8 which cause sync to run forever as you
are discribing There have been several comments to this list with
hacked solutions bust most were rather brutal, like "remove all the sync
bandwidth control code"
I'd wait for the next release!
On Thu, 1 Jul 1999,
Mark,
Having a very large chunk size would reduce the performance down close to that
of a single device. Two performance factors to keep in mind: access time, and
throughput. Access time is important for the many small files and accesses
needed, and throughput is needed for large requests. Mixed
Jonathan F. Dill wrote:
That's fantastic--Did you "roll your own" or special order them from
someplace? How much did they cost? I was also wondering about using
ribbon with twisted pairs (like some old DEC MicroVax used to use for
internal SCSI) but I would expect it to be expensive per
I have recently upgraded some boxes from RH5.2 to RH6.0 and have run into
some problems with getting my arrays to work.
The arrays were created under RH5.2 with raidtools-0.50beta10-2.
I cannot set "persistant-superblock" to 1, because then it would destroy
my data correct? So I leave it to 0.
I purchased two UDMA/66 cables from Fry's Electronics. There stores are
located throughout the west. They were different lengths and prices. The
average price was ~$20.
It's my understanding that these cables are needed for both UDMA/33 and
UDMA/66 drives to transfer at ratred speed as follows:
16 matches
Mail list logo
