Rsync is called with ACL/xattr option but it's not supported by destination filesystem

Bug #571894 reported by rndmerle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Back In Time
Fix Released
Medium
Unassigned

Bug Description

Hi.

When rsyncing, those sort of errors occured :
rsync: rsync_xal_set: lsetxattr("somedir/.somefile.v4Iw7m","user.Zone.Identifier") failed: Operation not supported (95)

I'm using Ubuntu 9.10 and Ubuntu 10.4. The destination filesystem is ext3.
By default no drives are mounted with xattr support.
Rsync is compiled with ACL/xattr support by default, though.

Maybe it's related with https://bugs.launchpad.net/backintime/+bug/489380

I added the destination drive in /etc/fstab with the user_xattr option and rsync worked flawlessly.

Best regards.

Revision history for this message
Dan (danleweb) wrote :

The should be some options to enable/disable ACL/xattr.

Changed in backintime:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Steffen Neumann (sneumann) wrote :

Hi,

would that be a user-configurable setting,
or could BiT check whether the target can handle
ACL/xattr, as in try { rsync -AX } { catch ... }

Yours,
Steffen

Revision history for this message
rndmerle (rndmerle) wrote :

Maybe just parsing the result of the "mount" command to see if the destination device is mounted using the user_xattr option.
But BiT only know the destination path. How to find to which device this path belongs, I don't know.

Revision history for this message
Dan (danleweb) wrote :

Mount is not enough: it can be a remote drive (sshfs for example) but this don't tell enought the real fs.
I atted the option to enable/disable ACL/XATTR.

Changed in backintime:
status: Confirmed → Fix Committed
Dan (danleweb)
Changed in backintime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.