RE: IRQ conflict between twa0 and skc0
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 the cards and now the network card is sharing an > interrupt with the video card, but neither seems to mind. > More importantly it isn't sharing with the raid card and they > all appear to be happy. 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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Memory requirements between releases
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 unsubscribe, send any mail to "[EMAIL PROTECTED]"
Create 2.5TB file system on 5.4S?
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 googling a bit I now know why, and realized that I knew why before, but I was being stupid. I've seen a few mentions of using gpt(8) and some vague references to using dedicated mode. But I haven't seen anything that says "this is the Right Way to do it". So...what's the proper way to make a large file system? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Reoccurring filesystem corruption
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: Bad file descriptor find: /usr/share/locale/fr_CH.ISO8859-1: Bad file descriptor find: /usr/share/locale/fr_FR.ISO8859-1: Bad file descriptor find: /usr/share/locale/fr_CH.ISO8859-15: Bad file descriptor Every time I see this, I run a fsck over the file-system in single user mode and fsck claims to have fixed all the corruption. Then, anywhere from a week to a month later, it starts happening again and gets worse and worse. Is this a sign of a dead disk, faulty ATA controller, or something wrong with FreeBSD? I get no error messages in dmesg. Is it possible fsck isn't actually fixing everything there is to be fixed? Is there some way of forcing fsck to do a more thorough check? Cheers Philip Murray FreeBSD 4.11-STABLE #4: Wed Apr 6 16:45:15 NZST 2005 Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Pentium(R) III CPU family 1400MHz (1399.33-MHz 686- class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbffMCA,CMOV,PAT,PSE36,MMX,FXSR,SSE> real memory = 2147418112 (2097088K bytes) avail memory = 2087903232 (2038968K bytes) Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec0 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Preloaded elf kernel "kernel" at 0xc03b. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00f5240 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #1 intpin 0 -> irq 2 IOAPIC #1 intpin 15 -> irq 10 IOAPIC #0 intpin 10 -> irq 11 pci0: on pcib0 twe0: <3ware Storage Controller driver ver. 1.40.01.002> port 0xd400-0xd40f irq 2 at device 1.0 on pci0 twe0: 4 ports, Firmware FE6X 1.02.00.029, BIOS BEXX 1.07.00.009 pci0: at 4.0 fxp0: port 0xd000-0xd03f mem 0xfe90-0xfe9f,0xfeace000-0xfeacefff irq 10 at device 6.0 on pci0 fxp0: Ethernet address 00:30:48:22:a6:1e inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ohci0: mem 0xfeacf000-0xfeac irq 11 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on motherboard pci1: on pcib1 orm0: at iomem 0xc-0xc7fff,0xc8000-0xc8fff, 0xc9800-0xca7ff on isa0 pmtimer0 on isa0 fdc0: ready for input in output fdc0: cmd 3 failed at out byte 1 of 3 atkbdc0: at port 0x60,0x64 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 SMP: AP CPU #1 Launched! ad0: 76319MB [155061/16/63] at ata0-master UDMA33 twed0: on twe0 twed0: 228954MB (468898176 sectors) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Reoccurring filesystem corruption
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 and fsck claims to have fixed all the corruption. Then, anywhere from a week to a month later, it starts happening again and gets worse and worse. You didn't mention it explicitly, but I think it's relevant: is the file system in question mounted (read-write) at the time you do the fsck? No, it's mounted read-only. I've also done it during early-startup when the filesystem isn't mounted at all. Cheers Philip Murray ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Reoccurring filesystem corruption
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 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: ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Create 2.5TB file system on 5.4S?
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 a new drive and failed miserably. And after googling a bit I now know why, and realized that I knew why before, but I was being stupid. I've seen a few mentions of using gpt(8) and some vague references to using dedicated mode. But I haven't seen anything that says "this is the Right Way to do it". So...what's the proper way to make a large file system? 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)... :-) Erik This message was sent using IMP, the Internet Messaging Program. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Create 2.5TB file system on 5.4S?
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 > 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 googling a bit I now know why, and > realized that I knew why before, but I was being stupid. > > I've seen a few mentions of using gpt(8) and some vague references to using > dedicated mode. But I haven't seen anything that says "this is the Right Way > to do it". So...what's the proper way to make a large file system? > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Create 2.5TB file system on 5.4S?
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 minutes ago I tried using gpt(8) to create a partition and then I newfs'd the whole thing using the defaults. It appears to have worked, but I have no idea if I did it right or if there's a better way. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Create 2.5TB file system on 5.4S?
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 server and I don't want to have to deal with splitting the database across two partitions. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IRQ conflict between twa0 and skc0
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 gigabit ethernet chip. Fortunately the slot swap seems to have sorted everything out. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
