You are not logged in.
Pages: 1
Dear experts,
I have used rsync (grsync actually) to make backups for years. It has worked like a charm. I use three USB-HDDs that I rotate between. Maybe not the most 'modern' solution but it works for me.
Today was the day for yet another backup.
Now rsync hangs after a short while. According to the messages it is skipping irregular files (conda something or the other) when it stalls.
I get no error messages. It just stops making progress.
The HDD I use has more than 300 GB of free space. When accessing it manually (using Thunar) it responds normally. I can see that new files have not been backed up.
I don't use the computer while taking backups.
I upgraded my system earlier today and is running kernel 7.0.10+deb13-amd64.
Firing up btop I see several rsync instances but none is doing anything. If I kill the backup process in grsync and close grsync I see no change in btop. I can kill some, but not all, rsync instances from btop.
I can't unmount the HDD as a rsync process is accessing it.
I have found this 'help': https://rsync.samba.org/issues.html
I am none the wiser for that as I don't see any correlation to my experience of using a process and equipment I have used successfully so many times suddenly fail.
Any leads would be appreciated.
TIA
/Martin
"Problems worthy of attack
prove their worth by hitting back."
Piet Hein
Offline
What is the full error message from grsync?
Can you run the rsync command from the terminal and then post the full error message.
You must unlearn what you have learned.
-- yoda
Offline
There was no error message!
I have re-booted my computer using an older kernel (6.1.0-21-amd64). Now the backup works just fine. I don't know if the kernel is causing this or if this was just a dumb luck thing.
I see later versions of rsync are derided on internet fora. They have been updated using Claude-generated code. As far as I have seen so far, the rsync version I use should not be a victim of this practice.
/Martin
"Problems worthy of attack
prove their worth by hitting back."
Piet Hein
Offline
What's the full message when this happens:
According to the messages it is skipping irregular files (conda something or the other) when it stalls.
Although it appears to be an issue with the kernel.
You must unlearn what you have learned.
-- yoda
Offline
Pages: 1