Re: NFS and Rebooting problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dec 9 Will H. Backman contributed the following: If you want to do it properly, use fdisk -e wd1, disklabel -E wd1, and newfs /dev/rwd1a, in that order. Joachim Which is the short version of the New Disk FAQ: http://www.openbsd.org/faq/faq14.html#NewDisk Thanks to Will & Joachim. Apologizes for not replying to message sooner. Tried using fdisk, disklabel and newfs first. Everything fine on the disk, but problem still there. Next, shutdown & disconnected wd1 cable & power, removed it from fstab & exports & rebooted, just sharing exports on wd0, & tried copying files from xp box. No help, still rebooted. Pulled the old nic, Intel 82557, & tried a 3com905c. This time, it didn't reboot when I did the file copy, with quite large files, so I thought I had the problem solved. Connected wd1 & reset the nfs shares , did a large file copy & rebooted. So, I restored the following tweaks to sysctl.conf: net.inet.tcp.keepinittime=600 # root setting tunables for nfs reboot problem net.inet.tcp.keepidle=28800 # root setting tunables for nfs reboot problem net.inet.tcp.keepintvl=600 # root setting tunables for nfs reboot problem net.inet.tcp.recvspace=65536# root setting tunables for nfs reboot problem net.inet.tcp.sendspace=32768# root setting tunables for nfs reboot problem net.inet.udp.recvspace=83200# root setting tunables for nfs reboot problem net.bpf.bufsize=65536 # root setting tunables for nfs reboot problem So far, haven't rebooted again, copying large files. Here's wd1 info from fstab so everyone knows I wasn't lazy & really did the initial disk work to repair my first "newbie" job on it: /dev/wd1a on /data2 type ffs (local, nodev, nosuid) Thanks again for the help. If anyone sees something I've bunged up, please let me know, if you have the time. Denny White Please do not CC me. Already subscribed to OBSD mailing list. GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A iD8DBQFDnylky0Ty5RZE55oRAil9AKClYY07FxJpJh2fdui3eT+S29JtTACglxmM IDOlJBoQG1j8kT5eeKDMzHE= =sx7q -END PGP SIGNATURE-
Re: NFS and Rebooting problem
> If you want to do it properly, use fdisk -e wd1, disklabel -E wd1, and > newfs /dev/rwd1a, in that order. > > Joachim Which is the short version of the New Disk FAQ: http://www.openbsd.org/faq/faq14.html#NewDisk
Re: NFS and Rebooting problem
On Fri, Dec 09, 2005 at 10:42:18AM -0600, Denny White wrote: > > Today Joachim Schipper contributed the following: > > > On Wed, Dec 07, 2005 at 11:36:35AM -0600, Denny White wrote: > >> /dev/wd0a / ffs rw 1 1 > >> /dev/wd0h /data ffs rw,nodev,nosuid 1 2 > >> /dev/wd0f /home ffs rw,nodev,nosuid 1 2 > >> /dev/wd0g /tmp ffs rw,nodev,nosuid 1 2 > >> /dev/wd0e /usr ffs rw,nodev 1 2 > >> /dev/wd0d /var ffs rw,nodev,nosuid 1 2 > >> /dev/wd1c /mnt ffs rw,nodev,nosuid 1 2 > >> /dev/cd0c /mnt/cdrom cd9660 ro,nodev,nosuid,noauto 0 0 > >> /dev/fd0a /mnt/floppy msdos ro,nodev,nosuid,noauto 0 0 > >> /mnt/data2/swap /mnt/data2/swap swap sw 0 0 > > > > I am not certain your swap file is configured correctly - I'm not > > certain, I've never used it, but every swap I've ever seen had a mount > > point of 'none'. Then again, the mount point was simply not used at all > > on Linux - I've never toyed with it on OpenBSD. > > > > Additionally, you shouldn't mount any 'c' partitions, such as /dev/wd1c, > > unless you are *very*, *very* sure what you are doing. In which case you > > probably don't want to. ;-) > > > > I don't think either of this will help much, though. > > > > Joachim > > > I thought it was configured right, but maybe not, afterall. > Maybe I didn't understand how to add a 2nd disk properly > when I put in an extra hd for storage space. I dangerously > dedicated, I think it's called, the entire drive. I didn't > see any need to divide it up, at the time. Did the same thing > on a fbsd box (but it's scsi, not ide) & not having problems > there. I can remotely mount the shares from the xp box & copy > really large files to the fbsd box without any problems. Have > copied files as large as iso's there without complaint from > that system. As for mounting /dev/wd1c, I didn't see any other > way to mount it, nor would the system let me do it any other > way. So, if you or anyone else sees a mistake there, in the > way I've mounted it, please advise. When I get home from work > tonight, I'm going to use swapctl to stop using the extra file > swap I created on the 2nd disk, hash it out in fstab, & see if > that helps with the file copying problem. If that works, I might > try doing, what the obsd faq calls, a more permanent swap to that > disc using a vnode device (www.openbsd.org/faq/faq14#SwapFile) > instead of a file swap. Thanks for the reply & advice. > Denny White If you want to do it properly, use fdisk -e wd1, disklabel -E wd1, and newfs /dev/rwd1a, in that order. Joachim
Re: NFS and Rebooting problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today Joachim Schipper contributed the following: On Wed, Dec 07, 2005 at 11:36:35AM -0600, Denny White wrote: Today Otto Moerbeek contributed the following: On Wed, 7 Dec 2005, Denny White wrote: When I'd drag & drop files to copy from a windows xp box to an nfs share on the obsd box, the obsd system would reboot. I thought at first that it was either something conflicting from the xp box, or that I had a hardware problem on the obsd box. That had happened once with a bad simm, but I had replaced it & had had no further problems until now. Before running a time consuming memory test on the obsd box, I did some reading on obsd tunables, and am now able to copy a file over from the xp box without the system rebooting. Below is a list of the changes: net.inet.tcp.keepinittime=600 net.inet.tcp.keepidle=28800 net.inet.tcp.keepintvl=600 net.inet.tcp.recvspace=65536 net.inet.tcp.sendspace=32768 net.inet.udp.recvspace=83200 net.bpf.bufsize=65536 vfs.nfs.iothreads=4 What type of nfs mount are you using? v2 or v3; udp or tcp? Any info on the console the moment the machine reboots? What is the value of tyhe ddb.panic sysctl? Anything in the logs? -Otto Looks like v3, tcp. there was nothing on the screen when the box rebooted. Just goes blank & reboots. Looked through the logs & couldn't find anything, either. Running sysctl -a | grep ddb.panic returns `ddb.panic=1'. I'm a relative newbie, so I could be completely offbase, but this doesn't look good. Looks like maybe it could be a hardware problem. Maybe the settings I upped could are just taking some of the strain off the system. I read in the obsd faqs, concerning nfs, that nfs filesystems should be mounted with 0 0 on the end of the line in /etc/fstab so the computer doesn't try to fsck the nfs filesystem on boot. Here's what my /etc/fstab looks like & /etc/exports: /dev/wd0a / ffs rw 1 1 /dev/wd0h /data ffs rw,nodev,nosuid 1 2 /dev/wd0f /home ffs rw,nodev,nosuid 1 2 /dev/wd0g /tmp ffs rw,nodev,nosuid 1 2 /dev/wd0e /usr ffs rw,nodev 1 2 /dev/wd0d /var ffs rw,nodev,nosuid 1 2 /dev/wd1c /mnt ffs rw,nodev,nosuid 1 2 /dev/cd0c /mnt/cdrom cd9660 ro,nodev,nosuid,noauto 0 0 /dev/fd0a /mnt/floppy msdos ro,nodev,nosuid,noauto 0 0 /mnt/data2/swap /mnt/data2/swap swap sw 0 0 I am not certain your swap file is configured correctly - I'm not certain, I've never used it, but every swap I've ever seen had a mount point of 'none'. Then again, the mount point was simply not used at all on Linux - I've never toyed with it on OpenBSD. Additionally, you shouldn't mount any 'c' partitions, such as /dev/wd1c, unless you are *very*, *very* sure what you are doing. In which case you probably don't want to. ;-) I don't think either of this will help much, though. Joachim I thought it was configured right, but maybe not, afterall. Maybe I didn't understand how to add a 2nd disk properly when I put in an extra hd for storage space. I dangerously dedicated, I think it's called, the entire drive. I didn't see any need to divide it up, at the time. Did the same thing on a fbsd box (but it's scsi, not ide) & not having problems there. I can remotely mount the shares from the xp box & copy really large files to the fbsd box without any problems. Have copied files as large as iso's there without complaint from that system. As for mounting /dev/wd1c, I didn't see any other way to mount it, nor would the system let me do it any other way. So, if you or anyone else sees a mistake there, in the way I've mounted it, please advise. When I get home from work tonight, I'm going to use swapctl to stop using the extra file swap I created on the 2nd disk, hash it out in fstab, & see if that helps with the file copying problem. If that works, I might try doing, what the obsd faq calls, a more permanent swap to that disc using a vnode device (www.openbsd.org/faq/faq14#SwapFile) instead of a file swap. Thanks for the reply & advice. Denny White GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A iD8DBQFDmbP1y0Ty5RZE55oRAjqLAJ0RVwBaW4dMI528shk/jDNCmtF+MQCgrea5 uFTQnup2NuGllEHbtfb5fy0= =bMGL -END PGP SIGNATURE-
Re: NFS and Rebooting problem
On Wed, Dec 07, 2005 at 11:36:35AM -0600, Denny White wrote: > > Today Otto Moerbeek contributed the following: > > On Wed, 7 Dec 2005, Denny White wrote: > >> When I'd drag & drop files to copy from a windows xp box > >> to an nfs share on the obsd box, the obsd system would > >> reboot. I thought at first that it was either something > >> conflicting from the xp box, or that I had a hardware > >> problem on the obsd box. That had happened once with a > >> bad simm, but I had replaced it & had had no further > >> problems until now. Before running a time consuming > >> memory test on the obsd box, I did some reading on obsd > >> tunables, and am now able to copy a file over from the > >> xp box without the system rebooting. Below is a list of > >> the changes: > >> > >> net.inet.tcp.keepinittime=600 > >> net.inet.tcp.keepidle=28800 > >> net.inet.tcp.keepintvl=600 > >> net.inet.tcp.recvspace=65536 net.inet.tcp.sendspace=32768 > >> net.inet.udp.recvspace=83200 net.bpf.bufsize=65536 vfs.nfs.iothreads=4 > > > > What type of nfs mount are you using? v2 or v3; udp or tcp? > > > > Any info on the console the moment the machine reboots? What is the > > value of tyhe ddb.panic sysctl? Anything in the logs? > > > > -Otto > > > Looks like v3, tcp. there was nothing on the screen when the > box rebooted. Just goes blank & reboots. Looked through the > logs & couldn't find anything, either. Running sysctl -a | grep ddb.panic > returns `ddb.panic=1'. I'm a relative newbie, so I could be completely > offbase, but this doesn't look good. Looks like maybe it could be a > hardware problem. Maybe the settings I upped could are just taking some > of the strain off the system. I read in the obsd faqs, concerning nfs, > that nfs filesystems should be mounted with 0 0 on the end of the line > in /etc/fstab so the computer doesn't try to fsck the nfs filesystem on > boot. Here's what my /etc/fstab looks like & /etc/exports: > > /dev/wd0a / ffs rw 1 1 > /dev/wd0h /data ffs rw,nodev,nosuid 1 2 > /dev/wd0f /home ffs rw,nodev,nosuid 1 2 > /dev/wd0g /tmp ffs rw,nodev,nosuid 1 2 > /dev/wd0e /usr ffs rw,nodev 1 2 > /dev/wd0d /var ffs rw,nodev,nosuid 1 2 > /dev/wd1c /mnt ffs rw,nodev,nosuid 1 2 > /dev/cd0c /mnt/cdrom cd9660 ro,nodev,nosuid,noauto 0 0 > /dev/fd0a /mnt/floppy msdos ro,nodev,nosuid,noauto 0 0 > /mnt/data2/swap /mnt/data2/swap swap sw 0 0 I am not certain your swap file is configured correctly - I'm not certain, I've never used it, but every swap I've ever seen had a mount point of 'none'. Then again, the mount point was simply not used at all on Linux - I've never toyed with it on OpenBSD. Additionally, you shouldn't mount any 'c' partitions, such as /dev/wd1c, unless you are *very*, *very* sure what you are doing. In which case you probably don't want to. ;-) I don't think either of this will help much, though. Joachim
Re: NFS and Rebooting problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today Otto Moerbeek contributed the following:
On Wed, 7 Dec 2005, Denny White wrote:
I was hoping someone could shed some light with some good
links, sample configurations, etc., that might help me
with the following. Not looking for someone to "fix it"
for me or anything like that. Maybe the following will show
that I have tried reading, googling, experimenting, etc.,
before asking. I don't want to have any settings too high
to cause other problems, just to change what's neccessary.
When I'd drag & drop files to copy from a windows xp box
to an nfs share on the obsd box, the obsd system would
reboot. I thought at first that it was either something
conflicting from the xp box, or that I had a hardware
problem on the obsd box. That had happened once with a
bad simm, but I had replaced it & had had no further
problems until now. Before running a time consuming
memory test on the obsd box, I did some reading on obsd
tunables, and am now able to copy a file over from the
xp box without the system rebooting. Below is a list of
the changes:
net.inet.tcp.keepinittime=600
net.inet.tcp.keepidle=28800
net.inet.tcp.keepintvl=600
net.inet.tcp.recvspace=65536 net.inet.tcp.sendspace=32768
net.inet.udp.recvspace=83200 net.bpf.bufsize=65536 vfs.nfs.iothreads=4
What type of nfs mount are you using? v2 or v3; udp or tcp?
Any info on the console the moment the machine reboots? What is the
value of tyhe ddb.panic sysctl? Anything in the logs?
-Otto
Looks like v3, tcp. there was nothing on the screen when the
box rebooted. Just goes blank & reboots. Looked through the
logs & couldn't find anything, either. Running sysctl -a | grep ddb.panic
returns `ddb.panic=1'. I'm a relative newbie, so I could be completely
offbase, but this doesn't look good. Looks like maybe it could be a
hardware problem. Maybe the settings I upped could are just taking some
of the strain off the system. I read in the obsd faqs, concerning nfs,
that nfs filesystems should be mounted with 0 0 on the end of the line
in /etc/fstab so the computer doesn't try to fsck the nfs filesystem on
boot. Here's what my /etc/fstab looks like & /etc/exports:
/dev/wd0a / ffs rw 1 1
/dev/wd0h /data ffs rw,nodev,nosuid 1 2
/dev/wd0f /home ffs rw,nodev,nosuid 1 2
/dev/wd0g /tmp ffs rw,nodev,nosuid 1 2
/dev/wd0e /usr ffs rw,nodev 1 2
/dev/wd0d /var ffs rw,nodev,nosuid 1 2
/dev/wd1c /mnt ffs rw,nodev,nosuid 1 2
/dev/cd0c /mnt/cdrom cd9660 ro,nodev,nosuid,noauto 0 0
/dev/fd0a /mnt/floppy msdos ro,nodev,nosuid,noauto 0 0
/mnt/data2/swap /mnt/data2/swap swap sw 0 0
# $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
#
# NFS exports Database
# See exports(5) for more information. Be very careful: misconfiguration
# of this file can result in your filesystems being readable by the world.
#
/home -alldirs -maproot=0 192.168.1.100 192.168.1.101 192.168.1.103
/data -alldirs -maproot=0 192.168.1.100 192.168.1.101 192.168.1.103
/mnt -alldirs -maproot=0 192.168.1.100 192.168.1.101 192.168.1.103
I don't quite understand the faqs I read, I guess. I thought
all you had to do was put the right parameters into /etc/exports
and you were good to go. Not having any problems on the old
hp netserver running fbsd_5_4. Hope some of this helps. Hurried
gathering the info. Have head off for work shortly.
Denny White
Before the problem started occurring, I was using softupdates. I tried running
without them, thinking maybe that had some bearing on
the problem. Apparently it didn't. The only thing that helped was the
changes listed above. I read that if you increase the tcp.recvspace &
tcp.sendspace too high, you can cause a kernel panic when booting.
That hasn't happened so far, with the above values. Exactly how high
I can go without problems, I don't know. The obsd box is used for email
& learning, mostly. No high usage production server. The largest file
I've tried to copy to the nfs share since making the changes was about
26mb. No reboot this time. Before the changes, about the largest I could
copy without trouble was 2mb. Right now, I'm limited on memory. There's
only 256mb on the obsd box. That might be a problem, too, if I keep
increasing the above values. There is no problem with file sizes when
using scp across the network. Forgot to mention that I had tested it
too, by mounting an obsd nfs share over on a fbsd box & had tried to
copy a large file over, resulting in a reboot. That was when I figured
I had it narrowed down to hardware or an obsd settings problem, the
latter apparently being the case. Thanks for any answers & advice.
Below is output of uname -a & dmesg.
OpenBSD badboybox.cableone.net 3.8 GENERIC#0 i386
OpenBSD 3.8-stable (GENERIC) #0: Fri Dec 2 01:25:13 CST 2005
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 601 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 26795
Re: NFS and Rebooting problem
On Wed, 7 Dec 2005, Denny White wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> I was hoping someone could shed some light with some good
> links, sample configurations, etc., that might help me
> with the following. Not looking for someone to "fix it"
> for me or anything like that. Maybe the following will show
> that I have tried reading, googling, experimenting, etc.,
> before asking. I don't want to have any settings too high
> to cause other problems, just to change what's neccessary.
> When I'd drag & drop files to copy from a windows xp box
> to an nfs share on the obsd box, the obsd system would
> reboot. I thought at first that it was either something
> conflicting from the xp box, or that I had a hardware
> problem on the obsd box. That had happened once with a
> bad simm, but I had replaced it & had had no further
> problems until now. Before running a time consuming
> memory test on the obsd box, I did some reading on obsd
> tunables, and am now able to copy a file over from the
> xp box without the system rebooting. Below is a list of
> the changes:
>
> net.inet.tcp.keepinittime=600
> net.inet.tcp.keepidle=28800
> net.inet.tcp.keepintvl=600
> net.inet.tcp.recvspace=65536 net.inet.tcp.sendspace=32768
> net.inet.udp.recvspace=83200 net.bpf.bufsize=65536 vfs.nfs.iothreads=4
What type of nfs mount are you using? v2 or v3; udp or tcp?
Any info on the console the moment the machine reboots? What is the
value of tyhe ddb.panic sysctl? Anything in the logs?
-Otto
> Before the problem started occurring, I was using softupdates. I tried running
> without them, thinking maybe that had some bearing on
> the problem. Apparently it didn't. The only thing that helped was the
> changes listed above. I read that if you increase the tcp.recvspace &
> tcp.sendspace too high, you can cause a kernel panic when booting.
> That hasn't happened so far, with the above values. Exactly how high
> I can go without problems, I don't know. The obsd box is used for email
> & learning, mostly. No high usage production server. The largest file
> I've tried to copy to the nfs share since making the changes was about
> 26mb. No reboot this time. Before the changes, about the largest I could
> copy without trouble was 2mb. Right now, I'm limited on memory. There's
> only 256mb on the obsd box. That might be a problem, too, if I keep
> increasing the above values. There is no problem with file sizes when
> using scp across the network. Forgot to mention that I had tested it
> too, by mounting an obsd nfs share over on a fbsd box & had tried to
> copy a large file over, resulting in a reboot. That was when I figured
> I had it narrowed down to hardware or an obsd settings problem, the
> latter apparently being the case. Thanks for any answers & advice.
> Below is output of uname -a & dmesg.
>
> OpenBSD badboybox.cableone.net 3.8 GENERIC#0 i386
>
> OpenBSD 3.8-stable (GENERIC) #0: Fri Dec 2 01:25:13 CST 2005
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> cpu0: Intel Pentium III ("GenuineIntel" 686-class) 601 MHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
> real mem = 267952128 (261672K)
> avail mem = 237613056 (232044K)
> using 3296 buffers containing 13500416 bytes (13184K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(a7) BIOS, date 01/31/02, BIOS32 rev. 0 @ 0xfb4f0
> apm0 at bios0: Power Management spec V1.2
> apm0: AC on, battery charge unknown
> apm0: flags 70102 dobusy 1 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf/0xb970
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdd90/144 (7 entries)
> pcibios0: PCI Exclusive IRQs: 5 9 10 11
> pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C596A 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 "VIA VT82C691 PCI" rev 0xc4
> ppb0 at pci0 dev 1 function 0 "VIA VT82C598 AGP" rev 0x00
> pci1 at ppb0 bus 1
> pcib0 at pci0 dev 7 function 0 "VIA VT82C686 ISA" rev 0x22
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x10: ATA66, channel 0
> configured to compatibility, channel 1 configured to compatibility
> wd0 at pciide0 channel 0 drive 0:
> wd0: 16-sector PIO, LBA, 28629MB, 58633344 sectors
> wd1 at pciide0 channel 0 drive 1:
> wd1: 16-sector PIO, LBA, 38166MB, 78165360 sectors
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 4
> wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 4
> atapiscsi0 at pciide0 channel 1 drive 0
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: SCSI0 5/cdrom
> removable
> atapiscsi1 at pciide0 channel 1 drive 1
> scsibus1 at atapiscsi1: 2 targets
> cd1 at scsibus1 targ 0 lun 0: SCSI0 5/cdrom removable
> cd0(pciide0:1:0): using PIO mode 4, DMA mode 2
> cd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x10: i
