NFS mounted ZFS (From FreeNAS 9.10): Invalid Arg on rsync

Larry Rosenman ler at lerctr.org
Sun Jan 8 20:42:10 UTC 2017


On 2017-01-08 14:39, Rick Macklem wrote:
> 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=0
> 
> I have no idea if these bytes are valid UTF-8 or not, but the sysctl
> is worth a try.
> 
>> Rick? Yep, it's me...
> [stuff snipped]
ler at freenas.lerctr.org's password:
Last login: Sun Jan  8 09:40:47 2017 from 192.168.200.4
FreeBSD 10.3-STABLE (FreeNAS.amd64) #0 r295946+47645f1(9.10.2-STABLE): 
Mon Dec 19 08:30:01 UTC 2016

	FreeNAS (c) 2009-2016, The FreeNAS Development Team
	All rights reserved.
	FreeNAS is released under the modified BSD license.

	For more information, documentation, help or support, go here:
  	http://freenas.org
Welcome to FreeNAS
$ sudo sysctl vfs.nfsd.enable_checkutf8=0
Password:
sysctl: unknown oid 'vfs.nfsd.enable_checkutf8'
$

:(

Ok, I'll just live with the noise.  I back this stuff up with Bacula as 
well.


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler at lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281


More information about the freebsd-fs mailing list