Bullseye: raspiBackup terminates with RC23 if type rsync is used and backup space is a nfs partition

[framps]

Root cause is that /var/log/journal now has ACLs

[bastelbert]

Errors on Raspberry Pi 4 with latest Bullseye and raspiBackup.sh 0.6.6.1:

20211112-013013 DBG 1981: --- Redirect: & - Skips: rsync: [generator] set_acl: sys_acl_set_file(var/log/journal, ACL_TYPE_ACCESS): Operation not supported (95) rsync: [generator] set_acl: sys_acl_set_file(var/log/journal/3e23e34d17484a28b9473f69f7d9d21c, ACL_TYPE_ACCESS): Operation not supported (95) rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/3e23e34d17484a28b9473f69f7d9d21c/.system.journal.8pTVZn, ACL_TYPE_ACCESS): Operation not supported (95) rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/3e23e34d17484a28b9473f69f7d9d21c/.system@0005cf904280e339-4b09e06bb02c79ac.journal~.j2Q8Jp, ACL_TYPE_ACCESS): Operation not supported (95) rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/3e23e34d17484a28b9473f69f7d9d21c/.system@0005d08251e08f15-891128351680d704.journal~.Wxd60n, ACL_TYPE_ACCESS): Operation not supported (95) rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/3e23e34d17484a28b9473f69f7d9d21c/.system@0005d083451f4562-ea8192744cbc848d.journal~.fU4w4o, ACL_TYPE_ACCESS): Operation not supported (95) rsync: [receiver] set_acl: sys_acl_set_file(var/log/journal/3e23e34d17484a28b9473f69f7d9d21c/.user-1000.journal.dIbQpp, ACL_TYPE_ACCESS): Operation not supported (95) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]

[framps]

@bastelbert Looks like you are an early bird 😆 .

I'm still in the evaluation phase...

But there is a workaround:

If you are not interested in /var/log/journal (Only people which do Linux debugging will need the journal actually) just exclude /var/log/journal from the backup. To exclude the directory just update following line in /usr/local/etc/raspiBackup.conf:

DEFAULT_EXCLUDE_LIST="--exclude=/var/log/journal"

See man journald.conf for details how journaling works

You also can pass following option to raspiBackup:

-u "\--exclude=/var/log/journal"

to exclude the persistent journal from backup.

[framps]

I just learned all previous RaspiOS images which can be downloaded from raspberrypi.com don't include /var/log/journal and therefore there was no issue with ACLs. But now the Bullseye image includes /var/log/journal (not sure whether by intention or by mistake) which causes the issue now.

[framps]

Read this article which explains why Debian decided to enable persistent journal in Bullseye.

[bastelbert]

DEFAULT_EXCLUDE_LIST="--exclude=/var/log/journal"

Thanks for your great support, works now!

[framps]

Fixed the issue in 5635776.

@bastelbert Would you like to verify the fix? Please download https://raw.githubusercontent.com/framps/raspiBackup/bullseye/raspiBackup.sh into /home/pi .

Then change

DEFAULT_EXCLUDE_LIST="--exclude=/var/log/journal"

to
DEFAULT_EXCLUDE_LIST=""

and finally execute

sudo bash ./raspiBackup.sh

(note the leading dot 😉 )

[bastelbert]

Cool, thank you! I can confirm that the fix works on my RasPi4.