Remote server hanging on boot please read
This is the day I've been dreading for just under two years of trouble free service. My colocated server which is a 4 hour drive away has broken. It is hanging on the white-on-blue boot message at Kernelized Raidframe activated and will proceed no further. According to the on site tech there appears to be no HDD activity. If the parity set was dirty it would continue past this to the 'raid0: Initiating re-write of parity' message. Box details - OpenBSD3.4 release i386 generic with raidframe, 2x200GB EIDE drives in raidframe mirror, 1u rack, IDE DVD-Rom, PIII 1.2Ghz, 1GB Ram. I've never seen it hang at this line before. The tech says he can shift-page-up/page-down but alt-ctrl-del and enter are non-responsive. Please has anyone experienced this before? The box was being rebooted at the time and was working perfectly just seconds before. Can anyone suggest a course of action? would you advise yanking a HD one after the other to see what happens or perhaps trying to boot in single user (and if so how and what to try)? many thanks in advance Gary
Re: Help needed with SMTP please
Jaap Versteegh wrote: Gary Clemans-Gibbon wrote: I guess therefore that I don't need SASL or any authenticated SMTP. I'm guessing that I need somehow to allow relaying in mail.cf ? http://www.metaconsultancy.com/whitepapers/smtp.htm#s6 and then to block port 25 on the external interface to stop ppl outside the server connecting to relay spam. Are you sure that your ISP isn't doing exactly this on their gateway in order to prevent you from spamming ;) ? Jaap Versteegh . What ISP? The server is co-located and nothing is blocked other than what I block with pf. Thanks for that link - very useful. I've tried a couple of things in main.cf.. mynetworks = 127.0.0.0/8 and smtpd_recipient_restrictions = permit_mynetworks, permit but still no luck. FWIW when the mail fails I also get the following line in the browser window... Mailer Error: Language string failed to load: [EMAIL PROTECTED]
Help needed with SMTP please
I have a web server running apache/php/mysql for web and postfix/courier for mail. using the PEAR php code for sending mail my server can successfully send mail from a php script as long as the recipient is a local domain. (I can pick up the mail remotely using pop3). If I try to send to a non-local domain I get an error about relaying (see below for php output of successful send and failed send). All I want is for the php scripts to be able to send mail to addresses outside the server. I do not need to use the server as an smtp server from remote locations. I guess therefore that I don't need SASL or any authenticated SMTP. I'm guessing that I need somehow to allow relaying and then to block port 25 on the external interface to stop ppl outside the server connecting to relay spam. Is this a correct assumption or am I barking up the wrong tree? The box is running (i386) generic with raidframe, OpenBSD3.4, Postfix, Courier IMAP, Apache. Please can someone point me in the right direction? Here is the php output of a successful send (to local domain) ... SMTP -> FROM SERVER: 250 Ok: queued as 889C14CBC80 SMTP -> get_lines(): $data was "" SMTP -> get_lines(): $str is "221 Bye " SMTP -> get_lines(): $data is "221 Bye " SMTP -> FROM SERVER: 221 Bye Message has been sent Here is the unsuccessful send (to foreign domain)... SMTP -> FROM SERVER: 454 : Relay access denied SMTP -> ERROR: RCPT not accepted from server: 454 : Relay access denied SMTP -> get_lines(): $data was "" SMTP -> get_lines(): $str is "250 Ok " SMTP -> get_lines(): $data is "250 Ok " SMTP -> FROM SERVER: 250 Ok Message could not be sent. I can supply dmesg and or any other logs if required (I don't know which logs to check on though!) Many thanks, Gary
Re: Boot hanging following power out - SOLVED
Rogier Krieger wrote: On 8/20/05, Gary Clemans-Gibbon <[EMAIL PROTECTED]> wrote: /dev/rwd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. Can't open /dev/rwd1a: Device not configured CAN'T CHECK FILE SYSTEM. You seem to have a hardware problem. Are you sure the system *detects* your data drive? The dmesg from startup should tell you which devices the kernel detected. Better make sure it didn't die during the outage. Beyond getting a /dev/wd1 back, you will probably want to run fsck(8) after that. Read the man page. You do have backups, don't you? Cheers, Rogier Hi Roger, I just did fsck /dev/rwd1a and rwd2a I uncommented the two entries in fstab and rebooted. All seems OK. I am very relieved. Basically I had a near heart attack because it couldn't run the checks during boot and was hanging like there was a HW problem. Only physically disconnecting the two drives and removing their entries from fstab manually would allow me to run fsck. I'm wondering if I could have fed a command to the boot prompt that would have NOT mounted the two data drives. Would single user mode have not mounted them? Is there some way of doing this at the boot prompt? Still learning... thanks for all the help as always Gary (much relieved)
Re: Boot hanging following power out - it's worse
[EMAIL PROTECTED] wrote: gary, Original message Date: Sat, 20 Aug 2005 12:13:32 -0700 From: Gary Clemans-Gibbon <[EMAIL PROTECTED]> Subject: Re: Boot hanging following power out - it's worse Cc: OpenBSD misc-list I rebooted the box and now it is hanging with Automatic boot in progress: starting file system checks. /dev/rwd0a: file system is clean; not checking and that's the last thing it says. I'm pretty desperate here, there is data on these disks that I cannot lose since my last backup. many many thanks in advance, Gary i would follow the advice of the failure: run fsck manually. to do this boot into single user mode by issuing "boot -s" at the boot prompt. then "fsck -p /dev/wd0a" or whatever partition of whatever drive you want. i usually try to get all the partitions to check out before i manually mount them with "mount /dev/wd0a /", etc. then see if your data is accessible and try to boot into multiuser mode. hth, jake Gary Clemans-Gibbon wrote: Hi, I have an i386 3.7 release generic box running as a file server in my home with three hdds, one for os, two for data. We just had a power surge/outage that lasted a split second but now the box hangs on boot with the following.. Can't open /dev/rwd1a: Device not configured CAN'T CHECK FILE SYSTEM. /dev/rwd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. The boot stops at that point. /dev/rwd1a is one of the data disks. The other checks fine. Please can someone tell me how to get the box to boot and how to fix this please. Thanks in advance Gary . Thanks Dick, I now have the box booted OK but the two data drives are not mounted, their entries in fstab are commented out. As I understand it the drives need to be mounted to run fsck but I can't mount them as it tells me to run fsck! Basically please can you tell me the command to run fsck on an unmounted drive that appears in fstab as follows... #/dev/wd1a /data1 ffs rw 1 2 Sorry to be such a newb but I find the man page a little confusing and the -p option you gave seems to require the device to be mounted. Also I thought that you needed to supply a (mounted) path to fsck like fsck /data1 Can I do fsck /dev/wd1a ? If so what parameters do I need to add. Also should I be using fsck_ffs ? Whats the difference? Thanks Gary
Re: Boot hanging following power out
Tom Cosgrove wrote: "Gary Clemans-Gibbon" 20-Aug-05 20:05 >>> Hi, I have an i386 3.7 release generic box running as a file server in my home with three hdds, one for os, two for data. We just had a power surge/outage that lasted a split second but now the box hangs on boot with the following.. Can't open /dev/rwd1a: Device not configured "Device not configured" usually means that the operating system was not able to find the device. If this is the case, it would indicate a hardware problem. If you post your dmesg to the list it might give some other indication. If dmesg does not show wd1, then it may have been damaged by a power surge. You could try putting the disk into another box to see if it is wd1 or the controller. CAN'T CHECK FILE SYSTEM. /dev/rwd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. The boot stops at that point. /dev/rwd1a is one of the data disks. The other checks fine. Please can someone tell me how to get the box to boot and how to fix this please. Thanks in advance Gary But please post your dmesg to the list. Thanks Tom . Thanks mfor the reply Tom, I'm almost pulling my hair out here. I can't post dmesg because it is hanging on bootup. Now if I disconnect both data hdds then it will boot but not properly ie it asks for shell/terminal etc. With either data disk connected it just hangs. Is there a boot command I can give so that I can boot it with the data drives connected but tell it to skip the auto filechecks? I think we had a power spike as only three or four out of a total of eleven computers rebooted, the rest are fine. If these two (200g) hdds are toasted then I'm having a worse day than I thought. OK (since I started typing this reply) I booted with the drives disconnected, I did mount -a and commented out the two data drives in fstab. Now I am re-booted with the drives connected and I have a normal login prompt. Please, what can I do next? How should I manually check the drives? many, many thanks Gary
Re: Boot hanging following power out - it's worse
I rebooted the box and now it is hanging with Automatic boot in progress: starting file system checks. /dev/rwd0a: file system is clean; not checking and that's the last thing it says. I'm pretty desperate here, there is data on these disks that I cannot lose since my last backup. many many thanks in advance, Gary Gary Clemans-Gibbon wrote: Hi, I have an i386 3.7 release generic box running as a file server in my home with three hdds, one for os, two for data. We just had a power surge/outage that lasted a split second but now the box hangs on boot with the following.. Can't open /dev/rwd1a: Device not configured CAN'T CHECK FILE SYSTEM. /dev/rwd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. The boot stops at that point. /dev/rwd1a is one of the data disks. The other checks fine. Please can someone tell me how to get the box to boot and how to fix this please. Thanks in advance Gary
Boot hanging following power out
Hi, I have an i386 3.7 release generic box running as a file server in my home with three hdds, one for os, two for data. We just had a power surge/outage that lasted a split second but now the box hangs on boot with the following.. Can't open /dev/rwd1a: Device not configured CAN'T CHECK FILE SYSTEM. /dev/rwd1a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY. The boot stops at that point. /dev/rwd1a is one of the data disks. The other checks fine. Please can someone tell me how to get the box to boot and how to fix this please. Thanks in advance Gary
Re: Writes to samba server very, very slow (SOLVED)
Gary Clemans-Gibbon wrote:
Hi All,
I just built a OpenBSD 3.7 samba file server for my home lan. It's a P3
500, 128mb RAM, with a 2 gig IDE HDD for the OS and two x Maxtor 200 GB
IDE drives for data.
Everything is working fine except that when I copy files to the box from
a Windows XP box the transfers are very slow, like 9 minutes for a 48 Mb
file. Copying the same file back to the win box is quick - a couple of
seconds as you'd expect.
Please forgive me if I don't provide all the needed info here or if I
didn't run any obvious checks. Please indicate what info is needed and
how to get it and I'll repost it.
This same hardware was previously running RH7.3 with samba and worked
fine. I've tried a different ethernet cable and a different port on my
switch too.
many thanks in advance,
Gary
Here is /etc/samba/smb.conf global section..
[global]
workgroup = myworkgroup
server string = My Samba Server
hosts allow = 192.168.20. 127.0.0.1
log file = /var/log/smbd.%m
security = user
socket options = TCP_NODELAY IPTOS_LOWDELAY
read raw = yes
write raw = yes
Here is dmesg
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 501 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115580928 (112872K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @ 0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115580928 (112872K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @ 0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Nvidia Riva TNT" rev 0x04
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 4 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 1032MB, 2114180 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
wd2 at pciide0 channel 1 drive 0:
wd2: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <, 52X24X52 CD-RW, 1.07> SCSI0 5/cdrom
removable
wd2(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x02 at pci0 dev 4 function 3 not configured
dc0 at pci0 dev 9 function 0 "ADMtek AN983" rev 0x11: irq 9, address
00:50:bf:fe:83:bc
ukphy0 at dc0 phy 1: Generic IEEE 802.3u media
Re: Writes to samba server very, very slow
Darren Tucker wrote: Gary Clemans-Gibbon wrote: Also I have just grabbed the stable branch from cvs and am running stable GENERIC and still doesn't fix it. Just a recap - the problem is not just samba writes to either of the data disks from the network via samba or scp are painfully slow. Reads from the box to the network are fast. Copying files from one disk to another one the server are fast. Taking the disks out of the equation entirely: does scp'ing a file to /dev/null run fast or slow? $ dmesg [...] uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 9 [...] dc0 at pci0 dev 9 function 0 "ADMtek AN983" rev 0x11: irq 9, address The NIC is sharing IRQ 9 with the USB controller, can you select another IRQ for the NIC in the BIOS? Especially if you can select a non-shared one? Darren, Forgot about the /dev/null idea. interesting result. I scp'd a 10 Mb file from my gentoo box and it completed fast in a few seconds - speed 3.3 Mb/s. Not great but faster than the other experiences. I then did the same with a 2.5Gb file and it started off at 3.3 or 3.5 Mb/sec but tailed of continuously until by the time the transfer was 12% done the transfer speed was down to 50 kb/sec. Very strange. Something is not happy here. Does this info give you any clues? I'm more baffled than before! thanks Gary
Re: Writes to samba server very, very slow
Darren Tucker wrote: Gary Clemans-Gibbon wrote: Also I have just grabbed the stable branch from cvs and am running stable GENERIC and still doesn't fix it. Just a recap - the problem is not just samba writes to either of the data disks from the network via samba or scp are painfully slow. Reads from the box to the network are fast. Copying files from one disk to another one the server are fast. Taking the disks out of the equation entirely: does scp'ing a file to /dev/null run fast or slow? $ dmesg [...] uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 9 [...] dc0 at pci0 dev 9 function 0 "ADMtek AN983" rev 0x11: irq 9, address The NIC is sharing IRQ 9 with the USB controller, can you select another IRQ for the NIC in the BIOS? Especially if you can select a non-shared one? Good suggestion Darren, I thought you might have hit upon it there. I remember a problem from way back when a promise raid controller card was fussy about which pci slot it was in. Anyway I tried moving the NIC to another slot and also manually set the irq in the bios to 12. Neither made any difference though # dmesg | grep irq uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 9 dc0 at pci0 dev 10 function 0 "ADMtek AN983" rev 0x11: irq 12, address 00:50:bf:9c:62:e4 pckbc0: using irq 1 for kbd slot lpt0 at isa0 port 0x378/4 irq 7 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 sb1 at isapnp0 "Creative SB AWE64 PnP, CTL0042, , Audio" port 0x220/16,0x330/2,0x388/4 irq 5 drq 1,5: dsp v4.16 wdc2 at isapnp0 "Creative SB AWE64 PnP, CTL2011, PNP0600, IDE" port 0x168/8,0x36e/2 irq 10
Re: Writes to samba server very, very slow
John Brooks wrote: How about a nic from a different mfr? Using another good 'dc' nic doesn't rule out a basic hardware incompatibility related directly to that brand of nic card coupled with your other hardware. JB . Even though it worked fine with RH7.3 a three + year old OS ? I've seen specific nic cards conflict with switches, hubs, and routers. Mix in some driver code that may do things a little different from one OS to another... By your response I take it you did swap out with the same brand of nic. Might be worth a try, what else has worked? . I've tried two different makes of NIC as can be seen from the two different dmesg listings I've posted in two seperate messages... The first was an SMC 1244TX and the second (and currently installed is a NIC that I have bought in the past in bulk and have proven very reliable with bsd, linux and windows, Encore ENL832-TX+ based on the RTL8139 chip. This NIC as far as I know is as generic as anything and I've used dozens of them in the past in all kinds of systems without a hitch. It is also listed on the Hardware compatability list. http://www.openbsd.org/i386.html#hardware Gary
Re: Writes to samba server very, very slow
Don Koch wrote: [EMAIL PROTECTED] said: I heeded your words of wisdom and after some rummaging I found a crossover cable. Hooked it up the same winXP box direct and the exact same result. Sounds like a bad nic. If you have a spare, you might try swapping with it. Also, what's the other machine and what is it running? The NIC is fine, and yes I swapped it out early on as well as the cable and the port on the switch. I've also tried a crossover cable. I've also tried all the different media options in ifconfig as given by ifconfig -m dc0. This is a basic install with only samba installed. Nothing could be simpler. Gary
Re: Writes to samba server very, very slow
Tim Hammerquist wrote: Gary Clemans-Gibbon wrote: Yes, I've tried different cables and different ports on the switch. This hardware has all been used before together. I cycled the power to the switch (can't find a reset button) and no change. Via samba or SCP it takes 7 minutes to write a file to the server and 12 seconds to read the same file. Tried an xover cable directly between the nodes? Tim . Tim, Just tried one. No difference. Also I am now running GENERIC stable. Still no change. Gary
Re: Writes to samba server very, very slow
Avtar Gill wrote:
Stephen Marley wrote:
Have you tried a crossover cable, bypassing the switch?
Words of wisdom right there. I would definitely try a crossover cable
between the OpenBSD server and your client machine. That will show you
whether the problem lies with Samba or elsewhere. I remember
experiencing problems like yours years ago (no Samba though) and
specifying half-duplex resolved the issue.
Thanks Stephen.
I heeded your words of wisdom and after some rummaging I found a
crossover cable. Hooked it up the same winXP box direct and the exact
same result.
Also I have just grabbed the stable branch from cvs and am running
stable GENERIC and still doesn't fix it. Just a recap - the problem is
not just samba writes to either of the data disks from the network via
samba or scp are painfully slow. Reads from the box to the network are
fast. Copying files from one disk to another one the server are fast.
thanks
Gary
$ dmesg
OpenBSD 3.7-stable (GENERIC) #0: Tue Jul 19 17:45:55 PDT 2005
[EMAIL PROTECTED]:/home/krusadr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 501 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115576832 (112868K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @ 0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Nvidia Riva TNT" rev 0x04
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 4 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wire
d to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 1032MB, 2114180 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
wd2 at pciide0 channel 1 drive 0:
wd2: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <, 52X24X52 CD-RW, 1.07> SCSI0 5/cdrom
removable
wd2(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x02 at pci0 dev 4 function 3 not configured
dc0 at pci0 dev 9 function 0 "ADMtek AN983" rev 0x11: irq 9, address
00:50:bf:9c:62:e4
ukphy0 at dc0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000749, model 0x0001, rev. 1
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 (mux 1 ignored for console): console keyboard, using
wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
lm0 at isa0 port 0x290/8: W83781D
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
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
isapnp0 at isa0 port 0x279: read port 0x203
sb1 at isapnp0 "Creative SB AWE64 PnP, CTL0042, , Audio" port
0x220/16,0x330/2,0x388/4 irq 5 drq 1,5: dsp v4.16
midi1 at sb1:
audio0 at sb1
opl0 at sb1: model OPL3
midi2 at opl0:
joy0 at isapnp0 "Creative SB AWE64 PnP, CTL7002, PNPB02F, Game" port 0x200/8
"Creative SB AWE64 PnP, CTL0022, , WaveTable" at isapnp0 port 0x620/4
not configured
wdc2 at isapnp0 "Creative SB AWE64 PnP, CTL2011, PNP0600, IDE" port
0x168/8,0x36e/2 irq 10
biomask ef45 netmask ef45 ttymask ffc7
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matched BIOS disk 80
dkcsum:
Re: Writes to samba server very, very slow
Stephen Marley wrote: On Tue, Jul 19, 2005 at 01:28:17PM -0700, Gary Clemans-Gibbon wrote: A little bit more info, i ran the following... . $ ifconfig -m dc0 dc0: flags=8843 mtu 1500 address: 00:50:bf:9c:62:e4 media: Ethernet autoselect (100baseTX full-duplex) status: active supported media: media none media 10baseT media 10baseT mediaopt full-duplex media 100baseTX media 100baseTX mediaopt full-duplex media autoselect inet 192.168.20.3 netmask 0xff00 broadcast 192.168.20.255 inet6 fe80::250:bfff:fe9c:62e4%dc0 prefixlen 64 scopeid 0x1 $ ifconfig dc0 media 100baseTX mediaopt full-duplex ifconfig: SIOCSIFMEDIA: Operation not permitted $ su Password: salyut# ksh # ifconfig dc0 media 100baseTX mediaopt full-duplex # ifconfig dc0 media 100baseTX # ifconfig dc0 media 10baseT # ifconfig dc0 media 100baseTX mediaopt full-duplex # ifconfig dc0 media 10baseT mediaopt full-duplex It speeded up for the 10baseT setting. I ran through the rest of the settings and now it seems hosed. I think I have thouroughly confused my switch now. Obviously it goes without saying that I want it to work at 100 not 10 but now it is really not working at all, like 30 minutes to copy a 5 Mb file in either direction! Not good :( Reset your switch. Try 100baseTX half-duplex. If autonegiotion is broken, and the switch is not manageable (to turn off autoneg), this may be the best you can do. Also, this may be obvious, but have you tried different cables? Yes, I've tried different cables and different ports on the switch. This hardware has all been used before together. I cycled the power to the switch (can't find a reset button) and no change. Via samba or SCP it takes 7 minutes to write a file to the server and 12 seconds to read the same file. thanks
Re: Writes to samba server very, very slow
Garance A Drosihn wrote: At 11:15 PM -0700 7/18/05, Gary Clemans-Gibbon wrote: Thanks David, I just tried that line but it seems to be the same or if anything it seems even slower. I missed the start of this thread, but make sure that you do not have a duplex-mismatch with your ethernet cards. You want to be sure your server and your client(s) have the same duplex setting as whatever they are connected to (usually some switch). At one point we had excruciating performance problems with our samba server, and eventually this turned out to be a duplex mismatch between the server and the switch it was connected to. The switch was set to 100-Mb-full/duplex (which is to say, it was *not* doing autonegotiation), and the network interface on the server was set to autonegotiate. The server ended up with the wrong answer for duplex... Garance, Thanks for that. I am experiencing similar slow write speeds when I transfer uusing SCP as well so it's not samba. Copying a file from one HDD to the other on the samba box results in a fast write. It looks like communication. I've tried two NICs. The box is hooked to a 16 port switch which works fine. I don't know how to check the autonegotiation. $ ifconfig -a lo0: flags=8049 mtu 33224 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 dc0: flags=8843 mtu 1500 address: 00:50:bf:9c:62:e4 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.20.3 netmask 0xff00 broadcast 192.168.20.255 inet6 fe80::250:bfff:fe9c:62e4%dc0 prefixlen 64 scopeid 0x1 pflog0: flags=0<> mtu 33224 pfsync0: flags=0<> mtu 2020 enc0: flags=0<> mtu 1536 Is there someway I can try different manual settings with the NIC. I guess it is an ifconfig command. I'm off to google now. If you have any suggestion I'd be grateful. thanks Gary
Re: Writes to samba server very, very slow
Thanks for your reply Tim. If anything it makes me feel worse. I was hoping it was something easily fixed. I just tried transferring a 50 Mb file to the OBSD samba box from win using SCP. Again very slow writes but much faster reads. The 50 Mb file took about 7 mins to transfer to the OBSD box and about 30 seconds to read from the OBSD box. Perhaps this isn't a samba smb issue at all. My fstab... # cat /etc/fstab /dev/wd0a / ffs rw 1 1 /dev/wd1a /data1 ffs rw 1 2 /dev/wd2a /data2 ffs rw 1 2 same result with either data disk. I've been googling all evening and found many many forum posts with similar problems but no solutions. Some posts date back to 2002! If I have to go back to RH7.3 I'll be bummed. Especially as I spent ages setting up all my families accounts and softlinks for the data store. Waste of a day! Tim Hammerquist wrote: Gary Clemans-Gibbon wrote: David Gwynne wrote: Gary Clemans-Gibbon wrote: Everything is working fine except that when I copy files to the box from a Windows XP box the transfers are very slow, like 9 minutes for a 48 Mb file. Copying the same file back to the win box is quick - a couple of seconds as you'd expect. I would suggest looking at the socket options parameter in /etc/samba/ smb.conf. I have the following in my smb.conf and transfer speeds seem to perform a lot better now: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 I just tried that line but it seems to be the same or if anything it seems even slower. Gary, I've seen this same phenomenon when copying to from my OSX Powerbook and my fileserver (running both FreeBSD 5 and Gentoo Linux), with the OSX acting as samba client. The transfer speeds are not "slightly" slower, they are slower by orders of magnitude, with normally 20sec transfers taking 10-20 minutes. I watch the progress meter slowly incrementing at the rate of 32-64k/sec over a 100bTX link. Does this sound like your issue? In my setup, I had limited success merely unmounting and remounting the share; that worked maybe 50% of the time. Also, the rate seemed to be normal more often if I had a simultaneous ssh connection between the same two machines, even if the ssh connection were idle. I was not able to find any consistently effective solution. After googling many times over several months, finding nothing more than the same advice you got about TCP_NODELAY and the SO_*BUF settings (which did not affect performance in my case either), I finally gave up, switching to NFS and/or scp. For what it's worth, I haven't noticed this since I upgraded my powerbook to OSX 10.4, so it might have something to do with the client OS, network stack, or Samba version. I apologize for not having anything solid to recommend. But I wanted to let you know that this *has* happened to others; you're not imagining it. Tim Hammerquist .
Re: Writes to samba server very, very slow - more info
This is really puzzling me, please someone help me out. I've tried a couple of things. Firstly I swapped out the NIC for a different brand, no change. Writes god-awful slow, reads nice and zippy. I did some googling and tried some things. Here are the results of ifconfig -a netstat -in netstat -ss I don't know if the output from netstat -ss is normal or not there are duplicate packets, please let me know, $ ifconfig -a lo0: flags=8049 mtu 33224 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5 dc0: flags=8843 mtu 1500 address: 00:50:bf:9c:62:e4 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.20.3 netmask 0xff00 broadcast 192.168.20.255 inet6 fe80::250:bfff:fe9c:62e4%dc0 prefixlen 64 scopeid 0x1 pflog0: flags=0<> mtu 33224 pfsync0: flags=0<> mtu 2020 enc0: flags=0<> mtu 1536 $ netstat -in NameMtu Network Address Ipkts IerrsOpkts Oerrs Colls lo0 332240 00 0 0 lo0 33224 127/8 127.0.0.10 00 0 0 lo0 33224 ::1/128 ::1 0 00 0 0 lo0 33224 fe80::%lo0/ fe80::1%lo0 0 00 0 0 dc0 150000:50:bf:9c:62:e424956 040617 0 0 dc0 1500 192.168.20/ 192.168.20.3 24956 040617 0 0 dc0 1500 fe80::%dc0/ fe80::250:bfff:fe24956 040617 0 0 pflog0* 332240 00 0 0 pfsync0 2020 0 00 0 0 enc0* 1536 0 00 0 0 $ netstat -ss ip: 24911 total packets received 16 bad header checksums 186 with data size < data length 24709 packets for this host 40602 packets sent from this host icmp: igmp: ipencap: tcp: 40579 packets sent 38744 data packets (50822440 bytes) 1 data packet (251 bytes) retransmitted 3 fast retransmitted packets 1354 ack-only packets (6063 delayed) 480 window update packets 24660 packets received 21738 acks (for 50819474 bytes) 58 duplicate acks 7062 packets (3128272 bytes) received in-sequence 52 completely duplicate packets (74096 bytes) 46 packets with some duplicate data (41032 bytes duplicated) 296 out-of-order packets (428428 bytes) 35 discarded for bad checksums 2 connection accepts 2 connections established (including accepts) 1 connection closed (including 0 drops) 12500 segments updated rtt (of 12502 attempts) 1 retransmit timeout 14841 correct ACK header predictions 2478 correct data packet header predictions 7 PCB cache misses cwr by fastrecovery: 3 cwr by timeout: 1 2 SYN cache entries added 2 completed udp: 58 datagrams received 1 broadcast/multicast datagram dropped due to no socket 57 delivered 30 datagrams output 1 missed PCB cache esp: ah: etherip: ipcomp: carp: pfsync: ip6: 7 packets sent from this host Mbuf statistics: icmp6: Output packet histogram: multicast listener report: 6 neighbor solicitation: 1 Histogram of error messages to be generated: pim6: rip6: thanks Gary Gary Clemans-Gibbon wrote: Thanks David, I just tried that line but it seems to be the same or if anything it seems even slower. Gary David Gwynne wrote: I would suggest looking at the socket options parameter in /etc/samba/ smb.conf. I have the following in my smb.conf and transfer speeds seem to perform a lot better now: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 On 19/07/2005, at 2:03 PM, Gary Clemans-Gibbon wrote: Hi All, I just built a OpenBSD 3.7 samba file server for my home lan. It's a P3 500, 128mb RAM, with a 2 gig IDE HDD for the OS and two x Maxtor 200 GB IDE drives for data. Everything is working fine except that when I copy files to the box from a Windows XP box the transfers are very slow, like 9 minutes for a 48 Mb file. Copying the same file back to the win box is quick - a couple of seconds as you'd expect. Please forgive me if I don't provide all the needed info here or if I didn't run any obvious checks. Please indicate what info is needed and how to get it and I'll repost it. This same hardware was previously running RH7.3 with samba and worked fine. I've tried a different ethernet cable and a different port on my switch too. many thanks
Re: Writes to samba server very, very slow
Thanks David,
I just tried that line but it seems to be the same or if anything it
seems even slower.
Gary
David Gwynne wrote:
I would suggest looking at the socket options parameter in /etc/samba/
smb.conf. I have the following in my smb.conf and transfer speeds seem
to perform a lot better now:
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
On 19/07/2005, at 2:03 PM, Gary Clemans-Gibbon wrote:
Hi All,
I just built a OpenBSD 3.7 samba file server for my home lan. It's a P3
500, 128mb RAM, with a 2 gig IDE HDD for the OS and two x Maxtor 200
GB IDE drives for data.
Everything is working fine except that when I copy files to the box from
a Windows XP box the transfers are very slow, like 9 minutes for a 48 Mb
file. Copying the same file back to the win box is quick - a couple
of seconds as you'd expect.
Please forgive me if I don't provide all the needed info here or if I
didn't run any obvious checks. Please indicate what info is needed
and how to get it and I'll repost it.
This same hardware was previously running RH7.3 with samba and worked
fine. I've tried a different ethernet cable and a different port on
my switch too.
many thanks in advance,
Gary
Here is /etc/samba/smb.conf global section..
[global]
workgroup = myworkgroup
server string = My Samba Server
hosts allow = 192.168.20. 127.0.0.1
log file = /var/log/smbd.%m
security = user
socket options = TCP_NODELAY IPTOS_LOWDELAY
read raw = yes
write raw = yes
Here is dmesg
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache)
501 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER
,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115580928 (112872K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @
0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev
0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER
,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115580928 (112872K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @
0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev
0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Nvidia Riva TNT" rev 0x04
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 4 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 1032MB, 2114180 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
wd2 at pciide0 channel 1 drive 0:
wd2: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <, 52X24X52 CD-RW, 1.07> SCSI0 5/ cdrom
removable
wd2(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 4 function 2 "
Writes to samba server very, very slow
Hi All,
I just built a OpenBSD 3.7 samba file server for my home lan. It's a P3
500, 128mb RAM, with a 2 gig IDE HDD for the OS and two x Maxtor 200 GB
IDE drives for data.
Everything is working fine except that when I copy files to the box from
a Windows XP box the transfers are very slow, like 9 minutes for a 48 Mb
file. Copying the same file back to the win box is quick - a couple of
seconds as you'd expect.
Please forgive me if I don't provide all the needed info here or if I
didn't run any obvious checks. Please indicate what info is needed and
how to get it and I'll repost it.
This same hardware was previously running RH7.3 with samba and worked
fine. I've tried a different ethernet cable and a different port on my
switch too.
many thanks in advance,
Gary
Here is /etc/samba/smb.conf global section..
[global]
workgroup = myworkgroup
server string = My Samba Server
hosts allow = 192.168.20. 127.0.0.1
log file = /var/log/smbd.%m
security = user
socket options = TCP_NODELAY IPTOS_LOWDELAY
read raw = yes
write raw = yes
Here is dmesg
OpenBSD 3.7 (GENERIC) #50: Sun Mar 20 00:01:57 MST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class, 512KB L2 cache) 501 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115580928 (112872K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @ 0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,SER,MMX,FXSR,SSE
cpu0: disabling processor serial number
real mem = 133787648 (130652K)
avail mem = 115580928 (112872K)
using 1658 buffers containing 6791168 bytes (6632K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(06) BIOS, date 03/03/00, BIOS32 rev. 0 @ 0xf0520
apm0 at bios0: Power Management spec V1.2 (BIOS mgmt disabled)
apm0: APM power management enable: unrecognized device ID (9)
apm0: APM engage (device 1): power management disabled (1)
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xd92
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xf0d10/128 (6 entries)
pcibios0: PCI Interrupt Router at 000:04:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 "Nvidia Riva TNT" rev 0x04
wsdisplay0 at vga1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 4 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 4 function 1 "Intel 82371AB IDE" rev 0x01: DMA,
channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA, 1032MB, 2114180 sectors
wd1 at pciide0 channel 0 drive 1:
wd1: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
wd2 at pciide0 channel 1 drive 0:
wd2: 16-sector PIO, LBA48, 194481MB, 398297088 sectors
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <, 52X24X52 CD-RW, 1.07> SCSI0 5/cdrom
removable
wd2(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
uhci0 at pci0 dev 4 function 2 "Intel 82371AB USB" rev 0x01: irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
"Intel 82371AB Power Mgmt" rev 0x02 at pci0 dev 4 function 3 not configured
dc0 at pci0 dev 9 function 0 "ADMtek AN983" rev 0x11: irq 9, address
00:50:bf:fe:83:bc
ukphy0 at dc0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x000749, model 0x0001, rev. 1
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 (mux 1 igno
ccd or raidframe?
Jay Savage wrote: On 5/5/05, Ian Watts <[EMAIL PROTECTED]> wrote: On Thu, 5 May 2005, Niall O'Higgins wrote: On Thu, May 05, 2005 at 12:10:58PM -0700, Gary Clemans-Gibbon wrote: The only thing is that I run 2 HDDs in RAID1 mirror with RAIDFRAME and so my kernel is generic + pseudo-device raid (if I remember correctly - it was a while ago I last did this and I've lost my notes). For such a setup I recommend ditching RAIDFrame for ccd(4), which is in GENERIC and as such actively maintained. The way I see it: cheap, personal mirroring/striping setups, use ccd(4). Real RAID, use ami(4) or maybe one of those external box things. Except that Gary is using a mirror and ccd(4) claims to provide either concatenated or interleaved disks, not mirroring: "A ccd may be either serially concatenated or interleaved." and as such provides no tolerance for disk failures: "WARNINGS If just one (or more) of the disks in a ccd fails, the entire file system will be lost." I use RAIDframe and haven't used ccd, so I'm just going by what the man page says... -- Ian You must be looking on your 3.6 or earlier box. Take a look at the revised man page on line (and presumably 3.7): A ccd may be either serially concatenated, interleaved, or mirrored. To serially concatenate partitions, specify an interleave factor of 0. Mir- roring configurations require an even number of components. It still won't provide all of the configurations of RAID(4), but it'll do simple mirroring. --jay . Is ccd the recommended way to go now instead of raidframe for a simple two-disk raid1 mirror? I've had a touble-free experience with raidframe, is there any compelling reason to switch to ccd ?
Re: Will different CPU and RAM matter?
Niall O'Higgins wrote: On Thu, May 05, 2005 at 11:15:35AM -0700, Gary Clemans-Gibbon wrote: I have a co-located 3.4 web/mail box at a remote location with a P3 1.2Ghz and 1Gb RAM (on-board LAN and video). At home I have another copy of the exact same motherboard but with a Celeron 1.1Ghz and 512 Gb RAM. The question is, can I install 3.7 on the box at home and then simply take out the HDD and swap it into the co-lo server? Will it care that it was installed on a different CPU with less RAM? Thanks to GENERIC kernel, this kind of thing will often work even on a completely different motherboard/cpu. When I upgraded from an old Athlon XP to a new Athlon 64 my OpenBSD install didn't mind a bit. So, you really shouldn't have any issues. This just shows the advantages of GENERIC approach vs. loadable modules. . The only thing is that I run 2 HDDs in RAID1 mirror with RAIDFRAME and so my kernel is generic + pseudo-device raid (if I remember correctly - it was a while ago I last did this and I've lost my notes). Sorry I didn't mention that at first but I wasn't thinking about the kernel change. Will that make a difference do you think? Sorry to be such a newb! Thanks again for all the replies. Much appreciated.
Re: Will different CPU and RAM matter?
STeve Andre' wrote: On Thursday 05 May 2005 14:15, Gary Clemans-Gibbon wrote: Hi All, I have a co-located 3.4 web/mail box at a remote location with a P3 1.2Ghz and 1Gb RAM (on-board LAN and video). At home I have another copy of the exact same motherboard but with a Celeron 1.1Ghz and 512 Gb RAM. The question is, can I install 3.7 on the box at home and then simply take out the HDD and swap it into the co-lo server? Will it care that it was installed on a different CPU with less RAM? TIA. Um, if one motherboard is a p3 and the other is a celeron, they aren't the same. Close maybe, but not the same. Remember that when at some point in the future two "similar" motherboards do slightly different things to you. Anyway, unless there are odd disk geometry problems, you ought to be able to move the disk over to the new box. Keep in mind that if the network card differs you'll have to change /etc/hostname.?. You should be able to do this easily. Have a backup plan in case it doesn't go well. --STeve Andre' . Steve, Actually the two motherboards are 100% identical, bought on the same day together. As for backup plan, how does "quickly chuck the original disk back in" sound? thanks Gary
Will different CPU and RAM matter?
Hi All, I have a co-located 3.4 web/mail box at a remote location with a P3 1.2Ghz and 1Gb RAM (on-board LAN and video). At home I have another copy of the exact same motherboard but with a Celeron 1.1Ghz and 512 Gb RAM. The question is, can I install 3.7 on the box at home and then simply take out the HDD and swap it into the co-lo server? Will it care that it was installed on a different CPU with less RAM? TIA.
