Date: Mon, 4 Dec 2017 00:46:21 +0000 From: Rafal Lukawiecki <raf@rafal.net> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Colin Percival <cperciva@tarsnap.com>, "freebsd-cloud@freebsd.org" <freebsd-cloud@freebsd.org> Subject: Re: Suppress kernel messages "NFSv4 fileid > 32bits" Message-ID: <F338760E-4209-4129-A9C6-4687490538A1@rafal.net> In-Reply-To: <YTOPR0101MB2172DD382234F70C201C7654DD3C0@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM> References: <386518E3-1D01-4E1F-BB77-E9C530E05381@rafal.net> <0100015ff59bd564-84bd069a-00b5-4a05-a8aa-dbe2aa19693c-000000@email.amazonses.com> <D64EB3EA-37B0-4FC3-9D0C-31642030B654@rafal.net> <010001601e629361-9732ac13-ac59-462a-b30f-92702c3600a4-000000@email.amazonses.com> <YTOPR0101MB2172DD382234F70C201C7654DD3C0@YTOPR0101MB2172.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F338760E-4209-4129-A9C6-4687490538A1>