Backup Central

Dear All,

I get this error in spite of having ACL enabled in the destination
volume and I have also manually checked it. pylibacl is also working
fine.

Fatal Error: --never-drop-acls specified, but ACL support
missing from destination filesystem
No increments older than Fri Sep 30 14:23:15 2005 found, exiting.


rdiff-backup from FINK project. pylibacl added manually and will be
submitted to FINK.

Another error that I was able to fix: 'Log.FatalError' changed to
'log.Log.FatalError' to fix it ---
Traceback (most recent call last):
File "/sw/bin/rdiff-backup", line 23, in ?
rdiff_backup.Main.Main(sys.argv[1:])
File "/sw/lib/python2.4/site-packages/rdiff_backup/Main.py", line
293, in Main
take_action(rps)
File "/sw/lib/python2.4/site-packages/rdiff_backup/Main.py", line
263, in take_action
elif action == "backup": Backup(rps[0], rps[1])
File "/sw/lib/python2.4/site-packages/rdiff_backup/Main.py", line
304, in Backup
rpout.conn.fs_abilities.backup_set_globals(rpin)
File "/sw/lib/python2.4/site-packages/rdiff_backup/
fs_abilities.py", line 608, in backup_set_globals
bsg.set_acls()
File "/sw/lib/python2.4/site-packages/rdiff_backup/
fs_abilities.py", line 424, in set_acls
Log.FatalError('--never-drop-acls specified, but ACL support\n'
NameError: global name 'Log' is not defined

Many thanks.

Best regards,
Murali.

Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Sun, 30 Oct 2005 14:20:20 +0000

I get this error in spite of having ACL enabled in the destination
volume and I have also manually checked it. pylibacl is also working
fine.

When you run it at high verbosity do you see "Access control lists
On" in the description of the destination system?

Another error that I was able to fix: 'Log.FatalError' changed to
'log.Log.FatalError' to fix it ---

Fixed, thanks.


--
Ben Escoto

Begin forwarded message:

From: Murali Vadivelu <mkv22 < at > cam.ac.uk>
Date: 30 October 2005 04:11:15 pm GMT
To: Ben Escoto <ben < at > emerose.org>
Subject: Re: [rdiff-backup-users] rdiff-backup - ACL troubles!


Hmm... I find it OFF on botht he source and destination. I checked
acls manually again. its definitely set and working!
/sw/bin/rdiff-backup --force --never-drop-acls -v9 /Users/muralikv/
Desktop/ /Volumes/RSNAPSHOT/Desktop
Sun Oct 30 16:10:09 2005 ACLs not supported by filesystem at /
Users/muralikv/Desktop
Sun Oct 30 16:10:09 2005
-----------------------------------------------------------------
Detected abilities for source (read only) file system:
Access control lists Off
Extended attributes On
Case sensitivity Off
Mac OS X style resource forks On
Mac OS X Finder information On
-----------------------------------------------------------------
Sun Oct 30 16:10:09 2005 Making directory /Volumes/RSNAPSHOT/
Desktop/rdiff-backup-data/rdiff-backup.tmp.0
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/5-_ a.
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/5-_ a.
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/:\?
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/A
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/a
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/foo
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/foo
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/hardlinked_file1
Sun Oct 30 16:10:09 2005 Hard linking /Volumes/RSNAPSHOT/Desktop/
rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file2 to /Volumes/
RSNAPSHOT/Desktop/rdiff-backup-data/rdiff-backup.tmp.0/
hardlinked_file1
Sun Oct 30 16:10:09 2005 ACLs not supported by filesystem at /
Volumes/RSNAPSHOT/Desktop/rdiff-backup-data/rdiff-backup.tmp.0
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/dir_inc_check
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/dir_inc_check
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/regfile
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/regfile
Sun Oct 30 16:10:09 2005 Touching /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/high_perms
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0/high_perms
Sun Oct 30 16:10:09 2005 Deleting /Volumes/RSNAPSHOT/Desktop/rdiff-
backup-data/rdiff-backup.tmp.0
Sun Oct 30 16:10:09 2005 Removing directory /Volumes/RSNAPSHOT/
Desktop/rdiff-backup-data/rdiff-backup.tmp.0
Sun Oct 30 16:10:09 2005
-----------------------------------------------------------------
Detected abilities for destination (read/write) file system:
Ownership changing Off
Hard linking On
fsync() directories On
Directory inc permissions On
High-bit permissions On
Extended filenames Off
Access control lists Off
Extended attributes On
Case sensitivity Off
Mac OS X style resource forks On
Mac OS X Finder information On
-----------------------------------------------------------------
Sun Oct 30 16:10:09 2005 Fatal Error: --never-drop-acls specified,
but ACL support
missing from destination filesystem
Sun Oct 30 16:10:09 2005 Cleaning up


On 30 Oct 2005, at 03:48 pm, Ben Escoto wrote:


Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Sun, 30 Oct 2005 14:20:20 +0000



I get this error in spite of having ACL enabled in the destination
volume and I have also manually checked it. pylibacl is also working
fine.



When you run it at high verbosity do you see "Access control lists
On" in the description of the destination system?



Another error that I was able to fix: 'Log.FatalError' changed to
'log.Log.FatalError' to fix it ---



Fixed, thanks.


--
Ben Escoto

Could this be the cause? - Is rdiff-backup testing for acl ability at
the source and destination directory instead of the respective volume
root?

Murali-PB-G4-Tiger:~ muralikv$ sudo fsaclctl -p /Volumes/RSNAPSHOT/
Access control lists are supported on /Volumes/RSNAPSHOT/.
Murali-PB-G4-Tiger:~ muralikv$ sudo fsaclctl -p /
Access control lists are supported on /.
Murali-PB-G4-Tiger:~ muralikv$ sudo fsaclctl -p /Users/
error (-1) from /Users/. (Unknown error: -1). Support for access
control lists is unkown.
error (-1) from /Users/. (Unknown error: -1)


On 30 Oct 2005, at 03:48 pm, Ben Escoto wrote:

Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Sun, 30 Oct 2005 14:20:20 +0000


I get this error in spite of having ACL enabled in the destination
volume and I have also manually checked it. pylibacl is also working
fine.


When you run it at high verbosity do you see "Access control lists
On" in the description of the destination system?


Another error that I was able to fix: 'Log.FatalError' changed to
'log.Log.FatalError' to fix it ---


Fixed, thanks.


--
Ben Escoto

Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Sun, 30 Oct 2005 17:16:18 +0000
Could this be the cause? - Is rdiff-backup testing for acl ability
at the source and destination directory instead of the respective
volume root?

Sun Oct 30 16:10:09 2005 ACLs not supported by filesystem at /Users/
muralikv/Desktop

Yes, if you are trying to back up /Users/muralikv/Desktop it will test
that very directory. If that test fails and you say --never-drop-acls
then it just exits with a fatal error.


--
Ben Escoto

Dear Ben,

Does it use the Mac OS X specific command /usr/sbin/fsaclctl command?
If that is the case it would fail as the OS probably stores the ACL
enabled status at the root of the volume.

I tested it with python and manually and it works with all the
folders/ files within the ACL enabled volumes as expected! Given
this, I do not understand why rdiff-backup should bail out as it is
python based and uses pylibacl.

With many thanks.

Best regards,
Murali.


On 31 Oct 2005, at 02:21 am, Ben Escoto wrote:

Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Sun, 30 Oct 2005 17:16:18 +0000

Could this be the cause? - Is rdiff-backup testing for acl ability
at the source and destination directory instead of the respective
volume root?



Sun Oct 30 16:10:09 2005 ACLs not supported by filesystem at /
Users/
muralikv/Desktop


Yes, if you are trying to back up /Users/muralikv/Desktop it will test
that very directory. If that test fails and you say --never-drop-acls
then it just exits with a fatal error.


--
Ben Escoto

Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Mon, 31 Oct 2005 02:46:48 +0000

Does it use the Mac OS X specific command /usr/sbin/fsaclctl command?
If that is the case it would fail as the OS probably stores the ACL
enabled status at the root of the volume.

Oh, no it "manually" tries to read ACL information from that directory
with pylibacl. Here is the relevant code:

try: posix1e.ACL(file=rp.path)
except IOError:
log.Log("ACLs not supported by filesystem at %s" % (rp.path,), 4)
self.acls = 0
else: self.acls = 1

since you got the error "ACLs not supported by filesystem at
/Users/muralikv/Desktop", then rdiff_backup tried to run

posix1e.ACL(file="/Users/muralikv/Desktop")

and got an IOError.


--
Ben Escoto

Ben Escoto wrote:
Murali Vadivelu <mkv22 < at > cam.ac.uk>
wrote the following on Mon, 31 Oct 2005 02:46:48 +0000

Does it use the Mac OS X specific command /usr/sbin/fsaclctl command?
If that is the case it would fail as the OS probably stores the ACL
enabled status at the root of the volume.

Oh, no it "manually" tries to read ACL information from that directory
with pylibacl. Here is the relevant code:

try: posix1e.ACL(file=rp.path)
except IOError:
log.Log("ACLs not supported by filesystem at %s" % (rp.path,), 4)
self.acls = 0
else: self.acls = 1

I have ACLs enabled on my Tiger system and have noticed that pylibacl
throws an IOError when you attempt to read the ACL for a file/dir that
does not have an ACL set yet eg.

aross-laptop:~ aross$ mkdir -p test/acltest

aross-laptop:~ aross$ ls -le test
total 0
drwxr-xr-x 2 aross aross 68 Oct 31 14:50 acltest

aross-laptop:~ aross$ python -c 'import posix1e; acl =
posix1e.ACL(file="acltest")'
Traceback (most recent call last):
File "<string>", line 1, in ?
IOError: [Errno 2] No such file or directory

aross-laptop:~ aross$ chmod +a "admin allow delete" acltest

aross-laptop:~ aross$ ls -le test
drwxr-xr-x + 2 root aross 68 Oct 31 14:52 acltest
0: group:admin allow delete

aross-laptop:~ aross$ python -c 'import posix1e; acl =
posix1e.ACL(file="acltest")'

[ no expection thrown]

I don't know if this is a bug in pylibacl or a case of Apple not
sticking to the standard.

Cheers

Andrew Ross
IT Officer
Whitley College

Ph: (03) 9340 8008

Andrew Ross <aross < at > whitley.unimelb.edu.au>
wrote the following on Mon, 31 Oct 2005 14:58:13 +1100

I have ACLs enabled on my Tiger system and have noticed that pylibacl
throws an IOError when you attempt to read the ACL for a file/dir that
does not have an ACL set yet eg.

Thanks, I forwarded your report to the pylibacl author and will let
the list know if he gets back to me. In the meantime, feel free to
spend some quality time with the posix1e and pylibacl documentation ;)

Offhand I think this bug is probably too serious to try to work around
it in rdiff-backup, and plan to wait for the fix in pylibacl or
Darwin.


--
Ben Escoto