pf stalls connection when using route-to
Hi listers,
We recently found that when the traffic passes pf with route-to, the
connection stalls.
Turning off TSO solves the problem. Our pf.conf is very simple:
table privip const {10/8, 172.16/12, 192.168/16}
pass out quick route-to (em0 10.1.1.1) from privip to ! privip no state
And we have a tcpdump capture file. It shows that there's lots of
duplicate packets and
retransmissions while TSO is enabled. Our NIC is an Intel PRO/1000:
em0: Intel(R) PRO/1000 Network Connection 6.9.14 port 0x2000-0x201f
mem 0xdf20-0xdf21 irq 18 at device 0.0 on pci4
em0: Using MSI interrupt
em0: [FILTER]
Screenshot: http://cf.files.jnlin.org/with-tso.png
Any suggestion? I just turn off the TSO, but I think it is only a workaround.
Sincerely,
Jui-Nan
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pf stalls connection when using route-to
On Tue, Apr 13, 2010 at 11:19 PM, Jeremy Chadwick free...@jdc.parodius.com wrote: What FreeBSD version? uname -a output please. I have tried 7.2-R and 8.0-R. Both version stalls, too. 8.0-RELEASE: # uname -a FreeBSD bsd8 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #3: Wed Mar 3 17:15:52 CST 2010 r...@bsd8:/usr/obj/usr/src/sys/KERNEL amd64 We only added carp in kernel config for HA. # cat /etc/sysctl.conf # $FreeBSD: src/etc/sysctl.conf,v 1.8.34.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 debug.bootverbose=1 kern.ipc.maxsockbuf=2097152 kern.ipc.somaxconn=8192 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxprocperuid=65536 net.inet.tcp.delayed_ack=0 debug.bootverbose=1 kern.ipc.maxsockbuf=2097152 kern.ipc.somaxconn=8192 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxprocperuid=65536 net.inet.tcp.delayed_ack=0 net.inet.carp.preempt=1 net.inet.carp.arpbalance=1 kern.randompid=9 net.inet.flowtable.enable=0 # cat /boot/loader.conf # coretemp_load=YES geom_mirror_load=YES geom_stripe_load=YES if_em_load=YES kbdmux_load=YES random_load=YES ukdb_load=YES zfs_load=YES # kern.ipc.nmbclusters=0 kern.maxproc=65536 net.inet.tcp.reass.maxsegments=1600 7.2-RELEASE: # uname -a FreeBSD bsd7 7.2-RELEASE-p7 FreeBSD 7.2-RELEASE-p7 #0: Fri Feb 26 22:28:05 UTC 2010 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 # cat /etc/sysctl.conf debug.bootverbose=1 kern.ipc.maxsockbuf=2097152 kern.ipc.somaxconn=32768 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxprocperuid=65536 kern.randompid=9 net.inet.icmp.icmplim=65536 net.inet.ip.fastforwarding=1 net.inet.ip.portrange.first=4096 net.inet.tcp.delayed_ack=0 net.inet.tcp.fast_finwait2_recycle=1 net.inet.tcp.maxtcptw=65535 net.inet.tcp.msl=1500 net.inet.tcp.nolocaltimewait=1 vfs.lookup_shared=1 vfs.nfs.prime_access_cache=0 vm.pmap.shpgperproc=2000 # cat /boot/loader.conf # coretemp_load=YES geom_mirror_load=YES geom_stripe_load=YES kbdmux_load=YES random_load=YES ukdb_load=YES zfs_load=YES # kern.ipc.nmbclusters=0 kern.maxproc=65536 vfs.zfs.prefetch_disable=1 vm.kmem_size=1G vm.kmem_size_max=1G net.inet.tcp.reass.maxsegments=1600 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Different behavior of make(1) between command line argument and .MAKEFLAGS special target
Hi listers, Recently I found that there's different behavior of specifying -j1 in command line argument and special target .MAKEFLAGS. According to section SPECIAL TARGETS in manpage of make(1): .MAKEFLAGS This target provides a way to specify flags for make when the makefile is used. The flags are as if typed to the shell, though the -f option will have no effect. Flags (except for -f) and variable assignments specified as the source for this target are also appended to the .MAKEFLAGS internal variable. Please note the difference between this target and the .MAKEFLAGS internal variable: specifying an option or variable assignment as the source for this target will affect both the current makefile and all processes that make executes. The behavior should be same while specifying flags in Makefile and typed to the shell. But when I try to set -j in Makefile, the behavior is different. I have filed a PR and send a patch (http://www.freebsd.org/cgi/query-pr.cgi?pr=144388). Any suggestion is welcomed. Sincerely, Jui-Nan Eric Lin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: TCP packet out-of-order problem
Oops, we surely have kern.ipc.nmbclusters=0 in loader.conf, but I think that should not modify net.inet.tcp.reass.maxsegments to 0 since we wish unlimited nmbclusters but not zero TCP reassembly segments. On Tue, Jan 6, 2009 at 4:16 PM, Robert Watson rwat...@freebsd.org wrote: On Tue, 6 Jan 2009, Lin Jui-Nan Eric wrote: I thought that the system auto-tune improperly in this case. Hmm. Do you have a custom setting for kern.ipc.nmbclusters in loader.conf or sysctl.conf? What does kern.ipc.nmbclusters configure itself to on your system? Also, could you send me the output of uname -a on the system? Thanks, Robert N M Watson Computer Laboratory University of Cambridge On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson rwat...@freebsd.org wrote: On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: After running netstat -s -p tcp, we found that lots of packets are discarded due to memory problems. We googled for it, and found that sysctl oid net.inet.tcp.reass.maxsegments became 0, therefore packets never reassembled. Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that setting kern.ipc.nmbclusters=0 makes net.inet.tcp.reass.maxsegments=0. After setting net.inet.tcp.reass.maxsegments=1600 in /boot/loader.conf, the network works perfectly now. Was it set to 0 through a configuration error, or did the system auto-tune improperly? Robert N M Watson Computer Laboratory University of Cambridge Thank you all for the help! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: TCP packet out-of-order problem
Hi Robert, I thought that the system auto-tune improperly in this case. On Mon, Jan 5, 2009 at 9:13 PM, Robert Watson rwat...@freebsd.org wrote: On Fri, 2 Jan 2009, Lin Jui-Nan Eric wrote: After running netstat -s -p tcp, we found that lots of packets are discarded due to memory problems. We googled for it, and found that sysctl oid net.inet.tcp.reass.maxsegments became 0, therefore packets never reassembled. Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that setting kern.ipc.nmbclusters=0 makes net.inet.tcp.reass.maxsegments=0. After setting net.inet.tcp.reass.maxsegments=1600 in /boot/loader.conf, the network works perfectly now. Was it set to 0 through a configuration error, or did the system auto-tune improperly? Robert N M Watson Computer Laboratory University of Cambridge Thank you all for the help! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amd(8) cores dump when load high
Update: After we add -S flag to amd_flags in /etc/rc.conf, amd does not core dump. I think it is a workaround solution. Thank you all guys! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: TCP packet out-of-order problem
Dear All listers, After running netstat -s -p tcp, we found that lots of packets are discarded due to memory problems. We googled for it, and found that sysctl oid net.inet.tcp.reass.maxsegments became 0, therefore packets never reassembled. Then we checked our /boot/loader.conf and /etc/sysctl.conf, and found that setting kern.ipc.nmbclusters=0 makes net.inet.tcp.reass.maxsegments=0. After setting net.inet.tcp.reass.maxsegments=1600 in /boot/loader.conf, the network works perfectly now. Thank you all for the help! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: TCP packet out-of-order problem
Hello, Yes, it's 1 now. On Wed, Dec 31, 2008 at 6:49 PM, Václav Haisman v.hais...@sh.cvut.cz wrote: Lin Jui-Nan Eric wrote, On 30.12.2008 21:06: Dear listers, We recently found our new FreeBSD server (located in some foreign region) has poor network performance. After doing some tcpdump and iperf testing, we found that out-of-order TCP packets are not inserted into queue. This is an 100Mbps line, and TSO is disabled. % uname -a FreeBSD bsd 7.1-RC2 FreeBSD 7.1-RC2 #2: Wed Dec 31 03:12:39 CST 2008 r...@bsd:/usr/obj/usr/src/sys/KERNEL amd64 % iperf -c 10.1.1.250 Client connecting to office, TCP port 5001 TCP window size: 3.07 MByte (default) [ 4] local 10.1.1.210 port 61488 connected with 10.1.1.250 port 5001 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.2 sec 5.74 MBytes 4.74 Mbits/sec 03:47:21.146397 IP 10.1.1.210.54919 10.1.1.250.5001: . 159305:160753(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146409 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 160753 win 12568 nop,nop,timestamp 3216612488 555928950 03:47:21.146473 IP 10.1.1.210.54919 10.1.1.250.5001: . 160753:162201(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146485 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 162201 win 12568 nop,nop,timestamp 3216612489 555928950 03:47:21.146972 IP 10.1.1.210.54919 10.1.1.250.5001: . 163649:165097(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146983 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 162201 win 12573 nop,nop,timestamp 3216612489 555928950 03:47:21.146985 IP 10.1.1.210.54919 10.1.1.250.5001: . 162201:163649(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146996 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 163649 win 12568 nop,nop,timestamp 3216612489 555928950 03:47:21.146998 IP 10.1.1.210.54919 10.1.1.250.5001: . 165097:166545(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.147006 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 163649 win 12573 nop,nop,timestamp 3216612489 555928950 03:47:21.147009 IP 10.1.1.210.54919 10.1.1.250.5001: . 166545:167993(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.147017 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 163649 win 12573 nop,nop,timestamp 3216612489 555928950 03:47:21.147019 IP 10.1.1.210.54919 10.1.1.250.5001: . 167993:169441(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 * You can see ack 163649 repeating, but the packet is transmitted before 163649:165097. % cat /etc/sysctl.conf # $FreeBSD: src/etc/sysctl.conf,v 1.8 2003/03/13 18:43:50 mux Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 debug.bootverbose=1 kern.ipc.somaxconn=8192 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxprocperuid=65536 net.inet.ip.fastforwarding=1 net.inet.tcp.delayed_ack=0 vm.pmap.shpgperproc=2000 kern.ipc.maxsockbuf=8388608 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 Is our configuration wrong? Or it is an known bug? I have searched stable net list, but found no similar discussion. Thank you all in advance! Do you have net.inet.tcp.sack.enable=1? -- VH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
TCP packet out-of-order problem
Dear listers, We recently found our new FreeBSD server (located in some foreign region) has poor network performance. After doing some tcpdump and iperf testing, we found that out-of-order TCP packets are not inserted into queue. This is an 100Mbps line, and TSO is disabled. % uname -a FreeBSD bsd 7.1-RC2 FreeBSD 7.1-RC2 #2: Wed Dec 31 03:12:39 CST 2008 r...@bsd:/usr/obj/usr/src/sys/KERNEL amd64 % iperf -c 10.1.1.250 Client connecting to office, TCP port 5001 TCP window size: 3.07 MByte (default) [ 4] local 10.1.1.210 port 61488 connected with 10.1.1.250 port 5001 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.2 sec 5.74 MBytes 4.74 Mbits/sec 03:47:21.146397 IP 10.1.1.210.54919 10.1.1.250.5001: . 159305:160753(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146409 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 160753 win 12568 nop,nop,timestamp 3216612488 555928950 03:47:21.146473 IP 10.1.1.210.54919 10.1.1.250.5001: . 160753:162201(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146485 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 162201 win 12568 nop,nop,timestamp 3216612489 555928950 03:47:21.146972 IP 10.1.1.210.54919 10.1.1.250.5001: . 163649:165097(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146983 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 162201 win 12573 nop,nop,timestamp 3216612489 555928950 03:47:21.146985 IP 10.1.1.210.54919 10.1.1.250.5001: . 162201:163649(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.146996 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 163649 win 12568 nop,nop,timestamp 3216612489 555928950 03:47:21.146998 IP 10.1.1.210.54919 10.1.1.250.5001: . 165097:166545(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.147006 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 163649 win 12573 nop,nop,timestamp 3216612489 555928950 03:47:21.147009 IP 10.1.1.210.54919 10.1.1.250.5001: . 166545:167993(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 03:47:21.147017 IP 10.1.1.250.5001 10.1.1.210.54919: . ack 163649 win 12573 nop,nop,timestamp 3216612489 555928950 03:47:21.147019 IP 10.1.1.210.54919 10.1.1.250.5001: . 167993:169441(1448) ack 1 win 1040 nop,nop,timestamp 555928950 3216612488 * You can see ack 163649 repeating, but the packet is transmitted before 163649:165097. % cat /etc/sysctl.conf # $FreeBSD: src/etc/sysctl.conf,v 1.8 2003/03/13 18:43:50 mux Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # # Uncomment this to prevent users from seeing information about processes that # are being run under another UID. #security.bsd.see_other_uids=0 debug.bootverbose=1 kern.ipc.somaxconn=8192 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxprocperuid=65536 net.inet.ip.fastforwarding=1 net.inet.tcp.delayed_ack=0 vm.pmap.shpgperproc=2000 kern.ipc.maxsockbuf=8388608 net.inet.tcp.sendspace=3217968 net.inet.tcp.recvspace=3217968 Is our configuration wrong? Or it is an known bug? I have searched stable net list, but found no similar discussion. Thank you all in advance! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Process stuck in STOP state
Hi Gavin, I will compile my kernel with WITNESS and try again! On Mon, Dec 29, 2008 at 11:23 PM, Gavin Atkinson ga...@freebsd.org wrote: On Fri, 26 Dec 2008, Lin Jui-Nan Eric wrote: Hi, Full back-trace is located here: http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ Did you get anywhere with this? If not, and you are willing to recompile your kernel to include WITNESS, can you (in addition to the above output) get the output of show alllocks next time it happens? Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Process stuck in STOP state
Dear All, We have recompiled our kernel with WITNESS and generated another textdump: http://aqua.pixnet.tw/~jnlin/textdump/event3/1230/ On Tue, Dec 30, 2008 at 12:00 AM, Lin Jui-Nan Eric eric...@tamama.org wrote: Hi Gavin, I will compile my kernel with WITNESS and try again! On Mon, Dec 29, 2008 at 11:23 PM, Gavin Atkinson ga...@freebsd.org wrote: On Fri, 26 Dec 2008, Lin Jui-Nan Eric wrote: Hi, Full back-trace is located here: http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ Did you get anywhere with this? If not, and you are willing to recompile your kernel to include WITNESS, can you (in addition to the above output) get the output of show alllocks next time it happens? Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amd(8) cores dump when load high
Hi Danny, Can you tell us which patch did you apply? Thank you very much! On Sun, Dec 28, 2008 at 3:52 PM, Danny Braniss da...@cs.huji.ac.il wrote: I got Couldn't lock process pages in memory using mlockall() too: [...] On Sat, Dec 27, 2008 at 9:07 PM, Rong-en Fan gra...@gmail.com wrote: On Sat, Dec 27, 2008 at 7:03 PM, Danny Braniss da...@cs.huji.ac.il wrote: No, we do not running amd with -S. # ps auxww | grep amd root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 /usr/sbin/amd -p -k amd64 -x all /net amd.map well, I'm running 7.1-PRERELEASE, what does the amd logs show? [...] Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory ** Hmm.. interesting, I got this Dec 26 15:32:11 bsd2 amd[39723]: Couldn't lock process pages in memory using mlo ckall(): Resource temporarily unavailable w/ 7-STABLE around Sep 4. I don't put plock = no in amd.conf, so by default it's plock'ed. Regards, Rong-En Fan some more ingrediants: when running vanilla amd it also failes to lock pages: Couldn't lock process pages in memory using mlockall(): Resource temporarily unavailable while the amd I'm running, which includes the latest - non official - patches works fine. but, the main diff I see is: opteron ldd /usr/sbin/amd /usr/sbin/amd: libc.so.7 = /lib/libc.so.7 (0x80065a000) while opteron ldd /SBIN/amd /SBIN/amd: librt.so.1 = /usr/lib/librt.so.1 (0x800658000) librpcsvc.so.4 = /usr/lib/librpcsvc.so.4 (0x80075d000) libwrap.so.5 = /usr/lib/libwrap.so.5 (0x800866000) libc.so.7 = /lib/libc.so.7 (0x80096f000) danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amd(8) cores dump when load high
No, we do not running amd with -S. # ps auxww | grep amd root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 /usr/sbin/amd -p -k amd64 -x all /net amd.map On Sat, Dec 27, 2008 at 4:51 PM, Danny Braniss da...@cs.huji.ac.il wrote: Yes, we found that it crashes when swap is used. on an amd64 architecture, amd could not plock it's pages in memory, and would, under memory preasure be swapped out, and break. I just run some tests under 7.1-PRERELEASE, and - it seems that plock is working. - amd is not being swapped out. are you running with amd -S ? danny On Fri, Dec 26, 2008 at 6:02 PM, Rong-en Fan gra...@gmail.com wrote: On Tue, Dec 23, 2008 at 12:44 AM, Lin Jui-Nan Eric eric...@tamama.org wrote: Dear listers, We currently found that amd frequently cores dump while loading is high (about 4~5) after we upgrade world kernel from 7.0-RELEASE to 7.1-PRERELEASE. I have read -stable and svn log of 7-STABLE, but can not found a report or a solution. Did anyone have the same issue? Thank you very much. According to my previous experience, amd 6.1.5 crashes under low memory situations. Not necessary high load. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amd(8) cores dump when load high
I got Couldn't lock process pages in memory using mlockall() too: Dec 27 23:20:38 worker1 amd[90422]: switched to logfile syslog Dec 27 23:20:38 worker1 amd[90422]: AM-UTILS VERSION INFORMATION: Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1997-2006 Erez Zadok Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1990 Jan-Simon Pendry Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1990 Imperial College of Science, Technology Medicine Dec 27 23:20:38 worker1 amd[90422]: Copyright (c) 1990 The Regents of the University of California. Dec 27 23:20:38 worker1 amd[90422]: am-utils version 6.1.5 (build 701100). Dec 27 23:20:38 worker1 amd[90422]: Report bugs to https://bugzilla.am-utils.org/ or am-ut...@am-utils.org. Dec 27 23:20:38 worker1 amd[90422]: Configured by David O'Brien obr...@freebsd.org on date 4-December-2007 PST. Dec 27 23:20:38 worker1 amd[90422]: Built by r...@worker1 on date Sun Nov 30 00:20:03 CST 2008. Dec 27 23:20:38 worker1 amd[90422]: cpu=amd64 (little-endian), arch=amd64, karch=amd64. Dec 27 23:20:38 worker1 amd[90422]: full_os=freebsd7.1, os=freebsd7, osver=7.1, vendor=undermydesk, distro=The FreeBSD Project. Dec 27 23:20:38 worker1 amd[90422]: domain=unknown.domain, host=worker1, hostd=worker1.unknown.domain. Dec 27 23:20:38 worker1 amd[90422]: Map support for: root, passwd, union, nis, ndbm, file, exec, error. Dec 27 23:20:38 worker1 amd[90422]: AMFS: nfs, link, nfsx, nfsl, host, linkx, program, union, ufs, cdfs, Dec 27 23:20:38 worker1 amd[90422]: pcfs, auto, direct, toplvl, error, inherit. Dec 27 23:20:38 worker1 amd[90422]: FS: cd9660, nfs, nfs3, nullfs, msdosfs, ufs, unionfs. Dec 27 23:20:38 worker1 amd[90422]: Network: wire=10.1.1.0 (netnumber=10.1.1). Dec 27 23:20:38 worker1 amd[90422]: My ip addr is 127.0.0.1 Dec 27 23:20:38 worker1 amd[90423]: released controlling tty using setsid() Dec 27 23:20:38 worker1 amd[90423]: Couldn't lock process pages in memory using mlockall(): Resource temporarily unavailable Dec 27 23:20:38 worker1 amd[90423]: file server localhost, type local, state starts up Dec 27 23:20:38 worker1 amd[90423]: Trying mount of amd.map on /net fstype toplvl mount_type non-autofs Dec 27 23:20:38 worker1 amd[90423]: creating mountpoint directory '/net' Dec 27 23:20:38 worker1 amd[90424]: /net: disabling nfs congestion window Dec 27 23:20:38 worker1 amd[90423]: first time load of map amd.map succeeded Dec 27 23:20:38 worker1 amd[90423]: amd.map mounted fstype toplvl on /net Dec 27 23:20:38 worker1 amd[90423]: /net set to never timeout I don't have a amd.conf: worker1 [/] -jnlin- ls -al /etc/amd.conf ls: /etc/amd.conf: No such file or directory On Sat, Dec 27, 2008 at 9:07 PM, Rong-en Fan gra...@gmail.com wrote: On Sat, Dec 27, 2008 at 7:03 PM, Danny Braniss da...@cs.huji.ac.il wrote: No, we do not running amd with -S. # ps auxww | grep amd root 706 0.0 0.1 7660 5416 ?? Ss Wed05PM 4:48.12 /usr/sbin/amd -p -k amd64 -x all /net amd.map well, I'm running 7.1-PRERELEASE, what does the amd logs show? [...] Dec 27 10:37:01 sf-02 amd[857]: Locked process pages in memory ** Hmm.. interesting, I got this Dec 26 15:32:11 bsd2 amd[39723]: Couldn't lock process pages in memory using mlo ckall(): Resource temporarily unavailable w/ 7-STABLE around Sep 4. I don't put plock = no in amd.conf, so by default it's plock'ed. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: amd(8) cores dump when load high
Yes, we found that it crashes when swap is used. On Fri, Dec 26, 2008 at 6:02 PM, Rong-en Fan gra...@gmail.com wrote: On Tue, Dec 23, 2008 at 12:44 AM, Lin Jui-Nan Eric eric...@tamama.org wrote: Dear listers, We currently found that amd frequently cores dump while loading is high (about 4~5) after we upgrade world kernel from 7.0-RELEASE to 7.1-PRERELEASE. I have read -stable and svn log of 7-STABLE, but can not found a report or a solution. Did anyone have the same issue? Thank you very much. According to my previous experience, amd 6.1.5 crashes under low memory situations. Not necessary high load. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Process stuck in STOP state
Hi, We have done a textdump, located here: http://aqua.pixnet.tw/~jnlin/textdump/ Thank you! On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein alf...@freebsd.org wrote: * Lin Jui-Nan Eric eric...@tamama.org [081223 09:17] wrote: Dear listers, Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve them with apache 2.2 (worker MPM + php fastcgi mode). Sorry. we use -STABLE now. event# uname -a FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org It'd be good if you could get to ddb and do a show all or threads and get all threads backtrace to see what's happening. thank you, -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Process stuck in STOP state
Hi, No, NFS is not working (df hangs, and cd /nfs/vol hangs, too). we have run fstat and see some NFS file is opened. I will do a full back-trace while this happened again. (It happens very frequentlyabout 10 times/day now) On Fri, Dec 26, 2008 at 11:26 AM, Alfred Perlstein alf...@freebsd.org wrote: * Lin Jui-Nan Eric eric...@tamama.org [081225 02:44] wrote: Hi, We have done a textdump, located here: http://aqua.pixnet.tw/~jnlin/textdump/ Thank you! Is NFS working when this happens? Can you run lsof too? It would be really good to get a backtrace from all processes, there's a ddb command to do this. -Alfred On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein alf...@freebsd.org wrote: * Lin Jui-Nan Eric eric...@tamama.org [081223 09:17] wrote: Dear listers, Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve them with apache 2.2 (worker MPM + php fastcgi mode). Sorry. we use -STABLE now. event# uname -a FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org It'd be good if you could get to ddb and do a show all or threads and get all threads backtrace to see what's happening. thank you, -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Process stuck in STOP state
Hi, Full back-trace is located here: http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ On Fri, Dec 26, 2008 at 11:34 AM, Lin Jui-Nan Eric eric...@tamama.org wrote: Hi, No, NFS is not working (df hangs, and cd /nfs/vol hangs, too). we have run fstat and see some NFS file is opened. I will do a full back-trace while this happened again. (It happens very frequentlyabout 10 times/day now) On Fri, Dec 26, 2008 at 11:26 AM, Alfred Perlstein alf...@freebsd.org wrote: * Lin Jui-Nan Eric eric...@tamama.org [081225 02:44] wrote: Hi, We have done a textdump, located here: http://aqua.pixnet.tw/~jnlin/textdump/ Thank you! Is NFS working when this happens? Can you run lsof too? It would be really good to get a backtrace from all processes, there's a ddb command to do this. -Alfred On Wed, Dec 24, 2008 at 11:07 AM, Alfred Perlstein alf...@freebsd.org wrote: * Lin Jui-Nan Eric eric...@tamama.org [081223 09:17] wrote: Dear listers, Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve them with apache 2.2 (worker MPM + php fastcgi mode). Sorry. we use -STABLE now. event# uname -a FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org It'd be good if you could get to ddb and do a show all or threads and get all threads backtrace to see what's happening. thank you, -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- - Alfred Perlstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Process stuck in STOP state
Dear listers, Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve them with apache 2.2 (worker MPM + php fastcgi mode). At least one time a day the apache process is stuck in the STOP state and is unkillable. gdb won't attach to the process, either. Does anyone have any similar issue? I have found that may be because of libkse, but we use libthr now. Thank you all in advance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Process stuck in STOP state
Dear listers, Our FreeBSD Server uses NFS to access PHP files on NetApp, then serve them with apache 2.2 (worker MPM + php fastcgi mode). Sorry. we use -STABLE now. event# uname -a FreeBSD event 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Thu Dec 4 01:45:42 CST 2008 r...@event:/usr/obj/usr/src/sys/KERNEL amd64 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
amd(8) cores dump when load high
Dear listers, We currently found that amd frequently cores dump while loading is high (about 4~5) after we upgrade world kernel from 7.0-RELEASE to 7.1-PRERELEASE. I have read -stable and svn log of 7-STABLE, but can not found a report or a solution. Did anyone have the same issue? Thank you very much. # uname -a FreeBSD bsd1 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Fri Dec 19 22:44:22 CST 2008 r...@bsd1:/usr/obj/usr/src/sys/KERNEL amd64 # dmesg pid 51645 (amd), uid 0: exited on signal 11 (core dumped) pid 52077 (amd), uid 0: exited on signal 11 (core dumped) pid 52083 (amd), uid 0: exited on signal 11 (core dumped) pid 53876 (amd), uid 0: exited on signal 11 (core dumped) pid 56444 (amd), uid 0: exited on signal 11 (core dumped) # gdb `which amd` /amd.core GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd...(no debugging symbols found)... Core was generated by `amd'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00080053ef8c in _rtld_thread_init () from /libexec/ld-elf.so.1 (gdb) bt #0 0x00080053ef8c in _rtld_thread_init () from /libexec/ld-elf.so.1 #1 0x0008005321c5 in _rtld_thread_init () from /libexec/ld-elf.so.1 #2 0x000800535bdc in _rtld_thread_init () from /libexec/ld-elf.so.1 #3 0x000800529a98 in _rtld_error () from /libexec/ld-elf.so.1 #4 0x00080052be8e in dlsym () from /libexec/ld-elf.so.1 #5 0x00080052c1a1 in dlclose () from /libexec/ld-elf.so.1 #6 0x00080070fb34 in __cxa_finalize () from /lib/libc.so.7 #7 0x0008006c5f8f in exit () from /lib/libc.so.7 #8 0x0041537c in ?? () #9 0x00407a82 in ?? () #10 0x00407be3 in ?? () #11 0x00415282 in ?? () #12 0x0040af8f in ?? () #13 0x00410ccc in ?? () #14 0x00406919 in ?? () #15 0x0040460e in ?? () #16 0x00080054b000 in ?? () #17 0x in ?? () #18 0x in ?? () #19 0x0008 in ?? () #20 0x7fffee78 in ?? () #21 0x7fffee86 in ?? () #22 0x7fffee89 in ?? () #23 0x7fffee8c in ?? () #24 0x7fffee92 in ?? () #25 0x7fffee95 in ?? () #26 0x7fffee99 in ?? () #27 0x7fffee9e in ?? () #28 0x in ?? () #29 0x7fffeea6 in ?? () #30 0x7fffeeb1 in ?? () #31 0x7fffeebb in ?? () #32 0x7fffeecf in ?? () #33 0x7fffeeda in ?? () #34 0x7fffeee5 in ?? () #35 0x7fffeef2 in ?? () #36 0x7fffef00 in ?? () #37 0x7fffef0c in ?? () #38 0x7fffef63 in ?? () #39 0x7fffef70 in ?? () #40 0x7fffef93 in ?? () #41 0x7fffefa2 in ?? () #42 0x7fffefb1 in ?? () #43 0x in ?? () #44 0x0003 in ?? () #45 0x00400040 in ?? () #46 0x0004 in ?? () #47 0x0038 in ?? () #48 0x0005 in ?? () #49 0x0007 in ?? () #50 0x0006 in ?? () #51 0x1000 in ?? () #52 0x0008 in ?? () #53 0x in ?? () #54 0x0009 in ?? () #55 0x00404580 in ?? () #56 0x0007 in ?? () #57 0x000800525000 in ?? () #58 0x in ?? () #59 0x in ?? () #60 0x in ?? () #61 0x in ?? () #62 0x in ?? () #63 0x in ?? () #64 0x in ?? () #65 0x in ?? () #66 0x in ?? () #67 0x in ?? () #68 0x in ?? () #69 0x in ?? () #70 0x in ?? () #71 0x in ?? () #72 0x in ?? () #73 0x in ?? () #74 0x6962732f7273752f in ?? () #75 0x702d00646d612f6e in ?? () #76 0x36646d61006b2d00 in ?? () #77 0x6c6c6100782d0034 in ?? () #78 0x6d610074656e2f00 in ?? () #79 0x55530070616d2e64 in ?? () #80 0x303d4449475f4f44 in ?? () #81 0x6f723d5245535500 in ?? () #82 0x3d4c49414d00746f in ?? () #83 0x69616d2f7261762f in ?? () #84 0x4800746f6f722f6c in ?? () #85 0x6f6f722f3d454d4f in ?? () #86 0x555f4f4455530074 in ?? () #87 0x474f4c00303d4449 in ?? () #88 0x6f6f723d454d414e in ?? () #89 0x414e524553550074 in ?? () #90 0x00746f6f723d454d in ?? () #91 0x6e6f633d4d524554 in ?? () #92 0x4854415000353273 in ?? () #93 0x2f3a6e6962732f3d in ?? () #94 0x7273752f3a6e6962 in ?? () #95 0x752f3a6e6962732f in ?? () #96 0x2f3a6e69622f7273 in ?? () #97 0x656d61672f727375
Re: amd(8) cores dump when load high
Hi, We are running some daily report (php scripts), get data from remote mysql database. And we are running daily backup script, to copy local data to remote NFS Server at the same time. On Tue, Dec 23, 2008 at 12:52 AM, SDH Admin ad...@stardothosting.com wrote: #634 0x000e in ?? () What is running when the load is high? OR specifically what is the server doing that is generating the load? Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
NFS Performance Issue
Hi Listers, We recently found that the Performance of the NFS Client in FreeBSD is worse than that in Linux. Linux [/net/iscsi] -jnlin- sudo ls -al /net/iscsi/mysql/blog-2/var/pixblog_2/blogarticle.ibd -rw-rw 1 3306 3306 734003200 2008-11-27 00:13 /net/iscsi/mysql/blog-2/var/pixblog_2/blogarticle.ibd Linux [/net/iscsi] -jnlin- uname -a Linux proxy 2.6.22.6-Linux #1 Mon Sep 3 11:54:48 CST 2007 i686 GNU/Linux Linux [/net/iscsi] -jnlin- sudo rsync --progress /net/iscsi/mysql/blog-2/var/pixblog_2/blogarticle.ibd /tmp/ blogarticle.ibd 734003200 100% 15.16MB/s0:00:46 (xfer#1, to-check=0/1) FreeBSD [/net/iscsi] -jnlin- uname -a FreeBSD newphp 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #3: Tue Nov 25 15:55:33 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL i386 FreeBSD [/net/iscsi] -jnlin- sudo rsync --progress /net/iscsi/mysql/blog-2/var/pixblog_2/blogarticle.ibd /tmp/ blogarticle.ibd 734003200 100%5.66MB/s0:02:03 (xfer#1, to-check=0/1) It's about 1/3 of NFS client in Linux. We have tuned TCP recv/send buffer, and got no gain. The mount parameters are: (We use amd) rw,nfsv3,lockd,grpid,intr,soft,cache,nodev,resvport,timeo=10,retrans=3,async,rsize=1024,wsize=1024,noatime Does anyone has any suggestion to get the performance better? Thank you all! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Performance Issue
On Thu, Nov 27, 2008 at 2:29 AM, Claus Guttesen [EMAIL PROTECTED] wrote: We recently found that the Performance of the NFS Client in FreeBSD is worse than that in Linux. What OS is your nfs-server running? Our NFS server is NetApp. You can ommit read- and write-size using tcp-mounts. From 'man mount_nfs': -w Set the write data size to the specified value. Ditto the com- ments w.r.t. the -r option, but using the ``fragments dropped due to timeout'' value on the server instead of the client. Note that both the -r and -w options should only be used as a last ditch effort at improving performance when mounting servers that do not support TCP mounts. I have a solaris 9 nfs-server with vxfs and I used to mount using udp but then I ran into 'server not responding' and changed to tcp-nfs-mount instead. I just copied a 200 MB file to the nfs-server in 7.5 sec. which is 26.6 MB/s. I'm trying to mount without read- and write-size now. Thank you! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Max size of one swap slice
On Wed, Aug 6, 2008 at 12:46 AM, Chuck Swiger [EMAIL PROTECTED] wrote: It's hard to conceive of why you'd want to add so much swap space, anyway-- if you've got programs which actually need to deal with 10s of gigabytes worth of data, then they ought to maintain a smaller/reasonable-sized working set in RAM and do disk I/O as needed themselves rather than depend upon the VM pager, anyways. We are running varnish, and found that it is not stable while using mmap mode. We don't know whether if the problem is in the code of varnish or file system, but we found that if we run varnish using malloc mode with big swap, it became stable. Thank you all for the information, I'll try to look into the kernel code. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Max size of one swap slice
Hi All, Recently we found that we can only allocate 32GB for one swap slice. Does there is any sysctl oid or any kernel option to increase it? Why we have this restriction? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
TMPFS: File System is Full
Hi, I found when we exhaust memory, tmpfs will not be able to write anything into it and cannot mount it. I use ZFS and TMPFS at the same time. Florence# cd /usr/src make buildworld /dev/null Florence# uname -a FreeBSD Florence.tamama.org 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #5: Mon May 5 00:36:32 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL amd64 Florence# mount -t tmpfs -o rw,size=1024000 tmpfs /tmp/tmpfs mount: tmpfs : No space left on device first 5 lines of top: last pid: 26893; load averages: 1.50, 1.58, 1.48 up 12+01:43:49 05:40:51 146 processes: 2 running, 144 sleeping CPU states: % user, % nice, % system, % interrupt, % idle Mem: 406M Active, 574M Inact, 1775M Wired, 83M Cache, 214M Buf, 126M Free Swap: 1024M Total, 1024M Free I think there should be a lower bound size limit. Does TMPFS use kernel-space memory? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
TMPFS: File System is Full
Hi, I found when we exhaust memory, tmpfs will not be able to write anything into it and cannot mount it. I use ZFS and TMPFS at the same time. Florence# cd /usr/src make buildworld /dev/null Florence# uname -a FreeBSD Florence.tamama.org 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #5: Mon May 5 00:36:32 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KERNEL amd64 Florence# mount -t tmpfs -o rw,size=1024000 tmpfs /tmp/tmpfs mount: tmpfs : No space left on device first 5 lines of top: last pid: 26893; load averages: 1.50, 1.58, 1.48 up 12+01:43:49 05:40:51 146 processes: 2 running, 144 sleeping CPU states: % user, % nice, % system, % interrupt, % idle Mem: 406M Active, 574M Inact, 1775M Wired, 83M Cache, 214M Buf, 126M Free Swap: 1024M Total, 1024M Free I think there should be a lower bound size limit. Does TMPFS use kernel-space memory? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
TMPFS does not support unix socket file?
Hi, I am trying to replace my /tmp to TMPFS. Everything is fine, but I found that MySQL does not run. The error log shows that it cannot bind /tmp/mysql.sock. Does TMPFS support unix socket file? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: TMPFS does not support unix socket file?
On Mon, May 12, 2008 at 1:18 AM, pluknet [EMAIL PROTECTED] wrote: 2008/5/11 Lin Jui-Nan Eric [EMAIL PROTECTED]: Hi, I am trying to replace my /tmp to TMPFS. Everything is fine, but I found that MySQL does not run. The error log shows that it cannot bind /tmp/mysql.sock. Does TMPFS support unix socket file? I've just checked tmpfs with unix with simple test case on my stable and it works. maybe permissions issue? It's a permission issue! Thank you very much. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Lots of FIN_WAIT_1 TCP Connections and deadlock in zoneli state
Hi All, I am running squid as reverse proxy on FreeBSD 7.0-R amd64. After running for a while (~ 8 hours), the throughput degrades to very very low rate. I found the squid is in zoneli state and is already a bug report on http://www.freebsd.org/cgi/query-pr.cgi?pr=106317 But after more investigation, I found there are lots of TCP Connections in FIN_WAIT_1 and never close. # netstat -an | grep FIN_WAIT_1 | wc -l 823 # netstat -an | grep FIN_WAIT_1 | head tcp4 0273 192.168.1.1.8061.62.121.195.64739FIN_WAIT_1 tcp4 0 13448 192.168.1.1.80163.22.44.102.58775FIN_WAIT_1 tcp4 0 33304 192.168.1.1.80163.32.61.253.2273 FIN_WAIT_1 tcp4 0 48416 192.168.1.1.8024.78.35.230.61059 FIN_WAIT_1 tcp4 0 33580 192.168.1.1.80140.130.102.8.24673FIN_WAIT_1 tcp4 0 32009 192.168.1.1.80163.23.57.133.38863FIN_WAIT_1 tcp4 0 78112 192.168.1.1.80122.146.0.210.21639FIN_WAIT_1 tcp4 0 32046 192.168.1.1.80140.130.102.8.23723FIN_WAIT_1 tcp4 0 32120 192.168.1.1.80140.128.194.130.56875 FIN_WAIT_1 tcp4 0 33580 192.168.1.1.80163.21.235.230.33900 FIN_WAIT_1 Is there a timeout timer for the FIN_WAIT_1 state? Thank you for any suggestions! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing 6.1-R on Dell Powervault 745N
Dear, On 10/20/06, Søren Schmidt [EMAIL PROTECTED] wrote: Boot verbose and grap the output like you did earlier in this thread will do nicely. What I need are the lines from where the channels on the controller are probed for raw devices, that should reveal if we can se any HW at all.. The verbose boot output is in http://www.csie.nctu.edu.tw/~jnlin/dmesg.v.log With Best Regards, Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing 6.1-R on Dell Powervault 745N
Hi, On 10/20/06, Søren Schmidt [EMAIL PROTECTED] wrote: OK, I need the output from a verbose boot. That will tell if the disks are seen at all and just the attach phase is failing. I might have a few ideas depending on the outcome of that... There is no message about ad0 shown in the boot procedure. Neither there is no message about failed device. How do I get the output from verbose boot? with digital camera? Best Regards, Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing 6.1-R on Dell Powervault 745N
Hi, On 10/19/06, Søren Schmidt [EMAIL PROTECTED] wrote: Nothing else that that it should work. I dont own any HW that uses this chip so I cannot test it out. The current support was done for the ARM port IIRC so things might be different on other systems. At any rate you definitly should try out 6.2-beta-something as 6.1 is getting old I have tried world kernel built yesterday (10/19), but the OS still can not recognize the hard disk. The dmesg and result of pciconf -lv: http://www.cs.nctu.edu.tw/~jnlin/cc/dmesg.log http://www.cs.nctu.edu.tw/~jnlin/cc/pciconf.log Best Regards, Jui-Nan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing 6.1-R on Dell Powervault 745N
Dear All, We have a Dell Powervault 745N and want to install FreeBSD 6.1-R. But the installer complains that it can not find out any hard disk. Since the dmesg contains ata2~5, I think the controller is recognized by FreeBSD, but it cannot get the SATA drive. The dmesg and result of running pciconf -lv is in this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/103624 Any suggestions? With Best Regards, Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountd changed?
Hi, On 10/16/06, Erik Trulsson [EMAIL PROTECTED] wrote: I had the same problems, but only when trying to export directories from the root filesystem. Your patch below would not help. The following patch (very much inspired by the comment on line 1038 in mountd.c) makes things work for me: Index: mountd.c This patch works for me too. Thank you the nice guys! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
mountd changed?
Hi, I have a freebsd box (6-stable) which export its root slice to NFS. The exports file is: / -alldirs -maproot=root -network 10.0.0 -mask 255.255.255.0 After making world kernel today, the nfs client said that permission denied. But another freebsd box (making world kernel today, too) exports its /home slice, and the nfs client did complain about it. Therefore, I try to copy the mountd binary file from another stable (9/30) to the broken nfs server, and it works. Any suggestions? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountd changed?
Hi, If I revert to revision 1.81.2.4, it worked correctly. On 10/15/06, Rink Springer [EMAIL PROTECTED] wrote: Hi, Hmm, I recently changed something which might trigger this. Could you back out revision 1.81.2.5 of src/usr.sbin/mountd/mountd.c and let me know whether this fixed the problem? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountd changed?
On 10/15/06, Lin Jui-Nan Eric [EMAIL PROTECTED] wrote: Hi, But another freebsd box (making world kernel today, too) exports its /home slice, and the nfs client did complain about it. Sorry, should be did not complain. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mountd changed?
Hi, The filesystem isn't shown in a 'showmount -e'. Nothing relevant in my /var/log/messages. On 10/16/06, Rink Springer [EMAIL PROTECTED] wrote: On Sun, Oct 15, 2006 at 11:45:23PM +0800, Lin Jui-Nan Eric wrote: No, it does not work. Hmm, I am assuming that the filesystem isn't shown when you do a 'showmount -e' on the server, is this correct? Anything relevant in your /var/log/messages ? -- Rink P.W. Springer- http://rink.nu Patience is for those who cannot afford decent hardware.- Peter Koeleman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
