This error occurs when I try to stat the file. 'ls -l' for example will trigger it, but an 'ls' won't. That may have to do with how Gluster's 'elastic hash algorithm' works on files and directories.
I am still trying to determine...how, when and why you would ever get permission denied errors...and how the SUNWattr_ro and SUNWattr_rw system attributes even work. There appears to be very little documentation on how this even works (that I have been able to find anyway). Thanks, Shain -----Original Message----- From: Tim Haley [mailto:tim.ha...@oracle.com] Sent: Tue 1/11/2011 4:20 PM To: Shain Miley Cc: opensolaris-discuss@opensolaris.org Subject: Re: [osol-discuss] Disabling SUNWattr_ro and SUNWattr_rw On 01/11/11 02:11 PM, Shain Miley wrote: > Cindy, > Thanks a lot for this info. > > These errors are occurring in/with our attempts to use Glusterfs > (gluster.org) on top of zfs. It is only happening on a small number of > our total files so far...but it is happening non the less. > > Gluster requires extended attributes in order to work correctly. > > I was under the impression that SUNWattr_ro and SUNWattr_rw are part of > the 'extensible attributes interfaces' (although I am piecing this > together from several different sources). > > Does the procedure that you describe below allow me to continue to use > extended attributes, or does that simply disable them altogether? > > Here is an example of the a file placed on the filesystem via Gluster: > > > smi...@server1:/smbpool/glusterfs# runat audio/ ls -l > total 11 > -r--r--r-- 1 root root 84 Jan 9 13:13 SUNWattr_ro > -rw-r--r-- 1 root root 408 Jan 9 13:13 SUNWattr_rw > -rwxrwxrwx 1 root root 12 Jan 9 13:13 trusted.afr.171.19.13.193-1 > -rwxrwxrwx 1 root root 12 Jan 9 13:13 trusted.afr.171.19.13.192-1 > -rwxrwxrwx 1 root root 8 Jan 8 15:34 trusted.posix1.gen > > > According to the support team at Gluster they are not adding them (which > I know is true) and their software should be ignoring them for the most > part. > > Here is an example from the error log (just so you are clear as to what > we are talking about): > > > [2011-01-07 16:49:31] E [compat.c:206:solaris_setxattr] libglusterfs: > Couldn't set extended attribute for /smbpool/glusterfs/audio (13) > [2011-01-07 16:49:31] E [posix.c:3056:handle_pair] posix1: > /smbpool/glusterfs/audio: key:SUNWattr_ro error:Permission denied > > I am hoping to get some more verbose output tonight when I increase the > logging level and restart the cluster. > > Thanks again, > > Shain > > Did you see this error when copying a file from one part of the glusterfs to the other? One thing I can think of that might be happening is that they are trying to copy all extended attributes from an existing file to a new copy, and really they should skip over the system attributes, they'll be created in the copy automatically. -tim > > > > On 01/11/2011 03:31 PM, Cindy Swearingen wrote: >> Hi Shain, >> >> You can't disable the system extended attributes and they shouldn't >> cause any problem unless you are accessing files with these >> attributes on systems that run Solaris 10 releases, which don't >> understand how to translate them. >> >> Is this is cause of the permission denied errors? >> >> If you want to disable users from creating them, then remount >> the the file system with noxattr. >> >> See the output below of how the attr creation succeeds and >> then errors after the file system is mounted with noxattr. >> >> Or, you can create a file system with noaxttr on, like this: >> >> # zfs create -o xattr=off rpool/fs4 >> >> Thanks, >> >> Cindy >> >> >> # zfs create rpool/fs3 >> # cd /rpool/fs3 >> # touch file.1 >> # runat file.1 ls -l >> total 1 >> -r--r--r-- 1 root root 156 Jan 11 13:23 SUNWattr_ro >> -rw-r--r-- 1 root root 472 Jan 11 13:23 SUNWattr_rw >> # runat file.1 touch attr_1 >> # runat file.1 ls -l >> total 2 >> -r--r--r-- 1 root root 156 Jan 11 13:23 SUNWattr_ro >> -rw-r--r-- 1 root root 472 Jan 11 13:23 SUNWattr_rw >> -rw-r--r-- 1 root root 0 Jan 11 13:23 attr_1 >> >> # cd / >> # zfs umount rpool/fs3 >> # zfs mount -o noxattr rpool/fs3 >> # cd /rpool/fs3 >> # touch file.2 >> # runat file.2 ls -l >> total 1 >> -r--r--r-- 1 root root 156 Jan 11 13:23 SUNWattr_ro >> -rw-r--r-- 1 root root 472 Jan 11 13:23 SUNWattr_rw >> # runat file.2 touch attr_1 >> touch: setting times of `attr_1': Invalid argument >> >> >> On 01/11/11 10:29, Shain Miley wrote: >>> Hello, >>> I was wondering if there is any way to disable the SUNWattr_ro and >>> SUNWattr_rw file attributes in OpenSolaris. >>> >>> I am receiving some permission denied error messages assocaited with >>> SUNWattr_ro on some files. It has been suggested that there is a way >>> to disable them, or remove them, etc. However I have been unable to >>> find any information about doing so. >>> >>> Example: >>> ad...@server1:/ztank/temp# touch test >>> ad...@server1:/ztank/temp# runat test ls -l >>> total 2 >>> -r--r--r-- 1 root root 84 Jan 11 11:58 SUNWattr_ro >>> -rw-r--r-- 1 root root 408 Jan 11 11:58 SUNWattr_rw >>> >>> >>> Thanks in advance, >>> >>> Shain >> > > _______________________________________________ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org
_______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
