From owner-freebsd-current@freebsd.org Tue Mar 21 08:48:04 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 51079D0A366 for ; Tue, 21 Mar 2017 08:48:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (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 287A26A8; Tue, 21 Mar 2017 08:48:04 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0ON500M00PC8M300@st13p35im-asmtp002.me.com>; Tue, 21 Mar 2017 08:48:03 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=4d515a; t=1490086083; bh=5KByKSKX/D1x5bqK5h4flIbx8JJvF1UY6eUpMDweRjI=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=Yk2BSRCw825SIXhSWIW0KA5ZqSG5iNeM+Rh5gO6rwa9Fe9Qf1Ybiq8Z3tjmQ6bg7G z4XgZ5+tmVvUh5gZT96sYnH+Xr5Px2KBdU2FEqXhM8nZn1WMj/BXbPxFwfL2OShyhw 9FkXWLNAGqizh1kUVroMYaK9+znKITHNBv3d5C1cagj1/I6P9Z6EqQAdptW4FCJFk9 lFTEZi2xPVO6gXXlO4Gkto45xjIo+3uvB87OryMtffbjoi0Pj+h4NKzrokV819e0LP ugyoYJudM/CXAdfJJOqYnf8ch3K/rX9hScygbxuMreTHGe7HLF1Nq7RrDOZyebkC94 OU1y/DINlLw6A== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0ON500D6FPS0I910@st13p35im-asmtp002.me.com>; Tue, 21 Mar 2017 08:48:02 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-21_06:,, 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-1703210079 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: NFSv2 boot & OLD_NFSV2 From: Toomas Soome In-reply-to: <20170321081339.2wbx3rb32qdavvn3@ivaldir.net> Date: Tue, 21 Mar 2017 10:47:57 +0200 Cc: Daniel Braniss , Rick Macklem , FreeBSD Current Content-transfer-encoding: quoted-printable Message-id: <1CAABCFC-2385-444D-B909-F5F1C33F8A88@me.com> 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> To: Baptiste Daroussin X-Mailer: Apple Mail (2.3259) 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 08:48:04 -0000 > On 21. m=C3=A4rts 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 Indeed, we definitely are *not* talking about back porting the removal, = there is no reason for that whatsoever. In fact at least 11 is = distributing loader based on NFSv3, likely even 10 (I havent checked = that). So yes, just talking about possible removal in current only. rgds, toomas