From owner-freebsd-fs@FreeBSD.ORG Mon Dec 6 22:54:46 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9806A106566C for ; Mon, 6 Dec 2010 22:54:46 +0000 (UTC) (envelope-from etnapierala@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 200A28FC15 for ; Mon, 6 Dec 2010 22:54:45 +0000 (UTC) Received: by fxm16 with SMTP id 16so9932669fxm.13 for ; Mon, 06 Dec 2010 14:54:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=zdTbltgVRuzGbwiw5RPQzh02xEU6mELkJk9Llh1lmm0=; b=eFSFSCaNZc2xJzbcJ7Q+xfa5cmlhPawerGgwcXPQFkQfhcojUhNBGXLm7lk/WLFBOM sMX2fQHRAYFoBmJD2sJpXItqGjtVC9Q6W9+rMkpDmrux7px7B4K5+al+8G0VwOSmWRPB y9d56ZcZfKjKyOCvqA/mZyLW4B7Rch3hDj0M8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=QvQkXLyT0V2QI/KmDk/xJTc7p5xp1RWkU9kZAFUeQg8RsA6t0fEsyiKzL9hUr5WNiF IkoQFRYsXC/kE72Mn3bBeqeRa08N82Fi9z6lceqQGfd11wCuhIpGqAfowJjGCkqgVawu IcCRm6ZTnsZ4+tzcT9FhtgYLAJyaDBFp7h97I= Received: by 10.223.100.4 with SMTP id w4mr5454326fan.26.1291676085055; Mon, 06 Dec 2010 14:54:45 -0800 (PST) Received: from [192.168.1.102] (45.81.datacomsa.pl [195.34.81.45]) by mx.google.com with ESMTPS id r24sm1737021fax.27.2010.12.06.14.54.43 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 06 Dec 2010 14:54:44 -0800 (PST) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=iso-8859-2 From: =?iso-8859-2?Q?Edward_Tomasz_Napiera=B3a?= In-Reply-To: <4CFD6808.8010004@netmusician.org> Date: Mon, 6 Dec 2010 23:54:41 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1124305635.1255931.1291670668724.JavaMail.root@erie.cs.uoguelph.ca> <4CFD5D73.1050601@netmusician.org> <4CFD6506.7090901@netmusician.org> <408E7ECD-C232-47DD-9D24-389F2CA4E406@FreeBSD.org> <4CFD6808.8010004@netmusician.org> To: Joe Auty X-Mailer: Apple Mail (2.1082) Cc: freebsd-fs@freebsd.org Subject: Re: Migrating from NFSv3 to v4 - NFSv4 ACL/permission confusion X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 22:54:46 -0000 Wiadomo=B6=E6 napisana przez Joe Auty w dniu 2010-12-06, o godz. 23:47: > Edward Tomasz Napiera=B3a wrote: >> Wiadomo=B6=E6 napisana przez Joe Auty w dniu 2010-12-06, o godz. = 23:34: >>> Edward Tomasz Napiera=B3a wrote: >>>> Wiadomo=B6=E6 napisana przez Joe Auty w dniu 2010-12-06, o godz. = 23:02: >>>>>> Also, make sure "ls -l" is not reporting "nobody". If the = user/group >>>>>> name mapping isn't working, most Setattr Ops will fail. >>>>>>=20 >>>>>> rick >>>>>>=20 >>>>> Thanks Rick, >>>>>=20 >>>>> I will look into this, but for the benefit of my own education, = are >>>>> NFSv4 ACLs supposed to be intertwined or separate from standard = Unix >>>>> permissions? I'm confused as to how the ACLs have changed from v3, = or if >>>>> this is even relevant to my problem not really knowing how they = work and >>>>> why they are needed :) >>>> Both POSIX.1e and NFSv4 ACLs are similar in that they both = influence >>>> the mode, and get influenced by it. In other words, when you = change >>>> the ACL, the mode gets updated; when you change the mode, the ACL = gets >>>> updated. Also, for both POSIX.1e and NFSv4 ACLs, file mode = continues >>>> to work as usual if you ignore the ACL part. >>>>=20 >>> Thanks for this! >>>=20 >>> So, if I want to just ignore the NFSv4 ACLs on account of not = needing >>> anything beyond the POSIX ACLs, I'm free to do so without = consequence... >>> Correct? >>=20 >> If you want to just ignore the ACLs on account of not needing = anything >> beyond the file mode, aka standard UNIX permissions. Filesystems >> support either POSIX.1e ACLs, or NFSv4 ACLs, not both. I didn't >> actually test NFSv4, but I guess it uses NFSv4 ACLs, not POSIX.1e. >> ZFS supports NFSv4 only. UFS supports either POSIX.1e or NFSv4, >> depending on the mount options. > I might be misunderstanding you, but ZFS definitely supports NFSv3 > because I've been mounting and using NFS volumes via this protocol > version for quite some time now without incident. Let me rephrase: ZFS only supports NFSv4 ACLs, it does not support POSIX.1e ACLs. Since ACLs are not a mandatory element of filesystem, sharing ZFS over NFSv3 works, but the client has no way to manipulate the ACLs or retrieve them. When sharing ZFS over NFSv4, the NFSv4 ACLs should work, I guess. Still, I'm not sure if the problem is actually ACL-related. -- If you cut off my head, what would I say? Me and my head, or me and my = body?