libzfs: vmem.h missing
Hi, when I try to compile an actual 7 STABLE Im getting: ===> cddl/lib/libzfs (depend) rm -f .depend mkdep -f .depend -a-DZFS_NO_ACL -I/usr/src/cddl/lib/libzfs/../../../sbin/mount -I/usr/src/cddl/lib/libzfs/../../../cddl/lib/libumem -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris -I/usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/include -I/usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/lib/libumem -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/sys -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/head -I/usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libnvpair -I/usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libuutil/common -I/usr/src/cddl/lib/libzfs/../.. /../cddl/contrib/opensolaris/lib/libzfs/common -D_SOLARIS_C_SOURCE /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/deviceid.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/mnttab.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/mkdirp.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/zmount.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/fsshare.c /usr/src/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/zone.c /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs/zfs_namecheck.c /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_util.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_graph.c /usr/src/cddl/lib/libzfs/../../../cdd l/contrib/opensolaris/lib/libzfs/common/libzfs_mount.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_pool.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_changelist.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_config.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_import.c /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_status.c In file included from /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/zio.h:32, from /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/common/zfs/zfs_prop.c:50: /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h:64:18: error: vmem.h: No such file or directory In file included from /usr/src/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/spa.h:32, from /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c:44: /usr/src/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common/sys/zfs_context.h:64:18: error: vmem.h: No such file or directory . why is vmem.h missing? -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: host(1) problem with -6 option
mdh wrote: Howdy folks, I'm having a little trouble understanding a problem that the `host` command in RELENG_7_0 (very recent) is having. This is by and large my first time working with IPv6, which I've been meaning to learn for some time. First off, I've got my zone file configured to return a record for x1.mydomain and named isn't complaining. However, when I run `host -6 x1.mydomain`, host returns the following output: ([EMAIL PROTECTED]) [/etc/namedb]: host -6 x1.mydomain /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: internal_send: :::127.0.0.1#53: Invalid argument /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: internal_send: :::IP.IP.IP.8#53: Invalid argument /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: internal_send: :::127.0.0.1#53: Invalid argument /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1179: internal_send: :::IP.IP.IP.8#53: Invalid argument ;; connection timed out; no servers could be reached It's the way resolv.conf works. Consider this -- happy-idiot-talk:~:% cat /etc/resolv.conf domain infracaninophile.co.uk nameserver ::1 nameserver 127.0.0.1 Which is all fine and dandy when told to use IPv6: happy-idiot-talk:~:% host -6 h-i-t.infracaninophile.co.uk h-i-t.infracaninophile.co.uk is an alias for happy-idiot-talk.infracaninophile.co.uk. happy-idiot-talk.infracaninophile.co.uk has address 81.187.76.162 happy-idiot-talk.infracaninophile.co.uk has IPv6 address 2001:8b0:151:1:240:5ff:fea5:8db7 happy-idiot-talk.infracaninophile.co.uk mail is handled by 10 smtp.infracaninophile.co.uk. but goes tits-up when told to use IPv4: happy-idiot-talk:~:% host -4 h-i-t.infracaninophile.co.uk host: couldn't get address for '::1': address family not supported nameserver entries in resolv.conf are tried in the order given. Using the -4 or -6 switches to host(1) forces it to try each of the listed nameserver addresses by the stated protocol. It makes no sense at all to try and access an IPv6 address using IPv4 transport, and trying the converse: an IPv4 address via IPv6, will either fail or try and use IPv4-mapped addresses. You might think that the '-4' and '-6' flags to host(1) are pretty much useless in that case, but they work fine when you also tell host(1) the domain name of a nameserver to use[*]: happy-idiot-talk:~:% host -4 h-i-t.infracaninophile.co.uk localhost Using domain server: Name: localhost Address: 127.0.0.1#53 Aliases: h-i-t.infracaninophile.co.uk is an alias for happy-idiot-talk.infracaninophile.co.uk. happy-idiot-talk.infracaninophile.co.uk has address 81.187.76.162 happy-idiot-talk.infracaninophile.co.uk has IPv6 address 2001:8b0:151:1:240:5ff:fea5:8db7 happy-idiot-talk.infracaninophile.co.uk mail is handled by 10 smtp.infracaninophile.co.uk. happy-idiot-talk:~:% host -6 h-i-t.infracaninophile.co.uk localhost Using domain server: Name: localhost Address: ::1#53 Aliases: h-i-t.infracaninophile.co.uk is an alias for happy-idiot-talk.infracaninophile.co.uk. happy-idiot-talk.infracaninophile.co.uk has address 81.187.76.162 happy-idiot-talk.infracaninophile.co.uk has IPv6 address 2001:8b0:151:1:240:5ff:fea5:8db7 happy-idiot-talk.infracaninophile.co.uk mail is handled by 10 smtp.infracaninophile.co.uk. Arguably it is a bug for host(1) to give up on the first entry in /etc/resolv.conf when told to use a conflicting address type. However, that should be reported to ISC rather than the FreeBSD project. When allowed to determine the transport type automatically everything works as expected. Cheers, Matthew [*] but only if the domain name of the nameserver you want to query can be resolved by means that don't fall foul of the same IPv4 vs IPv6 problem. Which boils down to using other than the DNS -- eg. /etc/hosts -- to find the nameserver address. -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: php-cgi frozen with sbwait when SMP enable
You can try taking look to lighttpd status and fcgi processes status like this: server.modules += ( "mod_status" ) status.status-url = "/server-status" status.statistics-url = "/sstatus1" status.statistics-url gives info for each fastcgi like this: fastcgi.active-requests: 0 fastcgi.backend.backend1.0.connected: 12493970 fastcgi.backend.backend1.0.died: 0 fastcgi.backend.backend1.0.disabled: 0 fastcgi.backend.backend1.0.load: 0 fastcgi.backend.backend1.0.overloaded: 0 fastcgi.backend.backend1.load: 1 fastcgi.requests: 19479062 etc... read what each means on lighttpd site... pls tell what caused this, it'd be very interesting to me! cheers, valqk. Ken Chen wrote: > I capture something. > > Please check the PID 57776. It's CPU time never change since my previous > mail here. > > web4# ps alx | grep php-cgi | grep -v grep | grep sbwait > 65534 57776 47240 0 4 0 182328 84984 sbwait I ??2:02.12 > /usr/local/bin/php-cgi > 65534 57801 47240 0 4 0 182328 82408 sbwait I ??0:19.97 > /usr/local/bin/php-cgi > 65534 57809 47240 0 4 0 182328 84096 sbwait I ??1:12.03 > /usr/local/bin/php-cgi > 65534 57823 47240 0 4 0 182328 84492 sbwait I ??2:04.21 > /usr/local/bin/php-cgi > 65534 57833 47240 0 4 0 183352 83316 sbwait I ??0:28.62 > /usr/local/bin/php-cgi > 65534 57866 47240 0 4 0 182328 79952 sbwait I ??0:05.92 > /usr/local/bin/php-cgi > 65534 57870 47240 0 4 0 182328 83184 sbwait I ??0:56.83 > /usr/local/bin/php-cgi > 65534 57871 47240 0 4 0 182328 83388 sbwait I ??0:54.96 > /usr/local/bin/php-cgi > 65534 57891 47240 0 4 0 182328 84436 sbwait I ??1:58.32 > /usr/local/bin/php-cgi > 65534 57925 47240 0 4 0 182328 84380 sbwait I ??2:03.53 > /usr/local/bin/php-cgi > 65534 65944 47240 0 4 0 182328 84184 sbwait I ??0:39.97 > /usr/local/bin/php-cgi > 65534 65952 47240 0 4 0 182328 84408 sbwait I ??0:21.37 > /usr/local/bin/php-cgi > 65534 66007 47240 0 4 0 183352 90960 sbwait I ??1:16.81 > /usr/local/bin/php-cgi > 65534 66014 47240 5 4 0 182328 92748 sbwait S ??1:41.23 > /usr/local/bin/php-cgi > 65534 66038 47240 1 4 0 182328 91900 sbwait I ??1:38.04 > /usr/local/bin/php-cgi > 65534 66060 47240 0 4 0 182328 90048 sbwait I ??1:15.46 > /usr/local/bin/php-cgi > 65534 66078 47240 3 4 0 182328 92224 sbwait S ??1:39.66 > /usr/local/bin/php-cgi > web4# top -b > last pid: 70768; load averages: 1.62, 1.65, 1.43 up 4+15:56:06 > 22:53:48 > 85 processes: 1 running, 84 sleeping > > Mem: 492M Active, 1204M Inact, 218M Wired, 60M Cache, 112M Buf, 27M Free > Swap: 2019M Total, 20K Used, 2019M Free > > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND > 69544 nobody 1 80 203M 38500K nanslp 1 6:31 11.33% php > 47290 nobody 1 40 101M98M kqread 1 30:42 2.98% lighttpd > 66526 nobody 1 40 178M 92796K accept 1 1:40 1.12% php-cgi > 66077 nobody 1 40 178M 92512K accept 0 1:49 1.07% php-cgi > 65921 nobody 1 40 178M 92696K accept 0 1:43 0.98% php-cgi > 65968 nobody 1 40 178M 92484K accept 0 1:43 0.93% php-cgi > 66017 nobody 1 40 178M 92444K accept 0 1:50 0.88% php-cgi > 65979 nobody 1 40 178M 92676K accept 1 1:44 0.88% php-cgi > 66424 nobody 1 40 178M 92928K accept 1 1:36 0.88% php-cgi > 65938 nobody 1 40 178M 92336K accept 1 1:52 0.73% php-cgi > 65951 nobody 1 40 178M 92704K accept 0 1:48 0.73% php-cgi > 66016 nobody 1 40 178M 92232K accept 1 1:41 0.73% php-cgi > 65950 nobody 1 40 178M 93192K accept 0 1:51 0.68% php-cgi > 65999 nobody 1 40 178M 92940K accept 1 1:46 0.63% php-cgi > 66008 nobody 1 40 178M 93000K accept 1 1:46 0.63% php-cgi > 69286 nobody 1 40 178M 92208K accept 1 0:37 0.63% php-cgi > 47289 nobody 1 40 73400K 70640K kqread 1 12:02 0.59% lighttpd > 65980 nobody 1 40 178M 93156K accept 1 1:51 0.59% php-cgi > 2008/11/7 Ivan Voras <[EMAIL PROTECTED]> > > >> Ken Chen wrote: >> >>> Oh.. sorry, I forgot to provide the information of my environment. >>> >>> web4# php-cgi -v >>> PHP 5.2.6 (cgi-fcgi) (built: Nov 2 2008 11:16:30) >>> Copyright (c) 1997-2008 The PHP Group >>> Zend Engine v2.2.0, Copyright (c) 1998-2008 Zend Technologies >>> with XCache v1.2.2, Copyright (c) 2005-2007, by mOo >>> web4# /usr/local/lighttpd/sbin/lighttpd -v >>> lighttpd-1.4.19 - a light and fast webserver >>> Build-Date: Sep 1 2008 16:58:51 >>> web4# uname -a >>> FreeBSD web4..com 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #11: Mon Nov >>> >> 3 >> >>> 01:10:36 CST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WEB4 i386 >>> web4# ps alx | grep php-cgi | grep -v grep | grep sbwait >>> 65534 57776 47240 0
Re: libzfs: vmem.h missing
Oliver Lehmann wrote: > Hi, > > when I try to compile an actual 7 STABLE Im getting: > > why is vmem.h missing? My cvsupfile only contained src-sys... so vmem.h got probably removed, but zfs_context.h got not updated -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fifo log problem
In message <[EMAIL PROTECTED]>, Mike Tancsa writes: >I tried changing the config so that there is only the fifo log being >written to and disabled newsyslog so that syslogd is not getting a >HUP signal. The strange thing is that reading from it gives >different results?!? > >Sometimes doing >[ps0278]# fifolog_reader all.fifo | wc >>From0 Wed Dec 31 19:00:00 1969 >To 1225760679 Mon Nov 3 20:04:39 2008 >Read from 1d800 > 59 4133068 >0[ps0278]# > >and a exactly for 1min it will show the correct results > >0[ps0278]# fifolog_reader all.fifo | wc >>From0 Wed Dec 31 19:00:00 1969 >To 1225760538 Mon Nov 3 20:02:18 2008 >Read from 0 >10765 75995 556816 >0[ps0278]# I could fear that you have two fifologs running at the same time, possibly as a result of syslogd doing something strange on sighup... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Western Digital hard disks and ATA timeouts
Søren Schmidt wrote:
On 7Nov, 2008, at 20:12 , Peter Wemm wrote:
On Thu, Nov 6, 2008 at 11:17 PM, Jeremy Chadwick <[EMAIL PROTECTED]>
wrote:
[..]
As stated, FreeBSD's ATA command timeout is hard-set to 5 seconds, and
is not adjustable without editing the ATA code yourself and increasing
the value. The FreeNAS folks have made patches available to turn the
timeout value into a sysctl.
Soren and/or others, please increase this timeout value. Five seconds
has now been deemed too aggressive a default. And please consider
migrating the timeout value into a sysctl.
The 5 second timeout has been a problem for quite a while actually.
I've had a number of instances where I've had to increase it to 20 or
30 seconds when recovering from marginal drives. The longest
"successful" recovery attempt I've seen was 26 seconds, I believe on a
Maxtor drive a few years ago. ("successful" == the drive spent 26
seconds but eventually successfully read the sector). Even the IBM
death star drives could take much longer than 5 seconds to do a
recovery 5 years ago. 5 seconds has never been a good default.
I think the timeout should be increased to at least 30 seconds. My
windows box has a timeout that goes for several minutes.
If there is concern about FreeBSD appearing to hang, I could imagine
that a console warning message could be printed after 5 seconds. But
just say "drive has not yet responded". But give it more time.
In this day and age we're generally not playing games with udma33 vs
66, notched cables, poor CRC support etc. SATA seems to have
eliminated all that. Hmm, it might make sense to increase the timeout
on SATA connections to 2 or 3 minutes by default.
Actually I do have a patch around that logs the timeout on the console
after the normal timeout (5secs), then just goes on to wait for double
the timeout and log again etc etc, final timeout was IIRC 60 secs but
could be anything.
I have a disk which I am finally getting rid of that produces READ_DMA
and WRITE_DMA errors at a pretty high rate. I did enable the extra ATA
error reporting and it doesn't seem to indicate any sort of actual
errors, just extra long itmeouts.
At one time, I did change the system to extend the timeout, but I did
not see any real improvement at 30 seconds. I suspect that an even more
extended timeout would be necessary to solve the problem.
I am removing the disk this week. Does anyone want a disk that produces
DMA timeouts at a regular rate? Would it help actually solve this problem?
Please let me know if you want such a beast and I will ship it to you.
/Joe
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysctl debug.cpufreq.highest
Thank You mate. Works like a charm, why not merge it into STABLE and CURRENT branches? I assume that STABLE is currently frozen 'cause of the RELEASE process, but such a small (and tested as 'lowest') change should fit into RELEASE. Regards vermaden > I've rolled a patchset to do this for 7.0-RELEASE > (http://acm.poly.edu/~spawk/cpufreq/) if anyone's interested. > > -Boris > > vermaden wrote: > > Hi, > > > > Currently there is possibility to set lowest speed of > > cpu for scaling with cpufreq (debug.cpufreq.lowest), > > it would be good to include also a option to set the > > highest possible freq to use with cpufreq, some laptops > > get too hot and/or consume too much power when running > > on maximum power/speed of cpu. > > > > Regards > > vermaden -- Dzwon taniej na zagraniczne komorki! Sprawdz >> http://link.interia.pl/f1f6a ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
