From owner-freebsd-fs@freebsd.org Sun Jan 8 21:42:19 2017 Return-Path: <owner-freebsd-fs@freebsd.org> Delivered-To: freebsd-fs@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 D31DBCA6A84 for <freebsd-fs@mailman.ysv.freebsd.org>; Sun, 8 Jan 2017 21:42:19 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thebighonker.lerctr.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE51B1088; Sun, 8 Jan 2017 21:42:19 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date: Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=YHoTYVQfZoGi3/0HHlowmpPgQLkxsXlvZ3/UQeTohmw=; b=GhSqf/oD5N0SIxXXLU6BOTglXY OlzBSFDhNyTDL5WREN0Fvt8sp+HqBwwjU/64NZZNTqsiSBvc1Wu6ey0zFnlifJDXA2MCstNwh+myK FW0KRBDyHWMG99gmp9TvehlUP088YgGsuM92I03f6ciK9yjA/YQ1xAfVbcHeSuRvztI4=; Received: from thebighonker.lerctr.org ([2001:470:1f0f:3ad:223:7dff:fe9e:6e8a]:60084 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87_1 (FreeBSD)) (envelope-from <ler@lerctr.org>) id 1cQLEH-0005ug-Sp; Sun, 08 Jan 2017 15:42:18 -0600 Received: from 2001:470:1f0f:42c:6d1d:a817:4442:35b by webmail.lerctr.org with HTTP (HTTP/1.1 POST); Sun, 08 Jan 2017 15:42:17 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 08 Jan 2017 15:42:17 -0600 From: Larry Rosenman <ler@lerctr.org> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Ben RUBSON <ben.rubson@gmail.com>, Freebsd fs <freebsd-fs@freebsd.org>, Rick Macklem <rmacklem@freebsd.org> Subject: Re: NFS mounted ZFS (From FreeNAS 9.10): Invalid Arg on rsync In-Reply-To: <fca1b327c69fdbc431365e0c316761eb@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> <YTXPR01MB01893055F0CBC2175632F1E0DD650@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM> <fca1b327c69fdbc431365e0c316761eb@lerctr.org> Message-ID: <0331b4c532d4bc2a49c602062a2e3b17@lerctr.org> X-Sender: ler@lerctr.org User-Agent: Roundcube Webmail/1.2.3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems <freebsd-fs.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/> List-Post: <mailto:freebsd-fs@freebsd.org> List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>, <mailto:freebsd-fs-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sun, 08 Jan 2017 21:42:19 -0000 On 2017-01-08 14:42, Larry Rosenman wrote: > 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@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. vfs.nfsd.disable_checkutf8 this IS on FreeNAS, so I set it. Does it have the same effect? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281