Swap on zvol - recommendable?
Hi, all, is it possible to make a definite statement about swap on zvols? I found some older discussions about a resource starvation scenario when ZFS arc would be the cause of the system running out of memory, trying to swap, yet the ZFS would not be accessible until some memory was freed - leading to a deadlock. Is this still the case with RELENG_8? The various Root on ZFS guides mention both choices (decicated or gmirror partition vs. zvol), yet don't say anything about the respective merits or risks. I am aware of the fact that I cannot dump to a raidz2 zvol ... Thanks for any hints, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 i...@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ 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
Schedule for 8.3-RELEASE...
Just a quick note to say the target schedule for 8.3-RELEASE has been set and is available here: http://www.freebsd.org/releases/8.3R/schedule.html The summary of the target dates is: Code Freeze:Feb 15, 2012 BETA1 builds: Feb 17, 2012 RC1 builds: Mar 2, 2012 RC2 builds: Mar 16, 2012 REL builds: Mar 23, 2012 The Security Officer has pushed back the estimated End of Life for 8.2-RELEASE to July 31, 2012. That will give three months between the release of 8.3-RELEASE and the EoL for 8.2-RELEASE. It is expected that 8.3-RELEASE will be an Extended Support release. See: http://www.freebsd.org/security/#sup for the full details of the currently supported releases. Thanks. -- Ken Smith - From there to here, from here to | kensm...@buffalo.edu there, funny things are everywhere. | - Theodor Geisel | signature.asc Description: This is a digitally signed message part
make buildworld fails with 8.2-RELEASE amd64 building STABLE
make buildworld fails when trying to make buildworld (no options) with 8.2-RELEASE with 8.2-STABLE sources as of 2/6/2012 updated at 9:15 AM from ftp.freebsd.org. The compile fails in the same spot every time; this is not a random failure. I have seen some evidence, however, that there may be hardware problems. The other hardware problem was a Broadcom GigE watchdog timeout and reset. Hardware is a Tyan S2885 (dual dual-core Opteron) which has been running Windows XP SP3 for some time without problems, for what that's worth. A Google search turns up nothing obviously related. Mike Squires mikes at siralan.org UN*X at home since 1986 uname -a: FreeBSD s2885.familysquires.net 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011 r...@amason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Error messages at failure: === gnu/usr.bin/gperf/doc (depend) c++ -O2 -pipe -I/usr/obj/usr/src/tmp/legacy/usr/include -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc: In destructor 'Bool_Array::~Bool_Array()': /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc:39: internal compiler error: Illegal instruction: 4 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop in /usr/src/gnu/usr.bin/gperf. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. s2885# ___ 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: serious packet routing issue causing ntpd high load?
Hi Qing, Any luck with this? Thanks Vlad On Thu, Nov 3, 2011 at 2:05 PM, Li, Qing qing...@bluecoat.com wrote: This endless route lookup miss message problem is reproducible without FLOWTABLE. The problem is with the multiple FIBs. I cannot reproduce this problem in my home network but the problem is easily seen at work. The route lookup miss itself in multi-FIBs configuration may be normal depending on the actual system configuration. It's the flooding of RTM_MISS messages that is abnormal. For example, if the route to the DNS servers is not configured in all FIBs, then the RTM_MISS message will be generated when an userland application sends to an explicit IP address in a specific FIB. In any case, I can reproduce the issue consistently and just trying to get a few uninterrupted hours to get it done. --Qing From: Alexander V. Chernikov [melif...@freebsd.org] Sent: Thursday, November 03, 2011 6:43 AM To: Steven Hartland Cc: Li, Qing; freebsd-stable@FreeBSD.org; li...@multiplay.co.uk Subject: Re: serious packet routing issue causing ntpd high load? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.10.2011 13:50, Steven Hartland wrote: - Original Message - From: Li, Qing qing...@bluecoat.com RTM_MISS: Lookup failed on this address: len 184, pid: 0, seq 0, errno 0, flags:DONE locks: inits: sockaddrs: DST ::A.B.C.D I'm unable to reproduce an issue on (nearly) GENERIC 8-S, but I see nearly the same situation on 8.1-S box with FLOWTABLE enabled. Do you have FLOWTABLE option in your kernel config ? Would it be possible for you to email me what exactly does ::A.B.C.D map into WRT your system or infrastructure ? Sorry for the slow reply been out of the country. All the hosts are local machines same /24 connecting to the server for mysql. It seems to be that every packet either to or from for the mysql server is generating an RTM_MISS. And are you able to share your ifconfig -a and netstat -rn output with me privately ? On its way. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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 - -- WBR, Alexander -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6ymoMACgkQwcJ4iSZ1q2meiACeKq4lhzw6scqCKzEyTNEeycxo 31QAn2q5KIRBwJpcF7yOpTe3wOcP3Aak =jfKN -END PGP SIGNATURE- ___ 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 -- Good, fast cheap. Pick any two. ___ 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
VOP_WRITE hex is not exclusive locked but should be
Hi. I have a server with an 8.2-RELEASE/amd64. It's primary use for routing/ipsec+gre tunneling. It's also running zfs. Sometimes it's locking up: it stops to respond to the network, but the console is still alive, though it doesn't log me in - the 'password:' prompt never comes up (I only can type my username or enter key). I've built a kernel with DEBUG_LOCKS/DEBUG_VFS_LOCKS, KDB/DDB, INVARIANTS, WITNESS and stuff. The only problem is that when booting such a new kernel and DEBUG_LOCKS/DEBUG_VFS_LOCKS are present, I get VOP_PUTPAGES: hex is not exclusive locked but should be and the kernel immidiately enters ddb. This happens on a daemons startup after the kernel is boot up and filesystems are mounted. Is this something that is safe to ignore (then how do I ignore that ? 'continue' only makes a new VOP_PUTPAGES message appear) ? Is it something that can lock up my server later on and should I report that ? I saw similar message (only it was about VOP_WRITE) in this maillist about 7-STABLE, someone said to try a memtest. I did one pass of a memtest (I know this isn't enough, but I cannot run it there for a day, and, furthermore, I got this message in subject immidiately on multiuser boot sequence so my guess is - the errors should appear immidiately too) and it didn't find any errors. Thanks. Eugene. ___ 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: FreeBSD 9: Group quotas increase but don't decrease automatically
On 2/3/2012 21:48, Konstantin Belousov wrote: This is a bug in +J code (even if you do not use +J). Do you have softupdates enabled on the volume ? If yes, try the following patch. diff --git a/sys/ufs/ffs/ffs_softdep.c b/sys/ufs/ffs/ffs_softdep.c index 5b4b6b9..ed2db79 100644 --- a/sys/ufs/ffs/ffs_softdep.c +++ b/sys/ufs/ffs/ffs_softdep.c @@ -43,6 +43,7 @@ __FBSDID($FreeBSD$); #include opt_ffs.h +#include opt_quota.h #include opt_ddb.h /* @@ -6428,7 +6429,7 @@ softdep_setup_freeblocks(ip, length, flags) } #ifdef QUOTA /* Reference the quotas in case the block count is wrong in the end. */ - quotaref(vp, freeblks-fb_quota); + quotaref(ITOV(ip), freeblks-fb_quota); (void) chkdq(ip, -datablocks, NOCRED, 0); #endif freeblks-fb_chkcnt = -datablocks; Bingo, this fixes the issue for me! Testing it out on one machine now and will push it out to the others gradually ... thanks! ___ 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
