From owner-freebsd-net@freebsd.org Wed Feb 8 18:23:18 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66718CD649A for ; Wed, 8 Feb 2017 18:23:18 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 344157E1 for ; Wed, 8 Feb 2017 18:23:18 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from crest.local (unknown [87.253.189.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id 3BC7C118D9 for ; Wed, 8 Feb 2017 19:23:16 +0100 (CET) Subject: Re: NFSROOT and lagg(4) To: freebsd-net@freebsd.org References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> <20170204210054.GJ2092@kib.kiev.ua> From: Jan Bramkamp Message-ID: Date: Wed, 8 Feb 2017 19:23:15 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: <20170204210054.GJ2092@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 18:23:18 -0000 On 04/02/2017 22:00, Konstantin Belousov wrote: > On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote: >> "what I want" is to pxe/netboot and then switch over to using a lagg(4) >> interface that includes the interface used in the pxe/netboot boot up. >> I suspect, I have to switch to MDROOT to do this, but I thought I'd ask >> if anyone is doing this type of configuration in their labs? >> >> What seems to happen is that I lose the nfsroot when I reconfigure the >> lagg, and I no longer have access to reconfigure. >> >> e.g. pxeboot from em0, then reconfigure networking to use em0/em1 in lagg0: >> >> em0: flags=8843 metric 0 mtu 1500 >> >> options=5259b >> ether 00:30:18:c5:0a:a9 >> nd6 options=29 >> media: Ethernet autoselect (1000baseT ) >> status: active >> em1: flags=8843 metric 0 mtu 1500 >> >> options=5259b >> ether 00:30:18:c5:0a:a9 >> nd6 options=29 >> media: Ethernet autoselect (1000baseT ) >> status: active >> lagg0: flags=8843 metric 0 mtu 1500 >> >> options=5259b >> ether 00:30:18:c5:0a:a9 >> inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255 >> nd6 options=29 >> media: Ethernet autoselect >> status: active >> groups: lagg >> laggproto lacp lagghash l2,l3,l4 >> laggport: em0 flags=1c >> laggport: em1 flags=1c >> > > Look at reroot support, see reboot(8) option -r. I suspect you could > need two reroots: first to some tmpfs or memory backed md(4) where > ifconfig is present to reconfigure interfaces, second to boot into the > final root. You can't reroot into a tmpfs. It gets unmounted during the reroot which deletes every it ever contained.