Rsynced fullbackup file .master.meta is not writeable by root
Hello, i am copying daily full backup files to a remote server using "rsync -av"
And then using tmpwatch to remove too old (144 hours) remote daily backups
tmpwatch -vvv --all -m 144 /destination/directory
The result:
[QUOTE]non-writeable file owned by root skipped: .master.meta
When i list one empty accounts directory permissions: [QUOTE] File: `/backup/abc/daily/2019-05-27/accounts/.' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 18h/24d Inode: 316964872 Links: 2 Access: (0711/drwx--x--x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-07 10:11:38.441892099 +0300 Modify: 2019-05-27 05:38:06.000000000 +0300 Change: 2019-06-07 10:11:10.781007910 +0300 File: `/backup/abc/daily/2019-05-27/accounts/..' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 18h/24d Inode: 316964870 Links: 3 Access: (0711/drwx--x--x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-07 10:05:58.000000000 +0300 Modify: 2019-05-27 05:00:02.000000000 +0300 Change: 2019-06-07 10:11:10.781007910 +0300 File: `/backup/abc/daily/2019-05-27/accounts/.master.meta' Size: 15289 Blocks: 32 IO Block: 4096 regular file Device: 18h/24d Inode: 316964877 Links: 1 Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-05-27 19:20:09.000000000 +0300 Modify: 2019-05-27 05:38:06.000000000 +0300 Change: 2019-05-27 19:20:09.298414600 +0300
Other files was removed by tmpwatch, but only this dotfile remains undeletable by tmpwatch. Which permission this dotfile must have in order the backups are restorable? I can change its permissions but i do not want to break something. How would you fix this so tmpwatch can delete the .master.meta dotfile?
When i list one empty accounts directory permissions: [QUOTE] File: `/backup/abc/daily/2019-05-27/accounts/.' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 18h/24d Inode: 316964872 Links: 2 Access: (0711/drwx--x--x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-07 10:11:38.441892099 +0300 Modify: 2019-05-27 05:38:06.000000000 +0300 Change: 2019-06-07 10:11:10.781007910 +0300 File: `/backup/abc/daily/2019-05-27/accounts/..' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 18h/24d Inode: 316964870 Links: 3 Access: (0711/drwx--x--x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-06-07 10:05:58.000000000 +0300 Modify: 2019-05-27 05:00:02.000000000 +0300 Change: 2019-06-07 10:11:10.781007910 +0300 File: `/backup/abc/daily/2019-05-27/accounts/.master.meta' Size: 15289 Blocks: 32 IO Block: 4096 regular file Device: 18h/24d Inode: 316964877 Links: 1 Access: (0400/-r--------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2019-05-27 19:20:09.000000000 +0300 Modify: 2019-05-27 05:38:06.000000000 +0300 Change: 2019-05-27 19:20:09.298414600 +0300
Other files was removed by tmpwatch, but only this dotfile remains undeletable by tmpwatch. Which permission this dotfile must have in order the backups are restorable? I can change its permissions but i do not want to break something. How would you fix this so tmpwatch can delete the .master.meta dotfile?
-
Hi @postcd If you modify that command to add the -f flag (can be -vvvf) does it change the behavior? I'm curious because .master.meta is a root owned hidden file. 0 -
-f flag worked. Thank you -f, --force Remove files even if root doesn"t have write access (akin to rm -f).0 -
That's what I was hoping for! Happy to hear it and thanks for following up @postcd 0
Please sign in to leave a comment.
Comments
3 comments