From owner-freebsd-cloud@freebsd.org Sun Dec 3 17:26:09 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 5C778E574CC for ; Sun, 3 Dec 2017 17:26:09 +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 353457F9C3 for ; Sun, 3 Dec 2017 17:26:08 +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 2D365274FE for ; Sun, 3 Dec 2017 12:19:11 -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 B264827505; Sun, 3 Dec 2017 12:18:58 -0500 (EST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\)) Subject: Suppress kernel messages "NFSv4 fileid > 32bits" From: Rafal Lukawiecki In-Reply-To: <0100015ff59bd564-84bd069a-00b5-4a05-a8aa-dbe2aa19693c-000000@email.amazonses.com> Date: Sun, 3 Dec 2017 17:18:56 +0000 Cc: Colin Percival 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> To: freebsd-cloud@freebsd.org 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: Sun, 03 Dec 2017 17:26:09 -0000 Is there a way to completely suppress the "NFSv4 fileid > 32bits=E2=80=9D = messages from flooding my logs and the subsequent emailed reports? This = message is unavoidable when running on AWS until FreeBSD 12 comes out, = based on the previous discussions here. I can see that Colin has worked on reducing their number = (https://reviews.freebsd.org/D8523) but I would prefer to disable this = message completely. Many thanks, Rafal -- Rafal Lukawiecki Data Scientist=20 Project Botticelli Ltd From owner-freebsd-cloud@freebsd.org Sun Dec 3 21:57:53 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 8C5E2E69A36 for ; Sun, 3 Dec 2017 21:57:53 +0000 (UTC) (envelope-from 010001601e629750-028b9ef1-0eb5-4cbf-a1f5-acb28d3e87a3-000000@amazonses.com) Received: from a8-13.smtp-out.amazonses.com (a8-13.smtp-out.amazonses.com [54.240.8.13]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 52B6D6B59E for ; Sun, 3 Dec 2017 21:57:52 +0000 (UTC) (envelope-from 010001601e629750-028b9ef1-0eb5-4cbf-a1f5-acb28d3e87a3-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn; d=tarsnap.com; t=1512338266; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=v3VUso5a5EDPH3GiTBMe6v3qgetR6vm6h53RTUveiYw=; b=YthFaVwi4jf9nnovrpfHC/ZVRNRJ5wwUrxVCL4yDzdtl0fTKTTc3bbAPGYtZMiDz CIIBcVfsZeDrjG6T4A1FdN4LRcL0C7Y1pgHatcHcqk3h4vaRQFKg71MPBWnV6g9AHU8 lt1LwZ/ESMUMWXIo03o3Ks8WI+Ys1qfzJMRlVKBI= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1512338266; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=v3VUso5a5EDPH3GiTBMe6v3qgetR6vm6h53RTUveiYw=; b=FYU505X5JcEciQJCkgvwMMttto88hSi4rkGceVP7kHI1uugnH7ZKDyzDDwvGUs7J nLNzRi2cIuv4liuYlm524gb0ZBXGKp2rMq8m6J/XijPPirjyE2l4fveEqRgcggqra0F JaoO+XXx6cZwBDadBOG3HWJT+/ZbNF1UDCnlRz9Q= Subject: Re: Suppress kernel messages "NFSv4 fileid > 32bits" To: Rafal Lukawiecki , freebsd-cloud@freebsd.org, Rick Macklem References: <386518E3-1D01-4E1F-BB77-E9C530E05381@rafal.net> <0100015ff59bd564-84bd069a-00b5-4a05-a8aa-dbe2aa19693c-000000@email.amazonses.com> From: Colin Percival Message-ID: <010001601e629750-028b9ef1-0eb5-4cbf-a1f5-acb28d3e87a3-000000@email.amazonses.com> Date: Sun, 3 Dec 2017 21:57:46 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2017.12.03-54.240.8.13 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES 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: Sun, 03 Dec 2017 21:57:53 -0000 On 12/03/17 09:18, Rafal Lukawiecki wrote: > Is there a way to completely suppress the "NFSv4 fileid > 32bits” messages > from flooding my logs and the subsequent emailed reports? This message is > unavoidable when running on AWS until FreeBSD 12 comes out, based on the > previous discussions here. Well, unavoidable when using EFS. Most people in EC2 aren't using EFS. > I can see that Colin has worked on reducing their number > (https://reviews.freebsd.org/D8523) but I would prefer to disable this > message completely. This is more of an NFS question than an EC2 question, but sure, suppressing that message completely is entirely doable. CCing in Rick, as the maintainer of the NFS code -- Rick, any opinion on having a vfs.nfs.suppress_32bits_warning sysctl, defaulting to 0, which suppresses those two warnings when set to nonzero? -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-cloud@freebsd.org Sun Dec 3 23:44:02 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 BAEA1E6C1CC for ; Sun, 3 Dec 2017 23:44:02 +0000 (UTC) (envelope-from raf@rafal.net) Received: from fbo-1.mxes.net (mxout-23.mxes.net [216.86.168.223]) (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 9243B6EAA6 for ; Sun, 3 Dec 2017 23:44:01 +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-1.mxes.net (Postfix) with ESMTP id 1F01C27549 for ; Sun, 3 Dec 2017 18:38:11 -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 65C6827544; Sun, 3 Dec 2017 18:37:47 -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: <010001601e629bb9-34372410-8c8e-4400-b082-0ff4f4ab7934-000000@email.amazonses.com> Date: Sun, 3 Dec 2017 23:37:45 +0000 Cc: freebsd-cloud@freebsd.org, Rick Macklem Content-Transfer-Encoding: quoted-printable Message-Id: <51462F8E-89C7-4FF2-AC56-8F63ED0BC8CB@rafal.net> References: <386518E3-1D01-4E1F-BB77-E9C530E05381@rafal.net> <0100015ff59bd564-84bd069a-00b5-4a05-a8aa-dbe2aa19693c-000000@email.amazonses.com> <010001601e629bb9-34372410-8c8e-4400-b082-0ff4f4ab7934-000000@email.amazonses.com> To: Colin Percival 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: Sun, 03 Dec 2017 23:44:02 -0000 > On 3 Dec 2017, at 21:57, Colin Percival wrote: >=20 > On 12/03/17 09:18, Rafal Lukawiecki wrote: >> Is there a way to completely suppress the "NFSv4 fileid > 32bits=E2=80=9D= messages >> from flooding my logs and the subsequent emailed reports? This = message is >> unavoidable when running on AWS until FreeBSD 12 comes out, based on = the >> previous discussions here. >=20 > Well, unavoidable when using EFS. Most people in EC2 aren't using = EFS. Apologies. I typed too fast. > CCing in Rick, as the maintainer of the NFS code -- Rick, any opinion = on > having a vfs.nfs.suppress_32bits_warning sysctl, defaulting to 0, = which > suppresses those two warnings when set to nonzero? Is this option already available somewhere in code, or would that be a = proposed one? I get tens of thousands of those warnings a day per server. Thankfully, = they are =E2=80=9Crolled-up=E2=80=9D with counts, but it still makes a = few hundred to low thousands of lines in the log and email reports. It = would be great to suppress it altogether till 2019 when FreeBSD 12 comes = out. Many thanks, Rafal From owner-freebsd-cloud@freebsd.org Mon Dec 4 00:31:17 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 844C8E6DE12 for ; Mon, 4 Dec 2017 00:31:17 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0058.outbound.protection.outlook.com [104.47.32.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28B9770463 for ; Mon, 4 Dec 2017 00:31:16 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM (52.132.46.161) by YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM (52.132.46.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.282.5; Mon, 4 Dec 2017 00:31:14 +0000 Received: from YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM ([fe80::f072:85d3:769:e6f8]) by YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM ([fe80::f072:85d3:769:e6f8%13]) with mapi id 15.20.0282.010; Mon, 4 Dec 2017 00:31:14 +0000 From: Rick Macklem To: Colin Percival , Rafal Lukawiecki , "freebsd-cloud@freebsd.org" Subject: Re: Suppress kernel messages "NFSv4 fileid > 32bits" Thread-Topic: Suppress kernel messages "NFSv4 fileid > 32bits" Thread-Index: AQHTbIHBzrn18CbEPkef8UkNsSPOcKMyU62G Date: Mon, 4 Dec 2017 00:31:14 +0000 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> In-Reply-To: <010001601e629361-9732ac13-ac59-462a-b30f-92702c3600a4-000000@email.amazonses.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2172; 6:TovdwOkfZD1WR1jf8pi4iEbftQPf1heNDa21XIjAizWQjU0lTZC28cXmwPYT7frN7UoloUFjkMXGxjN/SngrgW7MzFOXxo+eXqkk/x7TmQ9OZhgC2x7Gl9bM9NxTPk4Gj5jrd6NVuwTa/PjFQvNsiyvYR4fkbT9h0MDBk1LX+BS4rs+a4Ryrj0U6GBuxJDMCYVi+726wS1s3XK3b2mTRlcFd6nSh/bK6JVu0of00z1m7zxffmTbqco75B/mwAeqcdTj9kyVqUi81CQawFzrsJOyXr4cqXNzvBr1GTgq4Ul4ln4RXKtlE4/Zt9E/zQvT3yeZz/q1WSeZ1VryDXziQHACGLh4G2IMmDepCe6OFolg=; 5:3gGuNrX/pv6abN+yqTChj3E+3K0GOdq25xqw78tN4Iryzo1yYGs69d1vvVQnkvxd2uUxUSiYPRz6X0aXvd7XuBDqFkn0T4ckJOX4aW1h+TmmurV+qlDirqNB8xXjv0qfcL/6X8KEnn5A27jjKY+0uZ4DvXBikwx5OSfXt7OwLTM=; 24:BWIzkPtqlBqQ/pc8++iCnmqYIwn/ulqyOeRIxCp0i7iQWTu5LKm2TC4Qdfz1iqzNWvjKD1ayjUEfJqaC3iRq8ttIdSideOnhoesiBQ9Yy9o=; 7:OzTQSOPceKYvluxohvHLARYNeDCdVyR1YViMYqyvS+ddipiPlatxSF33Ppz59GfVPU2Ul6TRxJH7Bj8ZxSfkRnewq+KzeVPyjly1gpDm9upwpIoCGSeAHKNTeh/yeNZAc6bc4nUqvwzJCX+BtBgUPiAl2Q8y4ovkLc2RjMtZoZaYA8utdvPI2w8ayo3rg4sNcHnQbW3JuxXI1zFRa1t5N+f4Ny4oY1ZCInYnN8aXh4OEuYoBMrvTJyfbbXDxepDO x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: d398ff32-a2cd-43db-c737-08d53aae53de x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(8989060)(201703031133081)(201702281549075)(8990040)(5600026)(4604075)(2017052603286); SRVR:YTOPR0101MB2172; x-ms-traffictypediagnostic: YTOPR0101MB2172: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(20558992708506); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231022)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(20161123558100)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:YTOPR0101MB2172; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:YTOPR0101MB2172; x-forefront-prvs: 051158ECBB x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(366004)(376002)(346002)(174864002)(189002)(199003)(24454002)(102836003)(2501003)(53936002)(99286004)(6246003)(74482002)(101416001)(189998001)(106356001)(105586002)(478600001)(33656002)(5250100002)(229853002)(3280700002)(2900100001)(81156014)(8676002)(15650500001)(305945005)(6436002)(74316002)(2906002)(25786009)(55016002)(8936002)(9686003)(6306002)(14454004)(3660700001)(81166006)(68736007)(786003)(6506006)(316002)(97736004)(110136005)(76176011)(86362001)(54356011)(93886005)(5660300001)(2950100002)(7696005); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2172; H:YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: d398ff32-a2cd-43db-c737-08d53aae53de X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2017 00:31:14.7528 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2172 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:31:17 -0000 Colin Percival wrote: >On 12/03/17 09:18, Rafal Lukawiecki wrote: >> Is there a way to completely suppress the "NFSv4 fileid > 32bits=94 mess= ages >> from flooding my logs and the subsequent emailed reports? This message i= s >> unavoidable when running on AWS until FreeBSD 12 comes out, based on the >> previous discussions here. > >Well, unavoidable when using EFS. Most people in EC2 aren't using EFS. > >> I can see that Colin has worked on reducing their number >> (https://reviews.freebsd.org/D8523) but I would prefer to disable this >> message completely. > >This is more of an NFS question than an EC2 question, but sure, suppressin= g >that message completely is entirely doable. > >CCing in Rick, as the maintainer of the NFS code -- Rick, any opinion on >having a vfs.nfs.suppress_32bits_warning sysctl, defaulting to 0, which >suppresses those two warnings when set to nonzero? 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 mapp= ed to the same number. The most common error I am aware of is the fts(3) library functions generating "cycle in directory structure" errors. 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 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=