Date: Sun, 8 Jan 2017 20:39:31 +0000 From: Rick Macklem <rmacklem@uoguelph.ca> To: Larry Rosenman <ler@lerctr.org>, Ben RUBSON <ben.rubson@gmail.com> Cc: Freebsd fs <freebsd-fs@freebsd.org>, Rick Macklem <rmacklem@FreeBSD.org> Subject: Re: NFS mounted ZFS (From FreeNAS 9.10): Invalid Arg on rsync Message-ID: <YTXPR01MB01893055F0CBC2175632F1E0DD650@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> In-Reply-To: <4d9f90734ab13535924ecf9283f3a46d@lerctr.org> References: <6ba7eb62ebbb5174bc93397cba2f1195@lerctr.org> <637634D0-B813-41B1-BC12-456236E3C207@gmail.com> <3181bf2f8627e6ba8f1dcb605a341674@lerctr.org> <a2245ae80ec28396672293440f6bb705@lerctr.org> <EB8A96B4-CED4-48CD-BB5B-1EBE0E1C1072@gmail.com>, <4d9f90734ab13535924ecf9283f3a46d@lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Larry Rosenman wrote: > that's my assumption as well. > If I touch it with that exact string (including the #'s) it works, > HOWEVER, I suspect when rsync > copies it uses the real Unicode/UTF-8 bytes. > > And, I suspect NFSv4.1 has an issue. The original NFSv4 RFC #3530 required that all names be UTF-8 compliant and that the server return an error for any filenames with non-UTF-8 compliant = chars. (I think more recent RFCs have become less stringent w.r.t. this, but I'm not sure.) The FreeBSD NFSv4 server has a sysctl that loosens this restriction. I don'= t know if it is FreeNAS or not? # sysctl vfs.nfsd.enable_checkutf8=3D0 I have no idea if these bytes are valid UTF-8 or not, but the sysctl is wor= th a try. > Rick? Yep, it's me... [stuff snipped]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YTXPR01MB01893055F0CBC2175632F1E0DD650>