From owner-freebsd-current@freebsd.org Tue Mar 21 09:05:05 2017 Return-Path: Delivered-To: freebsd-current@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 01B8CD14023 for ; Tue, 21 Mar 2017 09:05:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C4414162A; Tue, 21 Mar 2017 09:05:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0ON500900QACR000@st13p35im-asmtp001.me.com>; Tue, 21 Mar 2017 09:05:03 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1490087103; bh=UOa/z9BLi1z+9Gc7dUteVUv0ZBD7f7MbJtX4/3LbmqU=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=GlmhEmNws4tqip0R9MXze+4xDfX3ZUspwPW08hVmUvKb7L5qF0bYfzZD5xDzdXWQW cRqycNUTJNNjfePtm3Bh2vGo6uAH/IxYSVcFm8hsC0LnlC/IzxJQZ+38bK2bOBmKDn PwBu1p+iJcDpeMNkQZrSbvmFan9j4MzhnjB99bSJqgGraC1CiFA8TIHQCTm7vHsBvN bGUu1gcobtiXNNbMfvdQCRirs5Jc7odvcSjDUODkrYHRqQE9eVGxM/PqGmzoVlDV00 BDPJ/tH3KiGEBd444yYPCjjt3fDdBH5qksI0aBlb4ILhGLvIdT95gf+UgiRyo/iD0Q c9/gYoL+VNe2g== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0ON500M1DQKCHI30@st13p35im-asmtp001.me.com>; Tue, 21 Mar 2017 09:05:03 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-21_07:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1703210082 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: NFSv2 boot & OLD_NFSV2 Date: Tue, 21 Mar 2017 11:04:59 +0200 In-reply-to: <80C5425F-9A71-45D9-BA41-229E4E72EC36@cs.huji.ac.il> Cc: Baptiste Daroussin , Rick Macklem , FreeBSD Current To: Daniel Braniss References: <38DD1950-AD12-4A27-8335-54F997E408DF@me.com> <20170320192000.6hal22ibnr3ajog3@ivaldir.net> <1B7471CD-2F2D-4F22-9D25-E46580CF9E96@me.com> <84D239AB-AB57-4A50-9700-E42BBF9CBE5A@cs.huji.ac.il> <20170321081339.2wbx3rb32qdavvn3@ivaldir.net> <80C5425F-9A71-45D9-BA41-229E4E72EC36@cs.huji.ac.il> X-Mailer: Apple Mail (2.3259) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 09:05:05 -0000 > On 21. m=C3=A4rts 2017, at 10:50, Daniel Braniss = wrote: >=20 >=20 >> On 21 Mar 2017, at 10:13, Baptiste Daroussin > wrote: >>=20 >> On Tue, Mar 21, 2017 at 09:58:21AM +0200, Daniel Braniss wrote: >>>=20 >>>> On 20 Mar 2017, at 23:55, Toomas Soome > wrote: >>>>=20 >>>>>=20 >>>>> On 20. m=C3=A4rts 2017, at 23:53, Rick Macklem = > wrote: >>>>>=20 >>>>> Baptiste Daroussin wrote: >>>>>> On Mon, Mar 20, 2017 at 08:22:12PM +0200, Toomas Soome wrote: >>>>>>> Hi! >>>>>>>=20 >>>>>>> The current boot code is building NFSv3, with preprocessor = conditional OLD_NFSV2. Should NFSv2 code still be kept around or can we = burn it? >>>>>>>=20 >>>>>>> rgds, >>>>>>> toomas >>>>>>=20 >>>>>> I vote burn >>>>>>=20 >>>>>> Bapt >>>>> I would be happy to see NFSv2 go away. However, depending on how = people configure >>>>> their diskless root fs, they do end up using NFSv2 for their root = fs. >>>>>=20 >>>>> Does booting over NFSv3 affect this? >>>>>=20 >>>>> I think the answer is no for a FreeBSD server (since the NFSv2 = File Handle is the same as >>>>> the NFSv3 one, except padded with 0 bytes to 32bytes long). >>>>> However, there might be non-FreeBSD NFS servers where the NFSv2 = file handle is different >>>>> than the NFSv3 one and for that case, the user would need NFSv2 = boot code (or >>>>> reconfigure their root fs to use NFSv3). >>>>>=20 >>>>> To be honest, I suspect few realize that they are using NFSv2 for = their root fs. >>>>> (They'd see it in a packet trace or via "nfsstat -m", but = otherwise they probably >>>>> think they are using NFSv3 for their root fs.) >>>>>=20 >>>>> rick >>>>=20 >>>> if they do not suspect, they most likely use v3 - due to simple = fact that you have to rebuild loader to use NFSv2 - it is compile time = option. >>>>=20 >>>=20 >>> old systems, 8.x, still use/boot v2, and so do old linux. >>> NetApp has discontinued support for v2, so we had to move this = machines to use FreeBSD server and the day was >>> saved. So, till these machines get upgraded/discontinued we have a = problem. There are several solutions >>> to this issue, but as long as it's a matter of getting rid for the = sake of it, I would vote to keep it a while longer. >>>=20 >>> danny >>>=20 >>>=20 >> Given you are speaking of 8.x I suppose you are using the loader that = comes with >> it, meaning you are safe if we remove it from the loader in 12.0 = (note as said >> by Toomas that is it is already off by default in the 12.0 loader) am = I missing >> something? >>=20 >=20 > as usual, did not read the whole thread, I assumed - wrongly - that = support for v2 would be discontinued. > removing v2 support from the boot process is fine! great, go for it. = It will only involve newer > hosts, and simplifying the boot process is always a good idea. >=20 > sorry for the noise. > danny >=20 yes, just to clarify, the current loader code (in current), is having = NFS code implemented as: #ifdef OLD_NFSV2 v2 implementation is here #else v3 implementation is here #endif Which does mean that pxeboot/loader.efi is built by default to use v3 = only, but we do have 2 parallel implementations of the NFS readers. And = yes, the question is just about boot loader reader code (we do not = implement NFS writes) - and we are *not* talking about server side = there. Indeed it also is possible to merge those 2 version implementations, but = to be honest, I see very little point of doing that either, even if = there is some setup still with v2 only server, there is still an option = just to use TFTP based boot - especially given that current boot loader = does provide parallel option to use either NFS or TFTP (via dhcp option = 150), with existing binaries - that is, without having to re-compile. rgds, toomas