Re: MegaRaid i4

2006-01-07 Thread Pailloncy Jean-Gerard
Yes, ide vs scsi benchmarks are usually skewed due to caching.   
SCSI disables

drive cache by default whereas IDE enables it by default.

Yes, I disable caching. So I get (really) bad performance.

I see the other thread about some broken MegaRaid i4.

What I can say is taht with 3.8-release, I have no problem to use  
bioctl.

# bioctl -i ami0
Volume  Status Size   Device
ami0 0 Online   249998344192 sd0 RAID1
  0 Online   249998344192 0:0.0   noencl Maxtor  
4A250J0  RAMB
  1 Online   249998344192 2:1.0   noencl Maxtor  
4A250J0  RAMB

ami0 1 Online   249998344192 sd1 RAID1
  0 Online   249998344192 3:0.0   noencl Maxtor  
4A250J0  RAMB
  1 Online   249998344192 1:1.0   noencl Maxtor  
4A250J0  RAMB

ami0 2 Degraded 46688384 sd2 RAID5
  0 Online   249998344192 3:1.0   noencl Maxtor  
4A250J0  RAMB
  1 Rebuild  249998344192 1:0.0   noencl Maxtor  
4A250J0  RAMB
  2 Online   249998344192 2:0.0   noencl Maxtor  
4A250J0  RAMB
ami0 3 Hot spare249998344192 0:1.0   noencl Maxtor  
4A250J0  RAMB


I broke the RAID-5 and it starts rebuilding.
I can setup new Hot-Spare.


But nothing was perfect, I had two crashes. I do not have ps and  
trace because I was using ddb.panic=0 to reboot the prod server  
automatically. The crash happens when I was on console, I disable  
ddb.panic=1, but luckily I get no other crash. And I can not do  
postmortem analysis because /var is to small to keep coredump in /var/ 
crash. I did not have test current. I do not want to stop this server  
too long.


So, here is the partial crash report (the dmesg is in one of my other  
mails in this thread). I hope it will be partially useful ;-)


fsync failed: type VDIR, usecount 0, writecount 0, holdcount 1, flags  
(VBIOONFREELIST|VBIOONSYNCLIST)
tag VT_UFS, ino 6987542, on dev 0, 9 flags 0x0, effnlink 2,  
nlink 2

mode 040755, owner 1000, group 1000, size 512 not locked
mounted on: /mnt
panic: sched_sync: fsync failed
Starting stack trace...
panic(d057fa84,d7c73960,ea077f5c,d7c73960,d7c73960) at panic+0x71
panic(d04f9970,d1b8b29c,d7d078f8,d17b4620,4) at panic+0x71
sched_sync(d7d078f8) at sched_sync+0x17a
Bad frame pointer: 0xd06f1ed8
End of stack trace.
syncing disks... 250 250 248 244 230 212 199 181 164 150 135 124 112  
108 102 89 69 45 23 1 giving up

rebooting...

fsync failed: type VDIR, usecount 0, writecount 0, holdcount 1, flags  
(VBIOONFREELIST|VBIOONSYNCLIST)
tag VT_UFS, ino 7011086, on dev 0, 9 flags 0x0, effnlink 2,  
nlink 2

mode 040755, owner 1000, group 1000, size 512 not locked
mounted on: /mnt
panic: sched_sync: fsync failed
Starting stack trace...
panic(d057fa84,d7c53e60,ea077f5c,d7c53e60,d7c53e60) at panic+0x71
panic(d04f9970,d18eda9c,d7d078f8,d17b467c,4) at panic+0x71
sched_sync(d7d078f8) at sched_sync+0x17a
Bad frame pointer: 0xd06f1ed8
End of stack trace.
syncing disks... 320 320 318 318 318 318 318 318 314 311 303 293 285  
280 269 254 240 233 230 221 giving up

sd2: WARNING: cache synchronization failed
rebooting...

Cordialement,
Jean-Girard Pailloncy



Re: MegaRaid i4

2006-01-07 Thread Marco Peereboom
I was talking about the cache on the disks, not on the controller.  The issues
you experienced were due to the OpenBSD driver not marking the i4 as broken.
The workaround code is now in tree implying that only 1 IO can be outstanding
and bioctl will no longer function.  So update to the latest -stable or
-current and besides some slower performance the system should be stable and
useful.

I tried to fix this before but I haven't been able to determine what causes
these issues.  I will give this another go at some point.

On Sat, Jan 07, 2006 at 10:35:25AM +0100, Pailloncy Jean-Gerard wrote:
 Yes, ide vs scsi benchmarks are usually skewed due to caching.   
 SCSI disables
 drive cache by default whereas IDE enables it by default.
 Yes, I disable caching. So I get (really) bad performance.
 
 I see the other thread about some broken MegaRaid i4.
 
 What I can say is taht with 3.8-release, I have no problem to use  
 bioctl.
 # bioctl -i ami0
 Volume  Status Size   Device
 ami0 0 Online   249998344192 sd0 RAID1
   0 Online   249998344192 0:0.0   noencl Maxtor  
 4A250J0  RAMB
   1 Online   249998344192 2:1.0   noencl Maxtor  
 4A250J0  RAMB
 ami0 1 Online   249998344192 sd1 RAID1
   0 Online   249998344192 3:0.0   noencl Maxtor  
 4A250J0  RAMB
   1 Online   249998344192 1:1.0   noencl Maxtor  
 4A250J0  RAMB
 ami0 2 Degraded 46688384 sd2 RAID5
   0 Online   249998344192 3:1.0   noencl Maxtor  
 4A250J0  RAMB
   1 Rebuild  249998344192 1:0.0   noencl Maxtor  
 4A250J0  RAMB
   2 Online   249998344192 2:0.0   noencl Maxtor  
 4A250J0  RAMB
 ami0 3 Hot spare249998344192 0:1.0   noencl Maxtor  
 4A250J0  RAMB
 
 I broke the RAID-5 and it starts rebuilding.
 I can setup new Hot-Spare.
 
 
 But nothing was perfect, I had two crashes. I do not have ps and  
 trace because I was using ddb.panic=0 to reboot the prod server  
 automatically. The crash happens when I was on console, I disable  
 ddb.panic=1, but luckily I get no other crash. And I can not do  
 postmortem analysis because /var is to small to keep coredump in /var/ 
 crash. I did not have test current. I do not want to stop this server  
 too long.
 
 So, here is the partial crash report (the dmesg is in one of my other  
 mails in this thread). I hope it will be partially useful ;-)
 
 fsync failed: type VDIR, usecount 0, writecount 0, holdcount 1, flags  
 (VBIOONFREELIST|VBIOONSYNCLIST)
 tag VT_UFS, ino 6987542, on dev 0, 9 flags 0x0, effnlink 2,  
 nlink 2
 mode 040755, owner 1000, group 1000, size 512 not locked
 mounted on: /mnt
 panic: sched_sync: fsync failed
 Starting stack trace...
 panic(d057fa84,d7c73960,ea077f5c,d7c73960,d7c73960) at panic+0x71
 panic(d04f9970,d1b8b29c,d7d078f8,d17b4620,4) at panic+0x71
 sched_sync(d7d078f8) at sched_sync+0x17a
 Bad frame pointer: 0xd06f1ed8
 End of stack trace.
 syncing disks... 250 250 248 244 230 212 199 181 164 150 135 124 112  
 108 102 89 69 45 23 1 giving up
 rebooting...
 
 fsync failed: type VDIR, usecount 0, writecount 0, holdcount 1, flags  
 (VBIOONFREELIST|VBIOONSYNCLIST)
 tag VT_UFS, ino 7011086, on dev 0, 9 flags 0x0, effnlink 2,  
 nlink 2
 mode 040755, owner 1000, group 1000, size 512 not locked
 mounted on: /mnt
 panic: sched_sync: fsync failed
 Starting stack trace...
 panic(d057fa84,d7c53e60,ea077f5c,d7c53e60,d7c53e60) at panic+0x71
 panic(d04f9970,d18eda9c,d7d078f8,d17b467c,4) at panic+0x71
 sched_sync(d7d078f8) at sched_sync+0x17a
 Bad frame pointer: 0xd06f1ed8
 End of stack trace.
 syncing disks... 320 320 318 318 318 318 318 318 314 311 303 293 285  
 280 269 254 240 233 230 221 giving up
 sd2: WARNING: cache synchronization failed
 rebooting...
 
 Cordialement,
 Jean-Girard Pailloncy



MegaRaid i4

2006-01-05 Thread Pailloncy Jean-Gerard

Hi,

I have a MegaRaid i4 card on an OpenBSD 3.8 box.
The speed of the card is very slow.
max: read  15 M/s, write  5 M/s
average: read 8 M/s, write 2.5 M/s

I have an other identical drive on the internal IDE bus, and it is at  
least three times faster.


Any idea ?

The card is on Mass Storage Mode.
I never change it, nor test the IOP mode.
Is it worth to try ? The man page recommends the use of the Mass  
Storage mode.


Is is safe to switch from one mode to an other ? Will the data be  
preserved ?


Jean-Girard Pailloncy



Re: MegaRaid i4

2006-01-05 Thread J.C. Roberts
On Thu, 5 Jan 2006 16:20:32 +0100, Pailloncy Jean-Gerard [EMAIL PROTECTED]
wrote:

Hi,

I have a MegaRaid i4 card on an OpenBSD 3.8 box.
The speed of the card is very slow.
max: read  15 M/s, write  5 M/s
average: read 8 M/s, write 2.5 M/s

I have an other identical drive on the internal IDE bus, and it is at  
least three times faster.

Any idea ?

The card is on Mass Storage Mode.
I never change it, nor test the IOP mode.
Is it worth to try ? The man page recommends the use of the Mass  
Storage mode.

Is is safe to switch from one mode to an other ? Will the data be  
preserved ?

Jean-Girard Pailloncy

Where's your dmesg?

New work on the i4 has been committed to both -CURRENT and -STABLE by
marco@ and dlg@ during December. Since my mind reading skills are very
poor, I can't see what the heck you're running without a dmesg.

jcr



Re: MegaRaid i4

2006-01-05 Thread Marco Peereboom
On Thu, Jan 05, 2006 at 04:20:32PM +0100, Pailloncy Jean-Gerard wrote:
 Hi,
 
 I have a MegaRaid i4 card on an OpenBSD 3.8 box.
 The speed of the card is very slow.
 max: read  15 M/s, write  5 M/s
 average: read 8 M/s, write 2.5 M/s

It is a very very old card (1995ish) and on top of that there is a
unfortunately a firmware issue that prevents us from running more than 1
command at a time.  You should get a PERC 3 or 4 instead.

 
 I have an other identical drive on the internal IDE bus, and it is at  
 least three times faster.
 
 Any idea ?

Yes, ide vs scsi benchmarks are usually skewed due to caching.  SCSI disables
drive cache by default whereas IDE enables it by default.

 
 The card is on Mass Storage Mode.
 I never change it, nor test the IOP mode.
 Is it worth to try ? The man page recommends the use of the Mass  
 Storage mode.
 
 Is is safe to switch from one mode to an other ? Will the data be  
 preserved ?

It is safe to switch however only mass-storage works on OpenBSD.

 
 Jean-Girard Pailloncy



Re: MegaRaid i4

2006-01-05 Thread Pailloncy Jean-Gerard

Where's your dmesg?

OpenBSD 3.8 (GENERIC) #138: Sat Sep 10 15:41:37 MDT 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) 4 CPU 2.40GHz (GenuineIntel 686-class)  
2.40 GHz
cpu0:  
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36, 
CFLUSH,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,CNXT-ID

real mem  = 1073324032 (1048168K)
avail mem = 757698560 (739940K)
using 4278 buffers containing 268853248 bytes (262552K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(00) BIOS, date 08/18/04, BIOS32 rev. 0 @  
0xfdb80

apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 30102 dobusy 0 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf4f70/272 (15 entries)
pcibios0: PCI Interrupt Router at 000:01:7 (ServerWorks CSB5  
SouthBridge rev 0x00)

pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x1200 0xc9800/0x1000  
0xca800/0x1800

cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 ServerWorks CMIC_SL Host rev 0x32
pchb1 at pci0 dev 0 function 1 ServerWorks CMIC_SL Host rev 0x00
pci1 at pchb1 bus 1
puc0 at pci0 dev 4 function 0 Lava Quad Serial rev 0x00: com, com,  
com, com

pccom3 at puc0 port 0 irq 5: ns16550a, 16 byte fifo
pccom4 at puc0 port 1 irq 5: ns16550a, 16 byte fifo
pccom5 at puc0 port 2 irq 5: ns16550a, 16 byte fifo
pccom6 at puc0 port 3 irq 5: ns16550a, 16 byte fifo
puc1 at pci0 dev 4 function 1 Lava Quad Serial rev 0x00: com, com,  
com, com

pccom7 at puc1 port 0 irq 5: ns16550a, 16 byte fifo
pccom8 at puc1 port 1 irq 5: ns16550a, 16 byte fifo
pccom9 at puc1 port 2 irq 5: ns16550a, 16 byte fifo
pccom10 at puc1 port 3 irq 5: ns16550a, 16 byte fifo
ami0 at pci0 dev 5 function 0 AMI MegaRAID rev 0x02: irq 10 AMI  
511/64b/lhc

ami0: FW N661, BIOS v1.01, 16MB RAM
ami0: 4 channels, 0 FC loops, 3 logical drives
scsibus0 at ami0: 40 targets
sd0 at scsibus0 targ 0 lun 0: AMI, Host drive #00,  SCSI2 0/direct  
fixed
sd0: 238417MB, 30393 cyl, 255 head, 63 sec, 512 bytes/sec, 488278016  
sec total
sd1 at scsibus0 targ 1 lun 0: AMI, Host drive #01,  SCSI2 0/direct  
fixed
sd1: 238417MB, 30393 cyl, 255 head, 63 sec, 512 bytes/sec, 488278016  
sec total
sd2 at scsibus0 targ 2 lun 0: AMI, Host drive #02,  SCSI2 0/direct  
fixed
sd2: 476834MB, 60787 cyl, 255 head, 63 sec, 512 bytes/sec, 976556032  
sec total

scsibus1 at ami0: 16 targets
scsibus2 at ami0: 16 targets
scsibus3 at ami0: 16 targets
scsibus4 at ami0: 16 targets
vga1 at pci0 dev 7 function 0 ATI Rage XL rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
fxp0 at pci0 dev 8 function 0 Intel 82557 rev 0x10, i82551: irq 9,  
address 00:e0:81:24:f0:96

inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
pcib0 at pci0 dev 15 function 0 ServerWorks CSB5 SouthBridge rev 0x93
pciide0 at pci0 dev 15 function 1 ServerWorks CSB5 IDE rev 0x93: DMA
wd0 at pciide0 channel 0 drive 0: Maxtor 4A250J0
wd0: 16-sector PIO, LBA48, 239372MB, 490234752 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus5 at atapiscsi0: 2 targets
cd0 at scsibus5 targ 0 lun 0: MITSUMI, CD-ROM SR244W, T01A SCSI0 5/ 
cdrom removable

cd0(pciide0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 2
pchb2 at pci0 dev 15 function 3 ServerWorks CSB5 PCI rev 0x00
pchb3 at pci0 dev 16 function 0 ServerWorks CIOBX2 rev 0x03
pchb4 at pci0 dev 16 function 2 ServerWorks CIOBX2 rev 0x03
pci2 at pchb4 bus 2
em0 at pci2 dev 7 function 0 Intel PRO/1000MT (82545EM) rev 0x01:  
irq 11, address: 00:e0:81:24:f0:97

isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom0: console
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask f545 netmask ff45 ttymask ffc7
pctr: user-level cycle counter enabled
dkcsum: sd0 matches BIOS drive 0x80
dkcsum: sd1 matches BIOS drive 0x81
dkcsum: sd2 matches BIOS drive 0x82
dkcsum: wd0 matches BIOS drive 0x83
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02


Cordialement,
Jean-Girard Pailloncy



LSI MegaRAID i4 in 3.8

2005-09-29 Thread Steven R. Gerber

I might want to use a pair Maxtor 250GB (PATA/IDE).
Will the old LSI MegaRAID i4 be fully supported in 3.8? like the 150-4?

Thanks,
Steven

--
Steven R. Gerber
Gerber Systems Design
305 Madison Avenue, Suite 449
New York, NY 10165
212-807-4174
http://www.Gerber-Systems.com