Re: ACLs

[Tim Bishop <tim-lists@bishnet.net>]

On Mon, Dec 09, 2013 at 02:41:11PM +0100, Mike Kallies wrote:
> Not sure if this is just an issue for me, but ACLs on tarsnap are
> giving me some trouble.
> 
> I cross-compiled Tarsnap to run on an ARM box for a QNAP appliance, it
> seems to work great.  The only problem is that ACLs are giving me
> trouble.
> 
> This is the original which was backed up then 'mv'ed to testfolder.orig:
> 
> [/share/MD0_DATA] # getfacl testfolder.orig/test.txt
> # file: testfolder.orig/test.txt
> # owner: mike
> # group: everyone
> user::rwx
> user:guest:---
> group::rwx
> group:dev:rwx
> group:bots:r-x
> mask::rwx
> other::rwx
> 
> This is the restore whcih was brought back to testfolder/test.txt
> (along with the whole directory)
> 
> [/share/MD0_DATA] # getfacl testfolder/test.txt
> # file: testfolder/test.txt
> # owner: mike
> # group: everyone
> user::rwx
> group::rwx
> other::rwx
> 
> 
> As you can see the ACLs seem to be stripped, this applies to all the
> other files and folders which were brought back.
> 
> Anyone have any suggestions as to what I might try to troubleshoot?
> Does anyone else have a problem with ACLs?  Did I break something
> cross-compiling?

What flags did you use when doing the restore? Did you use -p?

     -p      (x mode only) Preserve file permissions.  Attempt to restore the
             full permissions, including owner, file modes, file flags and
             ACLs, if available, for each item extracted from the archive.  By
             default, newly-created files are owned by the user running
             tarsnap, the file mode is restored for newly-created regular
             files, and all other types of entries receive default permis-
             sions.  If tarsnap is being run by root, the default is to
             restore the owner unless the -o option is also specified.

Tim.

-- 
Tim Bishop
http://www.bishnet.net/tim/
PGP Key: 0x6C226B37FDF38D55