{stroke in 2011 and now have BAD short-term memory loss}

What did I do, and how do I fix it?

I was using VIDEO on my movie archive {separate HDD} and then I just changed VIDEO to MOVIES, and everything turned bad

The following error message told me that I have a problem:

"rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1327) [sender=3.2.6]"

Now when I add/change/rename a MOVIE it doesn't do a {darn} thing to the backup.

Yet again:
1: what did I do?
2: how can I fix it, via rsync?

Thank you for your assistance in this matter, and have a wonderful day!

OK, I did a "--perms" in/on my rsync scripts, to no avail

Please explain with more detail. What do you mean by VIDEO or MOVIES?

What type of filesystem is on the destination?

Is the separate hard drive internal or external?

michaelk:

They are directory names.
What was once VIDEOS was renamed to MOVIES.

Yeah.... I guess I did it to myself, BUT I still cannot fix it {yet}.

Thank you for your time, and have a great day!

Windows to Linux? Increase the verbosity, it most likely the character set or filesystem type.

The directory in question is on /dev/sdb1.
The / directory mounted on /dev/nvme0n1p4, though.
Actually almost everything is mounted on /dev/nvme0n1p4 except for the HHDs they are mounted on /dev/sda1, /dev/sda2, /dev/sdb1, /dev/sdb2, and /dev/sdc.

{{PS: I have a 1TB SSD and 12TB HDD-space}}

{yeah... I backup 1-2 times a day}

Post the exact rsync line you are using to backup.

What filesystem is on /dev/sdb1?

elgrandeperro:

but I did a --perms for every rsync and it didn't help!

I spent some time a few minutes ago, and I went through my rsync string in detail.
It still does not fix this error, so I am reduced to manually using dolphin {the KDE file manager} to do the damnable backups.
However, the updates work as usual... go figure!

Have yourself a Merry Christmas!

OK, I have scaled down my rsync command to the following:

"~$ rsync --archive --verbose --stats --delete-after --recursive /MOVIES /media/kevin/{UUIDnumber}/"

but there is a problem with my file manager results.

under {UUIDnumber} I get size 2.1 TiB (2,325,753,782,125) 7,635 files, 516 sub-folders
and under {/MOVIES} I get size 2.1 TiB (2,325,753,806,701) 7,635 files, 516 sub-folders

the difference is approximately 0.97% but the same exact files and sub-directories, BUT NO ERROR!

What can account for this difference?
Should I worry about it?
what do y'all think?

{{PS: I lived in Tennessee for three years, which allows me the super-power to say y'all without being embarrassed }}

OK, I am now calling this as [solved]


Thank you for any help you have given me, and have a Fantastic Christmas!

In your new thread
https://www.linuxquestions.org/quest...re-4175720063/
you say
This tells you that errors were reported during the transfer and this message is a summary telling you there were errors.

To find out exactly what files had errors and what those errors were you would need to parse the output given when rsync was running and find the error so you could tell what needs to be done to fix it.

OK... I have changed the [SOLVED] tag back to UNSOLVED
========

Again, I have checked my rsync command and the changed files have NOT been migrated to my backup HDD.

{{This is upsetting me, since I have been using my current backup command to save my butt when I need it, and my rsync command hasn't been changed since 2013, and now, all of a sudden, my rsync command is disrespecting me!}}

Just to cover all bases,

Is it possible that the backup drive partition is full so the update cannot be completed? Does not seem likely but without knowing partition sizes cannot be sure.

Is there a possible permissions issue that prevents the update from proceeding? This would include either a different ownership, rw permissions, or even permissions on the entire path.

Would you please post the output of 'lsblk -f' in a code block so we can see details on the devices and maybe have a better picture to work from.

Short solution: I did this to myself.
===
Long solution: Oh God, yet another learning experience!

Like I had said, I have been using my rsync since 2013, I had made a modification when computer "gave up the ghost" in January 2022, and made a solution when my username directory was in /home/PUBLIC/kevin.

Then I finally got around to using usermod, and had /home/kevin was my new user BUT I FORGOT TO CHANGE THE RSYNC command to take the change in where my user became!!!!!

I changed /home/PUBLIC/kevin back to /home/kevin. I just ran my rsync command and yet again, it works perfectly.

Lesson learned, FINALLY.

Everybody, have a great day and a wonderful Christmas!