"Invalid argument (22)" & "Operation not supported (95)" ???
mstuff at read.org.nz
Thu Apr 30 11:11:12 GMT 2009
OK, error (95) seems to be solved by enabling ACLs on target drive -
which don't seem to be enabled by default on user created ext3 volumes
(cf root volume, which does have ACLs on by default)...
Also, enable user extended attributes just in case. So, the mount
options for the target volume are now "defaults,acl,user_xattr" instead
of just "defaults".
Info from here:
The options common to all filesystems are:
Use default settings. Default settings are defined per file system
at the file system level. For ext3 file systems these can be set with
the tune2fs command. The normal default for Ext3 file systems is
equivalent to rw,suid,dev,exec,auto,nouser,async(no acl support). Modern
Red Hat based systems set acl support as default on the root file system
but not on user created Ext3 file systems. Some file systems such as XFS
enable acls by default. Default file system mount attributes can be over
ridden in /etc/fstab.
Error (22) seems completely obscure, only info I've found is this bug:
Re that bug, it seems (to a novice) unlikely that the se-linux xattr
would be incompatible across two systems running
220.127.116.11-170.2.56.fc10.i686 and 18.104.22.168-57.fc8. So, after a bit more
digging may be it's time to re-open that bug. Comments welcome.
On 08/04/09 12:01, henri wrote:
> It looks like you are running a version of SE LINUX. Keep in mind that I
> have not run rsync any SE LINUX system.
> However, on Mac OS X an error is reported when ACL's are not enabled on
> a destination partition. As such, you may want to check that ACL's are
> enabled on the destination volume.
> Details for enabling ACL's on Mac OS X :
> Also, depending upon your distribution, you may find that compiling the
> latest version of rsync for will help?
> Details for compiling rsync version 3 Mac OS X :
> Again, I am not sure if this is the problem you are having. However, I
> strongly recommend that you confirm that ACL's are enabled on your
> systems destination partition(s).
> Best of luck. I would be interested to know how you resolve this issue.
> On 3/04/2009, at 11:24 PM, Morgan Read wrote:
>> Hi Folks
>> I've gone back over the list and the only reference I've found to
>> "Invalid argument (22)" is here:
>> That seems a different context of character set mismatches.
>> The common parts to my errors are:
>> rsync: rsync_xal_set: lsetxattr("...","security.selinux") failed:
>> Invalid argument (22)
>> rsync: rsync_xal_set: lsetxattr("...","user.Beagle") failed: Operation
>> not supported (95)
>> Where ... is some reference to a file relative to the source. Seems to
>> be a selinux issue on the former and a beagle issue on the latter.
>> Any ideas what's going on?
Getting errors: "There are problems with the signature" (or similar)?
Update your system by installing certificates from CAcert Inc, see here:
Or, if Internet Explorer is your default browser, simply click this link:
fedora + freedom; fact || fiction?
More information about the rsync