[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 Dimitry Andric d...@freebsd.org changed: What|Removed |Added Status|In Progress |Closed Resolution|--- |Unable to Reproduce --- Comment #8 from Dimitry Andric d...@freebsd.org --- (In reply to sasamotikomi from comment #6) Let's not mix different issues here. I'm quite convinced that your hardware is faulty. Please fix your hardware first, and it it still occurs, reopen the bug. -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
[Bug 198549] [build] FreeBSD -STABLE r280855 world fail to build.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198549 Dimitry Andric d...@freebsd.org changed: What|Removed |Added CC|sta...@freebsd.org | -- You are receiving this mail because: You are on the CC list for the bug. ___ 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
Jenkins build is back to normal : Build-UFS-image #1455
See https://jenkins.freebsd.org/job/Build-UFS-image/1455/changes ___ 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: hanging processes, nfs, automount
On Tue, 31 Mar 2015 10:24:05 +0200, Dominic Fandrey kamik...@bsdforen.de wrote: I don't know where to ask this, so I'm putting it out here. Introductions first: FreeBSD AprilRyan.norad 10.1-STABLE FreeBSD 10.1-STABLE #2 r280373: Mon Mar 23 17:43:09 CET 2015 root@AprilRyan.norad:/usr/obj/S403/amd64/usr/src/sys/S403 amd64 I have an nfs-share that I access via automount in /net/host/share. The following scenario: - cd /net/host/share inside tmux - Do stuff - S4 the laptop and take it to work the next morning - Resume and the tmux session hangs infinitely - Kill all shells belonging to the tmux session - tmux server process hangs in state rpcrec It's bad enough that there apparently is no path for NFS to fail and reanimate the shell that accesses the share. But the really bad problem is, that tmux in rpcrec state is not killable. I.e. not kill -9 able. And as long as that process is around any new tmux server I try to start just hangs. For this killable stuff there is the 'intr' mount option. See also the 'soft' mount option if you don't want NFS to wait indefinitely for a lost server. man mount_nfs describes this all. Regards, Ronald. My only recourse so far is a reboot. ___ 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[2]: ZFS out of swap space
After specifying Michelle Sullivan restore everything , now the system is
loaded .
At 10.1 LiveUSB I did zpool import but probably the tenth attempt, he has
executed , the same thing happened on the 11 branch. So I removed just in case
bad dataset - / var / db / mysql / billing,
After I did the export and rebooted in the hard disk. I am grateful to you
about .
Can you try if setting the sysctl variable vfs.zfs.free_max_blocks to
a limited number, like, 100,000, would make the pool import properly?
You may have run out of memory because of too much data being free'ed
in one transaction group?
This variable 9.3 and 10.1 do not see the branches . Most likely it was.
(I would recommend doing this after importing the pool read-only and
copy your data off, though).
Понедельник, 30 марта 2015, 11:19 -07:00 от Xin Li delp...@delphij.net:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/30/15 01:32, armonia wrote:
Yes, my mistake was probably that I have included data
deduplication to see how it works, but not turned it off at the
right time. In this case, the machine memory of 4 GB
async_destroy - too enabled.
That is the conclusion I have deduplication disabled.
Hrm, usually async_destroy should be enough to protect against this
situation.
Can you try if setting the sysctl variable vfs.zfs.free_max_blocks to
a limited number, like, 100,000, would make the pool import properly?
You may have run out of memory because of too much data being free'ed
in one transaction group?
(I would recommend doing this after importing the pool read-only and
copy your data off, though).
How to import a pool of read-only?
zpool import -o readonly poolname.
Thank you for your response.
zpool get all zroot NAME PROPERTY VALUE
SOURCE zroot size 230G
- zroot capacity 24%
- zroot altroot-
default zroot health ONLINE
- zroot guid 1229884058434432944
default zroot version-
default zroot bootfs zroot
local zroot delegation on
default zroot autoreplaceon
local zroot cachefile -
default zroot failmode wait
default zroot listsnapshots on
local zroot autoexpand off
default zroot dedupditto 0
default zroot dedupratio 1.02x
- zroot free 174G
- zroot allocated 56.1G
- zroot readonly off
- zroot commentZFS
local zroot expandsize 0
- zroot freeing0
default zroot feature@async_destroy enabled
local zroot feature@empty_bpobjactive
local zroot feature@lz4_compress active
local zroot feature@multi_vdev_crash_dump enabled
local zroot feature@spacemap_histogram active
local zroot feature@enabled_txgactive
local zroot feature@hole_birth active
local zroot feature@extensible_dataset enabled
local zroot feature@bookmarks enabled
local zroot feature@filesystem_limits enabled
local
???, 30 ? 2015, 0:36 -07:00 ?? Xin Li
delp...@delphij.net :
On 3/27/15 05:26, armonia wrote:
After importing I press ctrl + t and here's the conclusion:
load: 0.20 cmd: zpool 725 [tx-tx_sync_done_cv] 32.50r 0.00y
5.59s 0% 6432k
Have you ever enabled e.g. dedup on certain dataset(s) and have a
lot of files, and the pool don't have 'async destroy' feature
enabled? In that case the fastest way to recover, if this took too
long, would probably import the pool read-only and copy data to
another pool.
On -CURRENT you can use dtrace -qn 'zfs-dbgmsg{printf(%s\n,
stringof(arg0))}' to see more verbose information, they are not
always helpful but will give you better idea on what is going on
under the hood .
Cheers, ___
freebsd-stable@freebsd.org
/compose?To=freebsd%2dsta...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable To
unsubscribe, send any mail to
freebsd-stable-unsubscr...@freebsd.org
/compose?To=freebsd%2dstable%2dunsubscr...@freebsd.org
--
- --
Xin LI delp...@delphij.net https://www.delphij.net/
FreeBSD - The Power to Serve! Live free or die
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.1.2 (FreeBSD)
iQIcBAEBCgAGBQJVGZPKAAoJEJW2GBstM+nsPIAP/2aX5MItnX/LiLII+xKp/Hnx
9TZWUdpEqwOpIWovjiF7N+Vp9Uz8RCCHl5yzMbd5p/cvaP6h7oQZiJYzBDLVRx61
Rk3Uz7/SyycWPXlD6lhNYPZ9QrptgO6hhX5y4YHxOlibhe7NLCmZYNxBqNsqR0HW
FoseCRP2+ima4Qu5P4dVKDCnKwMdifP7qvrbOZcyYWIVThVBH14Rp7w9zfiiAN6v
AYSY9JLMYQGILfexORo/LG+kYI3gT2CIhYVNpfCsQLo5GNOucAZNYM5oO4aCt/BQ
hanging processes, nfs, automount
I don't know where to ask this, so I'm putting it out here. Introductions first: FreeBSD AprilRyan.norad 10.1-STABLE FreeBSD 10.1-STABLE #2 r280373: Mon Mar 23 17:43:09 CET 2015 root@AprilRyan.norad:/usr/obj/S403/amd64/usr/src/sys/S403 amd64 I have an nfs-share that I access via automount in /net/host/share. The following scenario: - cd /net/host/share inside tmux - Do stuff - S4 the laptop and take it to work the next morning - Resume and the tmux session hangs infinitely - Kill all shells belonging to the tmux session - tmux server process hangs in state rpcrec It's bad enough that there apparently is no path for NFS to fail and reanimate the shell that accesses the share. But the really bad problem is, that tmux in rpcrec state is not killable. I.e. not kill -9 able. And as long as that process is around any new tmux server I try to start just hangs. My only recourse so far is a reboot. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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
Trying to clone a ZFS drive, can't get ashift=12
I have an Oracle (nee Sun) X4-2 server with identical 300GB SAS drives. I did an MBR ZFS install from FreeBSD 10.1-RELEASE CD and have it updated to p6: $ uname -a FreeBSD foo 10.1-RELEASE-p6 FreeBSD 10.1-RELEASE-p6 #0: Tue Feb 24 19:00:21 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 $ freebsd-version 10.1-RELEASE-p6 The current ZFS setup is: $ zdb | grep ashift ashift: 12 ashift: 12 $ zpool status pool: bootpool state: ONLINE scan: resilvered 486M in 0h0m with 0 errors on Thu Mar 26 09:16:45 2015 config: NAMESTATE READ WRITE CKSUM bootpool ONLINE 0 0 0 diskid/DISK-001442CBEEKF%20%20%20%20%20%20%20%20KFHBEEKFs1a ONLINE 0 0 0 pool: zroot state: ONLINE scan: resilvered 200K in 0h0m with 0 errors on Wed Mar 25 10:51:36 2015 config: NAMESTATE READ WRITE CKSUM zroot ONLINE 0 0 0 diskid/DISK-001442CBEEKF%20%20%20%20%20%20%20%20KFHBEEKFs1d ONLINE 0 0 0 $ gpart show diskid/DISK-001442CBEEKF%20%20%20%20%20%20%20%20KFHBEEKF = 63 585937437 diskid/DISK-001442CBEEKF%20%20%20%20%20%20%20%20KFHBEEKF MBR (279G) 63 585937422 1 freebsd [active] (279G) 585937485 15 - free - (7.5K) $ gpart show diskid/DISK-001442CBEEKF%20%20%20%20%20%20%20%20KFHBEEKFs1 =0 585937422 diskid/DISK-001442CBEEKF%20%20%20%20%20%20%20%20KFHBEEKFs1 BSD (279G) 04194304 1 freebsd-zfs (2.0G) 41943048388608 2 freebsd-swap (4.0G) 12582912 573354510 4 freebsd-zfs (273G) [Why are the disk ids blank %20 filled?] Now I want to create another (sorta) matching setup, but this time want to use labels and 4G (instead of 2G) for bootpool. # gpart create -s MBR da1 # gpart add -t freebsd da1 # gpart create -s BSD da1s1 # gpart add -s 4G -t freebsd-zfs da1s1 # gpart add -s 4G -t freebsd-swap da1s1 # gpart add -t freebsd-zfs da1s1 # gpart show da1 = 63 585937437 da1 MBR (279G) 63 5859374221 freebsd (279G) 585937485 15 - free - (7.5K) # gpart show da1s1 =0 585937422 da1s1 BSD (279G) 08388608 1 freebsd-zfs (4.0G) 83886088388608 2 freebsd-swap (4.0G) 16777216 569160206 4 freebsd-zfs (271G) Except for da1s1a being 4G instead of 2G, everything matches the ZFS setup above. Make the labels. # glabel label boot0 da1s1a # glabel label swap0 da1s1b # glabel label root0 da1s1d Create the ZFS bootpool. # zpool create -o cachefile=/tmp/newpool.cache bootpoolNew label/boot0 # zdb -U /tmp/newpool.cache | grep ashift ashift: 9 The geometry matches, but ashift is 9 not 12. If I try to use 4K, the disk geometry doesn't match the original and ashift is still 9 instead of 12. # gpart create -s MBR da1 # gpart add -a 4k -t freebsd da1 # gpart create -s BSD da1s1 # gpart add -a 4k -s 4G -t freebsd-zfs da1s1 # gpart add -a 4k -s 4G -t freebsd-swap da1s1 # gpart add -a 4k -t freebsd-zfs da1s1 # gpart show da1 = 63 585937437 da1 MBR (279G) 63 63 - free - (32K) 126 5859373591 freebsd [active] (279G) 585937485 15 - free - (7.5K) # gpart show da1s1 =0 585937359 da1s1 BSD (279G) 0 2 - free - (1.0K) 28388608 1 freebsd-zfs (4.0G) 83886108388608 2 freebsd-swap (4.0G) 16777218 569160136 4 freebsd-zfs (271G) 585937354 5 - free - (2.5K) # zpool create -o cachefile=/tmp/newpool.cache bootpoolNew label/boot0 # zdb -U /tmp/newpool.cache | grep ashift ashift: 9 What gives? How do I get it to use 4k? -- DE ___ 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: [CFT] Call for testing pkg 1.5.0
On Mar 31, 2015, at 17:24, Sergei Vyshenski svysh.f...@gmail.com wrote: Instead, the following succeded: # cd /usr/ports/ports-mgmt/pkg-devel # make reinstall ... # pkg -v 1.4.99.16 That is expected. WITH_PKG=devel is a make(1) option that only affects ports (non-binary pkgs). -- Rui Paulo ___ 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
Build failed in Jenkins: FreeBSD_stable_9 #729
See https://jenkins.freebsd.org/job/FreeBSD_stable_9/729/changes Changes: [jhb] MFC 278760: Add two new counters for vnode life cycle events: - vfs.recycles counts the number of vnodes forcefully recycled to avoid exceeding kern.maxvnodes. - vfs.vnodes_created counts the number of vnodes created by successful calls to getnewvnode(). -- [...truncated 56568 lines...] cc -O2 -pipe -DGTAGS -DSYSV_CURSES -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/include -std=gnu99 -fstack-protector -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/ex/ex_cmd.c -o ex_cmd.o cc -O2 -pipe -DGTAGS -DSYSV_CURSES -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/include -std=gnu99 -fstack-protector -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/ex/ex_cscope.c -o ex_cscope.o cc -O2 -pipe -I. -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1 -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1/../arch/amd64 -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1/../common -std=gnu99 -fstack-protector -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1/../common/inittyp.c -o inittyp.o === usr.bin/yacc (all) cc -O2 -pipe -DHAVE_CONFIG_H -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xz/../../lib/liblzma -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xz/../../contrib/xz/src/common -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xz/../../contrib/xz/src/xz/list.c -o list.o cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/yacc/closure.c -o closure.o In file included from https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/ex/../common/options.h:101, from https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/ex/../common/common.h:82, from https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/ex/ex_cscope.c:35: https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/include/options_def.h:11:1: warning: O_DIRECTORY redefined In file included from https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/vi/../../contrib/nvi/ex/ex_cscope.c:26: https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/obj/builds/FreeBSD_stable_9/tmp/usr/include/fcntl.h:119:1: warning: this is the location of the previous definition sh https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1/makeman https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/obj/builds/FreeBSD_stable_9/tmp/usr/libexec/lint1 -m lint.7 cc -O2 -pipe -I. -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1 -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1/../arch/amd64 -Ihttps://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/xlint/lint1/../common -std=gnu99 -fstack-protector -Wno-pointer-sign -c cgram.c -o cgram.o cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/yacc/error.c -o error.o cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c https://jenkins.freebsd.org/job/FreeBSD_stable_9/ws/usr.bin/yacc/lalr.c -o
[CFT] Call for testing pkg 1.5.0
Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Here is what happened since pkg 1.4.0: - pkg has grown with an initial support for provides/requires: this is a naive version but good enough to at least make major upgrade of php safer as well as making pear/pecl maintenance saner (note that this will need modifications in the ports tree) - Lots of new regression tests has been added, which allows us not less break your systems an unexpected way (do not worry there are still rooms for breakage) - Initial support for OS X - Initial support for NetBSD/EdjeBSD - Update most of the bundled third party software has been updated to their latest version - Improve the messages reported by pkg (and probably make some other worse) - Properly support file flags - Implement argument support for custom keywords - Extend setting credential via plist to allow to set file flags - Make credential syntax via plist more flexible allow to only defines the first fields and not latest for example @(user,,) can now be written just @(user) - pkg updating now supports case insensitive matching - pkg create now support a verbose mode - Add an option to change the default on question, until now the default answer was No with that option set it would be Yes - lots of fixes to pkg audit -r - Global memory usage reduction and speed up - Improvements and cleanup on pkg alias - pkg annotate --show --all has been fixed - Make pkg.h C++ friendly - Lots of improvements in the solver - Lots of fixes on 32 bits platforms - Add support for: pkg create -M ./plop.ucl -p ./plop.plist - New pkg -r rootdir that will install in the given rootdir without chrooting - Export PKG_ROOTDIR to scripts allow to make them as portable as possible - Stop trying to remove all installed package with the argument of pkg delete is a local file - Be more explicit about why the solver it going to reinstall, remove or upgrade (when possible) - Plenty of bug fixes - Plenty of new bugs Please test and report as much bugs as you can! We could be very grateful if regressions tests could be provided along with the bug reports :) Plan is to release 1.5.0 as soon as possible Best regards, Bapt pgp9RSzgT2h8U.pgp Description: PGP signature
Re: [CFT] Call for testing pkg 1.5.0
On Tue, 2015-03-31 at 21:03 +0200, Baptiste Daroussin wrote: Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Hey Baptiste, Great work to you and all those involved in this project! I'm grateful to have such an awesome tool. For those of us who run our own package repos via Poudriere, what kinds of changes should we expect to make once pkg 1.5.0 is released? Do we need to do a full rebuild of our package repo? I'm also assuming that the upgrade path from 1.4.x to 1.5.0 will simply be as easy as running `pkg upgrade`, right? Thanks again for your hard work. Thanks, Shawn signature.asc Description: This is a digitally signed message part
Re: [CFT] Call for testing pkg 1.5.0
On Tue, Mar 31, 2015 at 03:19:15PM -0400, Shawn Webb wrote: On Tue, 2015-03-31 at 21:03 +0200, Baptiste Daroussin wrote: Hi all, We just released pkg 1.5.0 beta1 (in ports-mgmt/pkg-devel), Hey Baptiste, Great work to you and all those involved in this project! I'm grateful to have such an awesome tool. For those of us who run our own package repos via Poudriere, what kinds of changes should we expect to make once pkg 1.5.0 is released? Do we need to do a full rebuild of our package repo? I'm also assuming that the upgrade path from 1.4.x to 1.5.0 will simply be as easy as running `pkg upgrade`, right? Thanks again for your hard work. Add WITH_PKG=devel in your build make.conf then pkg upgrade will want you to upgrade to 1.4.99.16 (which is pkg 1.5.0 beta1) Best regards, Bapt pgpmXuAYEDP8s.pgp Description: PGP signature
Re: Build failed in Jenkins: FreeBSD_stable_9 #729
On Tuesday, March 31, 2015 05:02:04 PM jenkins-ad...@freebsd.org wrote: See https://jenkins.freebsd.org/job/FreeBSD_stable_9/729/changes Changes: [jhb] MFC 278760: Add two new counters for vnode life cycle events: - vfs.recycles counts the number of vnodes forcefully recycled to avoid exceeding kern.maxvnodes. - vfs.vnodes_created counts the number of vnodes created by successful calls to getnewvnode(). The actual error is unrelated (and also not in this really long e-mail). It appears to be: mv -f dtparserparse.h dtparser.y.h mv: rename dtparserparse.h to dtparser.y.h: No such file or directory *** [dtparser.y.h] Error code 1 I suspect this is some sort of race with -j? -- John Baldwin ___ 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
epair on 9-stable
Hi, Is epair (virtual ethernet) supposed to work on 9-stable? I'm having trouble with it. I want to connect one end to a bridge, e.g.: bge0 === bridge0 === epair0a --- epair0b and run dhclient on epair0b. But nothing comes through, not even on epair0a. bridge0 itself receives packets. No firewall involved. Any ideas? Johannes ___ 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: [CFT] Call for testing pkg 1.5.0
Hi, On Tue, Mar 31, 2015 at 9:23 PM, Baptiste Daroussin b...@freebsd.org wrote: Add WITH_PKG=devel in your build make.conf then pkg upgrade will want you to upgrade to 1.4.99.16 (which is pkg 1.5.0 beta1) This does not work for me. # cat /etc/make.conf |grep PKG WITH_PKGNG=yes WITH_PKG=devel # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking for upgrades (218 candidates): 100% Processing candidates (218 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. # pkg -v 1.4.12 # pkg info |grep pkg pkg-1.4.12 Package manager Instead, the following succeded: # cd /usr/ports/ports-mgmt/pkg-devel # make reinstall ... # pkg -v 1.4.99.16 All the best, Sergei ___ 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
