Re: Softupdates question
On 5/9/07, Nick Holland <[EMAIL PROTECTED]> wrote: If it was not obvious from my comments, I love softdeps. I have a siteXX.tgz file which does a few simple things, one of which is to change all mount points to use softdeps. One really does have to hunt a bit for relevant reasons not to use it. About the only place I can think of where I deliberately don't use it is on an e-mail archive system on the filled partitions which are mounted read-only. I can't tell you how many times I have forgot to install my siteXX file, started loading up /usr/src, and realized, "Dang, obviously no softdeps". At which point, I stop the checkout, fix the problem, reboot, and try again. Yes, the performance difference is that obvious, and it is faster to reboot than it is to wait it out. I'm still curious about the issue of using softdep's when you have a raid card with write-cache (and battery)... I thought I'd do a simple test unpacking the ports.tar.gz with softdeps disabled/enabled, to see for myself. Without softdep enabled, I have the following: [EMAIL PROTECTED] time tar xzf ports.tar.gz 0.970u 2.120s 1:00.62 5.0% 0+0k 9821+210784io 6pf+0w [EMAIL PROTECTED] time rm -r ports 0.160u 1.390s 1:01.65 2.5% 0+0k 14994+126181io 17pf+0w About a minute to unpack and another minute to remove. With softdep enabled, I have the following: [EMAIL PROTECTED] time tar xzf ports.tar.gz 1.270u 2.100s 0:45.62 7.3% 0+0k 9874+66318io 59pf+0w [EMAIL PROTECTED] time rm -r ports 0.210u 1.230s 0:14.59 9.8% 0+0k 15741+22055io 17pf+0w 45 seconds to unpack and 15 seconds to remove. (I've repeated this a few times each way, and I always have roughly the same results.) With softdep enabled, there was more cpu time, but a noticeable decrease in total time. So, fair to say that even with raid+write-cache+battery that softdep's are beneficial (in terms of less disk time)? I'm more interested in maintaining disk-consistency, and with this setup, it looks like softdeps will still help with that also. Thanks again for all the info! -George
Re: Softupdates question
On 5/8/07, mickey <[EMAIL PROTECTED]> wrote: On Tue, May 08, 2007 at 07:06:06AM -0400, Nick Holland wrote: > George C wrote: > > I've just stumbled across the SoftUpdates section in the FAQ, and was rather > > surprised that I had never seen/heard of this feature before. Before > > I mount any > > partition using softdep, I thought I'd google, browse the archives, etc. for any > > information about when/where they should be used. > > > > Although I've found a plethora of information about soft updates, much of it is > > either contradictory or incomplete I thought I'd ask here for clarification. > > > > Is it always best to mount /, /tmp, /usr, /var, /home with softdep? > > Under what curcumstances would it not be appropriate? > > Softdeps don't do anything for you if you are mostly reading from disk, > or if the partition is mounted read-only. It's about writing. of course they do. there are still atime updates for example that will be handled if not mount read-only. So, given the above two comments... sounds like softdep would be both "safe" and beneficial for (at least) /usr and /var. Probably also for /var/www. Still curious how they would work on, say, /var/mysql or /var/postgresql, but I can play with this on my own. Has anyone already tried? Care to comment? > All these machines have a perc5 raid controller using mfi driver does that > make a difference? yes... IF the RAID card has a write cache, SOME of the advantage of softdeps may not exist. On the other hand, if it doesn't have the battery, your write performance is so horrible, you probably want softdeps badly. Hmm. My cards do have a write cache w/ battery. So in this case, it looks like softdep on any partition would be inappropriateis that correct? Is this simply because the raid card (with write cache) is basically doing what softdep does? Many Thanks for all the advice! -George
Softupdates question
I've just stumbled across the SoftUpdates section in the FAQ, and was rather
surprised that I had never seen/heard of this feature before. Before
I mount any
partition using softdep, I thought I'd google, browse the archives, etc. for any
information about when/where they should be used.
Although I've found a plethora of information about soft updates, much of it is
either contradictory or incomplete I thought I'd ask here for clarification.
Is it always best to mount /, /tmp, /usr, /var, /home with softdep?
Under what curcumstances would it not be appropriate?
I have a few machines running a busy website (mounted on /var/www) and two
fairly-busy databases (mysql mounted on /var/www and postgresql mounted on
/var/postgresql).
All these machines have a perc5 raid controller using mfi driver does that
make a difference?
Running 4.1 MP + patches on all machines (just got the CDs and it's
awesome!)...dmesg below.
-George
p.s. Thanks for the new release! I'm already enjoying it! (and the poster!)
OpenBSD 4.1 (GENERIC.MP) #2: Sun May 6 18:14:39 EDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2,CX16,xTPR
real mem = 2146697216 (2096384K)
avail mem = 1951940608 (1906192K)
using 4278 buffers containing 107458560 bytes (104940K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+ BIOS, date 10/18/06, BIOS32 rev. 0 @
0xffe90, SMBIOS rev. 2.4 @ 0x7ffbc000 (62 entries)
bios0: Dell Inc. PowerEdge 2900
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfada0/432 (25 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 6321ESB LPC" rev 0x00)
pcibios0: PCI bus #16 is the last bus
bios0: ROM list: 0xc/0x9000! 0xc9000/0x1000 0xca000/0x1800
0xcb800/0x5200 0xec000/0x4000!
acpi at mainbus0 not configured
ipmi0 at mainbus0: version 2.0 interface KCS iobase 0xca8/8 spacing 4
mainbus0: Intel MP Specification (Version 1.4)
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 332 MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2,CX16,xTPR
cpu2 at mainbus0: apid 6 (application processor)
cpu2: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu2:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2,CX16,xTPR
cpu3 at mainbus0: apid 7 (application processor)
cpu3: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz
cpu3:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2,CX16,xTPR
mainbus0: bus 0 is type PCI
mainbus0: bus 1 is type PCI
mainbus0: bus 2 is type PCI
mainbus0: bus 3 is type PCI
mainbus0: bus 4 is type PCI
mainbus0: bus 5 is type PCI
mainbus0: bus 6 is type PCI
mainbus0: bus 7 is type PCI
mainbus0: bus 8 is type PCI
mainbus0: bus 9 is type PCI
mainbus0: bus 10 is type PCI
mainbus0: bus 11 is type PCI
mainbus0: bus 12 is type PCI
mainbus0: bus 13 is type PCI
mainbus0: bus 14 is type PCI
mainbus0: bus 15 is type PCI
mainbus0: bus 16 is type PCI
mainbus0: bus 17 is type ISA
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
ioapic1 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins
ioapic1: misconfigured as apic 0, remapped to apid 9
ioapic2 at mainbus0: apid 10 pa 0xfec83000, version 20, 24 pins
ioapic2: misconfigured as apic 0, remapped to apid 10
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 5000X Host" rev 0x12
ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0x12
pci1 at ppb0 bus 6
ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
pci2 at ppb1 bus 7
ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01
pci3 at ppb2 bus 8
ppb3 at pci3 dev 0 function 0 "ServerWorks PCIE-PCIX" rev 0xc2
pci4 at ppb3 bus 9
bnx0 at pci4 dev 0 function 0 "Broadcom BCM5708" rev 0x11: apic 8 int 16 (irq 5)
ppb4 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01
pci5 at ppb4 bus 10
ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01
pci6 at ppb5 bus 11
ral0 at pci6 dev 2 function 0 "Ralink RT2561S" rev 0x00: apic 9 int 4
(irq 5), address 00:0e:2e:8d:26:66
ral0: MAC/BBP RT2561C, RF RT2527
ppb6 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0x12
pci7 at ppb6 bus 12
ppb7 at pci0 dev 4 function 0 "Intel 5000 PCIE" rev 0x12
pci8 at ppb7 bus 13
ppb8 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0x12
pci9 at ppb8 bus 1
ppb9
Re: upgraded to current - need bnx firmware?
On 12/27/06, Ingo Schwarze <[EMAIL PROTECTED]> wrote:
Ryan Flannery wrote on Tue, Dec 26, 2006 at 07:26:59PM -0500:
> On 12/26/06, George C <[EMAIL PROTECTED]> wrote:
>> I just upgraded my 4.0 system to -current (GENERIC.MP),
You mean, before that, you had a 4.0-release or -stable system?
Just a wild guess since you explicitely mention the kernel:
Did you also extract the -current base40.tgz file set?
I had a 4.0-release install right from the cd pack. I extracted the source
from the cd and then updated it to -current (both /usr/src and /usr/src/sys).
then i built the new kernel, reboot, and was going to build the userland
when i ran into the bnx firmware problem.
i installed the firmware following the instructions above, reboot, and then
attempted to build the userland.
In section 5.3.4 of the FAQ, after building & installing the new kernel...
"At this point, reboot your machine to activate this new kernel. Note
that the new kernel should be running before the next step, though if
you have followed the above advice about upgrading to the most
recent available snapshot, it may not matter as much. Sometimes,
however, APIs change, and the old kernel will be unable to run new
applications, but the new kernel will generally support the old ones."
however, when I went to build the userland (after rebooting with the new
kernel and rebooting after installing the bnx firmware), the build itself went
fine (as far as i can tell) but when it was installing everything, i got the
following kernel panic:
uvm_fault(0xd0761680, 0xefd32000, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pmap_page_remove_86+0x114: movl 0(%eax, %edx, 4), %eax)
ddb{3}>
(my USB keyboard stopped working at that point, and i could not obtain a 'ps'
or 'trace' output...my apologies)
when I reboot, I get the following error after "most" of the kernel
loads, right afer
the two bnx devices are found:
init: not found
panic: no init
Stopped at Debugger+0x4: leave
I guess I should NOT have reboot before building the userland? After
reading the portion of the FAQ I posted above, I thought rebooting would
be the 'safe' thing to do.
See http://www.openbsd.org/faq/faq5.html#Flavors:
|| Keeping Things in Sync
|| It is important to understand that OpenBSD is an Operating System,
|| intended to be taken as a whole, not a kernel with a bunch of
|| utilities stuck on. You must make sure your kernel, "userland"
|| (the supporting utilities and files) and ports tree are all in
|| sync, or unpleasant things will happen. Said another way (because
|| people just keep making the error), you can not run brand new ports
|| on a month old system, or rebuild a kernel from -current source and
|| expect it to work with a -release userland.
Note the last sentence in particular.
>> and when I reboot, the two bnx devices could not find firmware
>> in /etc/firmware. It appears to be looking for /etc/firmware/bnx,
>> but that file is not present.
> try the following:
> # cd /usr/src/sys/dev/microcode/bnx
> # make
>
> that should produce a file named 'bnx' in that directory. copy it to
> /etc/firmware and reboot.
That may solve the immediate problem, but i suspect you might have
more problems than you noticed yet.
>> I can reboot the old kernel just fine (so it appears the old bnx
>> driver did not require it). Curious how/where the new firmware for
>> bnx is located at, and where I can obtain a copy.
>>
>> Is there some step I missed in the upgrade procedure that builds/adds
>> these firmware files? or is this simply done separately?
No, at least on i386, they are just contained in base40.tgz.
>> I followed the FAQ.
Very strange. After properly updating to 4.0-current on i386,
/etc/firmware/bnx is in place. I just did a source upgrade of
my development machine tonight:
[EMAIL PROTECTED] $ sysctl kern.version
kern.version=OpenBSD 4.0-current (GENERIC) #3: Tue Dec 26 20:45:43 CET 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
[EMAIL PROTECTED] $ grep bnx make-061226.log | tail -n3
===> sys/dev/microcode/bnx
install -c -o root -g bin -m 644 bnx /etc/firmware
install -c -o root -g bin -m 644
/usr/src/sys/dev/microcode/bnx/bnx-license /etc/firmware
[EMAIL PROTECTED] $ ll /etc/firmware/bnx
-rw-r--r-- 1 root bin 87616 Dec 27 01:26 /etc/firmware/bnx
The Dec 25 snapshot looks fine, too:
[EMAIL PROTECTED] $ tar -tzvf base40.tgz | grep 'etc.*bnx'
-rw-r--r-- 1 root bin 87616 Dec 25 11:50 ./etc/firmware/bnx
-rw-r--r-- 1 root bin 1946 Dec 25 11:50 ./etc/firmware/bnx-license
Obviously, something went wrong in your case.
Do not rely on the correctness of your system
before you understand what exactly was screwed up.
>> Also I've google'ed the archives/web for any answer to these
>> questions... unfortunately the web & mail archives are full of
>> references to the iwi firmware licensing issue, and little else.
upgraded to current - need bnx firmware?
Hello misc, I just upgraded my 4.0 system to -current (GENERIC.MP), and when I reboot, the two bnx devices could not find firmware in /etc/firmware. It appears to be looking for /etc/firmware/bnx, but that file is not present. I can reboot the old kernel just fine (so it appears the old bnx driver did not require it). Curious how/where the new firmware for bnx is located at, and where I can obtain a copy. Is there some step I missed in the upgrade procedure that builds/adds these firmware files? or is this simply done separately? I followed the FAQ. Also I've google'ed the archives/web for any answer to these questions... unfortunately the web & mail archives are full of references to the iwi firmware licensing issue, and little else. -GeorgeC
Re: symon w/ multiple CPU's
Many thanks to you both!
-George
On 12/19/06, Jason Dixon <[EMAIL PROTECTED]> wrote:
On Dec 19, 2006, at 3:29 PM, Henning Brauer wrote:
> * George C <[EMAIL PROTECTED]> [2006-12-19 20:19]:
>> Hello misc,
>> Anyone know if symon is able to read stats from multiple CPU's in the
>> 4.0 GENERIC.SMP kernel? I have the following in my symon.conf:
>>
>> $ cat /etc/symon.conf
>> monitor { cpu(0), cpu(1), cpu(2), cpu(3), mem, mbuf, pf,
>> if(lo0), if(bnx0), if(bnx1),
>> io(sd0), io(sd1), io(sd2), io(sd3)
>> } stream to 127.0.0.1 2100
>>
>>
>> But all of the CPU data recorded for each CPU (0-3) is the exact same
>> (even the cpu rrd files that the symux client logs to for this host
>> are identical).
>
> just ran into that as well; it's a bug in symon, it only queries the
> sum of all CPUs.
> i have it almost fixed, except it doesn't work yet :)
I reported this to Willem back in September but haven't seen any
updates. Perhaps Darrin would be willing to share his diff.
--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net
symon w/ multiple CPU's
Hello misc,
Anyone know if symon is able to read stats from multiple CPU's in the
4.0 GENERIC.SMP kernel? I have the following in my symon.conf:
$ cat /etc/symon.conf
monitor { cpu(0), cpu(1), cpu(2), cpu(3), mem, mbuf, pf,
if(lo0), if(bnx0), if(bnx1),
io(sd0), io(sd1), io(sd2), io(sd3)
} stream to 127.0.0.1 2100
But all of the CPU data recorded for each CPU (0-3) is the exact same
(even the cpu rrd files that the symux client logs to for this host
are identical).
-George
Intel 51xx's and E53xx's support and recommendation
Hello misc, My company is upgrading a number of our servers, and I've been browsing the various lists and Google'ing to find answers to the following... We're looking at ordering a number of the dell PowerEdge 2900 machines for a number of applications (mostly database/web). In configuring these, we're weighing our options on choosing one of the following setups: 1. Two Intel dual core 5130's (2GHz w/ 4MB cache @ 1333MHz fsb), or 2. One Intel quad core E5310 (1.6GHz w/ 2x4MB cache @ 1066MHz fsb) I've been trying to figure out if these are supported at this time, and so far on the lists I've found "Yes" but with a few instances of stability problems. My questions are: 1. Are both of these cpu's supported and stable at this time? 2. In your opinion, for a set of DB servers (postgresql) and web servers (apache base w/ php 5), which of the options above (2 dual core or 1 quad core) would OpenBSD work best with? Many thanks, -George C.
