From owner-freebsd-stable@FreeBSD.ORG Tue Jan 20 20:47:21 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E701F913 for ; Tue, 20 Jan 2015 20:47:21 +0000 (UTC) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B1D8F9C8 for ; Tue, 20 Jan 2015 20:47:21 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id y10so5615885pdj.7 for ; Tue, 20 Jan 2015 12:47:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=f4FcfUa7BP+BR8FJvStOt1Z5JPxsHRJJK3CBqms0wmU=; b=EDJtBAgHJwTlaMbtU21BJ4iyd6RYPM+K1zg/WLSfbSaT1JaOvZjvrN0nLQZnfOwnp2 sAJ6n3HLmX0AEooJhM6zKFKGS9qG4zVsrwu+p+0ZCqevdoxNb16v3GR1tBcdQflmeLuY iMKMVij5cD2m/k0eKBwxGC5YbpDiVYnYdWoMcJd77h5dodgNinsJRJzrUywa99yZJ0lA bP+/1EukX+Fz1aDjyXCBn91hY6gepPPIVZ8ZBsQIf1Jnj96QloR34quPlZgRKTQldHLY 1zDPDi/2zi+GYwCoHZr2h53nZsbqHTL85kDuwZEcQL6DyAcx/lMCay3dramb0VPfPKg7 XGkA== MIME-Version: 1.0 X-Received: by 10.68.163.196 with SMTP id yk4mr56441784pbb.143.1421786841372; Tue, 20 Jan 2015 12:47:21 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.66.253.37 with HTTP; Tue, 20 Jan 2015 12:47:21 -0800 (PST) In-Reply-To: <20150120162844.GH42409@kib.kiev.ua> References: <54BE76CC.5020901@gmail.com> <20150120155406.GG42409@kib.kiev.ua> <54BE7BE3.8020207@gmail.com> <20150120162844.GH42409@kib.kiev.ua> Date: Tue, 20 Jan 2015 12:47:21 -0800 X-Google-Sender-Auth: 7znIOqueA8MRIkIicWdFVZcITKY Message-ID: Subject: Re: installworld fails From: Kevin Oberman To: Konstantin Belousov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Johan Hendriks , FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2015 20:47:22 -0000 On Tue, Jan 20, 2015 at 8:28 AM, Konstantin Belousov wrote: > On Tue, Jan 20, 2015 at 05:01:39PM +0100, Johan Hendriks wrote: > > Thanks, Your solution did work, thank you very much. > > > > > > I do the same routine as always. > > The buildworld and build kernel went fine. > > > > cd /usr/src/ > > make cleanworld > > make buildworld > > make kernel > > mergemaster -p > > make installworld > > mergemaster -iU > I doubt it, really. Installation procedure installs libc before libthr. > Your libc was built from sources before r277317, while libthr was at > r277317 or after. > > Also, as I said, the mere complain about libthr during installworld is > a red mark, since no install-time tools are multithreaded, AFAIK. > Also, a minor, but occasionally significant deviation from the recommended procedure is that you need to do "mergemaster -p" before the "make kernel". If you check the man page on mergemaster you will note that it is intended to be run even before buildworld, but it's pretty unlikely that a buildworld will fail because of it. There was one update back four or five years ago that depended on a user or group to do the kernel and lots of reports of a broken kernel install came in. Rare, but very annoying. Also, I prefer F to U and use -P as an aded safety factor. As was pointed out to me a wile back, -U has an inherent race that can bite you in a couple of ways. Again, unlikely to bite you, but not impossible.There is a warning in the man page for mergemaster.. Also, a reboot to single user between "make kernel" and "make installworld" is a really, really good idea. If you installworld and your kernel is bad (and this happens once in a while), you have a real mess on your hands. With remote systems with no OOB access to the console skipping the reboot this is almost a necessity, but make sure that you have done an identical upgrade on a local system before trying it Finally, buildworld does a cleanworld, so a separate "make cleanworld" is a waste of time. There are cases when the clean (in either way) is inadequate, so I do "rm -r /usr/obj/*" and add "-DNO_CLEAN" to both buildworld and kernel (or buildkernel). If you have multiple CPUs, -jN (where 'N' is a bit greater than the number of cores) is a big time saver in buildworld and buidlkernel. Yes, this stuff is a bit paranoid, but costs little, so I recommend it. Several years of engineering a critical high performance (currently up to 340 Gbps) international network makes me very conservative. Making a mistake that cuts off the data flow from the Large Hadron Collider in Europe to the US is a really bad idea. ;-) At 100 Gbps, it only takes a very short hit to blow away a .9999 reliability and my organization wanted 5 9s. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com