Kevin Kramer wrote: > no. I'm running on a Dell 1950. I'm updating the system now. Do my > aclmode,aclinherit look right? I've read the guide and think this is my > best option. > > thanks.
the ACL properties have no bearing on this. The issue is that you are using an NFSv3 client and its asking for a POSIX draft ACL which ZFS doesn't support. The ZFS code now returns ENOTSUP which should let the linux cp program know that ACLs aren't supported on the file system. what OS is on the client and what OS is on the server? -Mark > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 11, 2008 10:58 AM > To: kevin kramer > Cc: zfs-discuss@opensolaris.org > Subject: Re: [zfs-discuss] ACL invalid argument from client > > kevin kramer wrote: > > client CentOS 5.1 latest kernel > > mount option for zfs filesystem = > rw,nosuid,nodev,remount,noatime,nfsvers=3,udp,intr,bg > > ,hard,rsize=8192,wsize=8192 > > > > directory and parent owned by user and users GID, 775 > > on client touch /tmp/dummy > > cd to zfs area > > mv /tmp/dummy . > > > > receive this error > > /bin/mv /tmp/dummy . > > /bin/mv: preserving permissions for `./dummy': Invalid argument > > /bin/mv: preserving ACL for `./dummy': Invalid argument > > /bin/mv: preserving permissions for `./dummy': Invalid argument > > > > the file does get copied. but it sends exit 0 when similarly used in > a script > > > > zfs pool name = vol1 > > zfs get aclmode vol1 > > vol1 aclinherit discard local > > vol1 aclmode groupmask local > > > > vol1/scr20 is the mount point on the client > > > > vol1/scr20 aclinherit discard local > > vol1/scr20 aclmode groupmask local > > > > I've also tried using mount option noacl with no luck.. what do I > need to do to ignore ACL's on my clients that support ACL's? and I've > tried passthrough mode for aclinherit. > > > > thanks for any insight > > > > Is your ZFS file system on an S10 system? > > You are most likely seeing this bug. > > 6528189 cp -p invalid argument issue on Redhat linux AS 3.0 NFS client > against ZFS NFS directory > > This was fixed last May. > > Assuming you are on an S10 update then you probably want this patch. > > 127729-02 > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
