Greetings! During migrating i686 installation of ArchLinux to x86_64, all filesystem was rsynced to a new location. Maybe this somehow relates to the problem that has appeared after migrating and that did not happen before: during backuping the system, rsync reports the following error message: rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) The full log is as follows: [root at kw al]# /usr/bin/rsync --update -DHAErlptgo --relative --delete-during --verbose --itemize-changes /var/log/journal /mnt/backup/rootdir/ sending incremental file list rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) .d..t...... /var/log/ .d..tp..... /var/log/journal/ .d...p..... /var/log/journal/c892f90078ad480d902f236dfd220532/>f..t...... /var/log/journal/c892f90078ad480d902f236dfd220532/system.journal >f..t...... /var/log/journal/c892f90078ad480d902f236dfd220532/user-1000.journalcd+++++++++ /var/log/journal/remote/ sent 16,782,653 bytes received 169 bytes 6,713,128.80 bytes/sec total size is 119,537,664 speedup is 7.12 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] The 'remote' directory is empty on both source and destination. After deleting 'remote' directory on destination, it's recreated and the same error is reported. The source filesystem is ext4, the destination is on btrfs and is accessed via samba. Why can this message happen and how can this be corrected? Thanks. Albert.
If the filesystem doesn't support ACLs then don't use -A. Also, why is there samba between rsync and btrfs? On 06/23/2016 04:14 PM, Albert Berger wrote:> Greetings! > > During migrating i686 installation of ArchLinux to x86_64, all filesystem was rsynced to a new location. Maybe this somehow relates to the problem that has appeared after migrating and that did not happen before: during backuping the system, rsync reports the following error message: > > rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) > > The full log is as follows: > > [root at kw al]# /usr/bin/rsync --update -DHAErlptgo --relative --delete-during --verbose --itemize-changes /var/log/journal /mnt/backup/rootdir/ > sending incremental file list > rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) > .d..t...... /var/log/ > .d..tp..... /var/log/journal/ > .d...p..... /var/log/journal/c892f90078ad480d902f236dfd220532/ >> f..t...... /var/log/journal/c892f90078ad480d902f236dfd220532/system.journal >> f..t...... /var/log/journal/c892f90078ad480d902f236dfd220532/user-1000.journal > cd+++++++++ /var/log/journal/remote/ > > sent 16,782,653 bytes received 169 bytes 6,713,128.80 bytes/sec > total size is 119,537,664 speedup is 7.12 > rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] > > The 'remote' directory is empty on both source and destination. After deleting 'remote' directory on destination, it's recreated and the same error is reported. The source filesystem is ext4, the destination is on btrfs and is accessed via samba. Why can this message happen and how can this be corrected? > > Thanks. > > Albert. >-- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone: (407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. Kevin at FutureQuest.net (work) Orlando, Florida kmk at sanitarium.net (personal) Web page: http://www.sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/rsync/attachments/20160623/3dce67af/signature.sig>
On Thu, Jun 23, 2016 at 04:27:10PM -0400, Kevin Korb wrote:> If the filesystem doesn't support ACLs then don't use -A. >I did some search about this error before asking this question, and in other case unsupported ACLs were indeed the cause. But btrfs supports ACLs: [root at kw al]# getfacl /mnt/backup/rootdir/var/log/journal/remote getfacl: Removing leading '/' from absolute path names # file: mnt/backup/rootdir/var/log/journal/remote # owner: systemd-journal-remote # group: systemd-journal-remote # flags: -s- user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:group:wheel:r-x default:mask::r-x default:other::r-x> Also, why is there samba between rsync and btrfs? >The destination is on other machine. The samba is used because there are Windows machines in the local net. Albert.> On 06/23/2016 04:14 PM, Albert Berger wrote: > > Greetings! > > > > During migrating i686 installation of ArchLinux to x86_64, all filesystem was rsynced to a new location. Maybe this somehow relates to the problem that has appeared after migrating and that did not happen before: during backuping the system, rsync reports the following error message: > > > > rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) > > > > The full log is as follows: > > > > [root at kw al]# /usr/bin/rsync --update -DHAErlptgo --relative --delete-during --verbose --itemize-changes /var/log/journal /mnt/backup/rootdir/ > > sending incremental file list > > rsync: set_acl: sys_acl_delete_def_file(var/log/journal/remote): Operation not supported (95) > > .d..t...... /var/log/ > > .d..tp..... /var/log/journal/ > > .d...p..... /var/log/journal/c892f90078ad480d902f236dfd220532/ > >> f..t...... /var/log/journal/c892f90078ad480d902f236dfd220532/system.journal > >> f..t...... /var/log/journal/c892f90078ad480d902f236dfd220532/user-1000.journal > > cd+++++++++ /var/log/journal/remote/ > > > > sent 16,782,653 bytes received 169 bytes 6,713,128.80 bytes/sec > > total size is 119,537,664 speedup is 7.12 > > rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1178) [sender=3.1.2] > > > > The 'remote' directory is empty on both source and destination. After deleting 'remote' directory on destination, it's recreated and the same error is reported. The source filesystem is ext4, the destination is on btrfs and is accessed via samba. Why can this message happen and how can this be corrected? > > > > Thanks. > > > > Albert. > > > > -- > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., > Kevin Korb Phone: (407) 252-6853 > Systems Administrator Internet: > FutureQuest, Inc. Kevin at FutureQuest.net (work) > Orlando, Florida kmk at sanitarium.net (personal) > Web page: http://www.sanitarium.net/ > PGP public key available on web site. > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., >> -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html