On Sat, Aug 13, 2005 at 08:11:52PM -0700, [EMAIL PROTECTED] wrote:
Quoting Sam Leffler [EMAIL PROTECTED]:
The ipw and iwi drivers (at least) have never worked right so far as
I can tell. At one point I tried the iwi driver and it kinda worked
but failed in many common scenarios and in
From: Brandon Fosdick [mailto:[EMAIL PROTECTED]
Darren Pilgrim wrote:
Try switching slots with the RAID and video cards. It's silly, but
then so is PCI interrupt routing.
Unbelievable. Who ever wrote the PCI spec should have been shot.
I believe the IEEE was involved. :)
I switched
Thanks for all replies and suggestions. sounds like I can give 6 a try.
I can move the hd to a bigger machine for installing and compiling.
Chris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
Now that my shiny new 9500S is installed and not fighting for IRQs, I've created and initialized a ~2.5TB array using the bios utility. So the next step is mounting the new array.
I naively tried following the regular handbook instructions for adding a new drive and failed miserably. And after
Hi,
I have a 4.11 machine that keeps getting file-system corruption on a
single ATA drive (on a ServerWorks ROSB4, not the 3ware mentioned in
the dmesg bewlow). In the nightly run e-mails I see pages and pages of:
Checking setuid files and devices:
find: /usr/share/locale/fr_CA.ISO8859-15:
On 15/08/2005, at 10:04 AM, David Wolfskill wrote:
On Mon, Aug 15, 2005 at 09:55:07AM +1200, Philip Murray wrote:
Hi,
I have a 4.11 machine that keeps getting file-system corruption on a
single ATA drive ...
Every time I see this, I run a fsck over the file-system in single
user mode
The Serverworks ROSB4 is known broken - I get instant file corruption on
mine if I try to run it at udma33.
Try
$ atacontrol mode 0 PIO4 PIO4
(I have not tried this - I just use a Promise PDC2071 for all the disks
instead...)
Cheers
Mark
Philip Murray wrote:
Hi,
I have a 4.11 machine
Quoting Brandon Fosdick [EMAIL PROTECTED]:
Now that my shiny new 9500S is installed and not fighting for IRQs,
I've created and initialized a ~2.5TB array using the bios utility.
So the next step is mounting the new array. I naively tried following
the regular handbook instructions for adding
Where exactly did you run into trouble?
I'm guessing you made the array, you have a device for it in /dev but
ran into problems (expected) using fdisk or bsdlabel.
-Jon
On Sun, 14 Aug 2005, Brandon Fosdick wrote:
Now that my shiny new 9500S is installed and not fighting for IRQs, I've
Jon Dama wrote:
Where exactly did you run into trouble?
I'm guessing you made the array, you have a device for it in /dev but
ran into problems (expected) using fdisk or bsdlabel.
Yup, that's exactly what happened. I ended up with a 0.5TB partition. At least,
thats what df said.
A few
Erik Stian Tefre wrote:
You can avoid the problem by splitting the array up in partitions
smaller than
2TB each. (I know this does not answer your question, but it simplifies
things,
and it works for me(TM)... :-)
:) Thanks, but I thought of that already. This is going to be a big database
Darren Pilgrim wrote:
I believe the IEEE was involved. :)
That explains a lot :)
IRQ sharing is a known issue with many RAID cards and even some gigabit
ethernet cards. It seems to correlate to cards that push the
performance limit of the bus.
And here I am with both a RAID card and a
12 matches
Mail list logo
