From owner-freebsd-cloud@freebsd.org Mon Dec 4 00:46:47 2017 Return-Path: Delivered-To: freebsd-cloud@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 9F762E6E8C1 for ; Mon, 4 Dec 2017 00:46:47 +0000 (UTC) (envelope-from raf@rafal.net) Received: from fbo-2.mxes.net (mxout-22.mxes.net [216.86.168.222]) (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 7572B7109E for ; Mon, 4 Dec 2017 00:46:46 +0000 (UTC) (envelope-from raf@rafal.net) Received: from smtp-out-1.mxes.net (smtp-out-1.mxes.net [67.222.241.250]) by fbi-2.mxes.net (Postfix) with ESMTP id 8D09627500 for ; Sun, 3 Dec 2017 19:46:45 -0500 (EST) Received: from [192.168.40.37] (86-40-118-125-dynamic.agg2.bri.bbh-prp.eircom.net [86.40.118.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id DB743274F9; Sun, 3 Dec 2017 19:46:22 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Re: Suppress kernel messages "NFSv4 fileid > 32bits" From: Rafal Lukawiecki In-Reply-To: Date: Mon, 4 Dec 2017 00:46:21 +0000 Cc: Colin Percival , "freebsd-cloud@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <386518E3-1D01-4E1F-BB77-E9C530E05381@rafal.net> <0100015ff59bd564-84bd069a-00b5-4a05-a8aa-dbe2aa19693c-000000@email.amazonses.com> <010001601e629361-9732ac13-ac59-462a-b30f-92702c3600a4-000000@email.amazonses.com> To: Rick Macklem X-Mailer: Apple Mail (2.3445.4.7) X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2017 00:46:47 -0000 > My only suggestion is that the message should be generated at least = once, > since it does indicate that your mount is "broken". When the fileid = (i-node#) > is truncated to 32bits, it is possible for two different fileids to be = mapped to > the same number. The most common error I am aware of is the fts(3) = library > functions generating "cycle in directory structure" errors. >=20 > It would have to be a direct commit to stable/11, but if Colin wants = to do it, > I don't have a problem with it, rick >=20 That sounds very reasonable to me. If I knew the code of = nfs_commonsubs.c better, I would volunteer, but I suppose it would be = safer in Colin=E2=80=99s hands. Many thanks, Rafal=