On Fri, 22 Mar 2024, Tomas Kuchta wrote:
Errors with rsync usually mean that the file system changed - such as logs,
proc, sys, var, etc.
Tomas,
I thought this might be the cause. While I did nothing in the partitions
being sync'd the kernel or some other application might have made a change.
On Thu, Mar 21, 2024, 13:20 MC_Sequoia wrote:
> "I worry that the copy omitted content. Especially when the size reported
> as copied doesn't match the size of something like "du -s""
>
> rsync = remote synchronization of local & remote files. If there's no
> delta, there's no need to sync the fi
"I worry that the copy omitted content. Especially when the size reported as
copied doesn't match the size of something like "du -s""
rsync = remote synchronization of local & remote files. If there's no delta,
there's no need to sync the files.
On Thu, 21 Mar 2024, Michael Ewan wrote:
As others have said, capture the output, but instead of a pipe use
'--log-file=rsync.log' option. Also, when you run rsync the second time it
should only log the errors since all the files have been copied already.
Michael,
Good point. Will do so.
Th
On Thu, 21 Mar 2024, King Beowulf wrote:
you can tee stdout to a file
Ed,
True that. Didn't occur to me as I was focused on getting that replacement
drive set up.
$ rsync blah-blah 2>&1| | tee rsync.log
I'll do this the next new disk update.
Thanks,
Rich
"you can tee stdout to a file
>
> $ rsync blah-blah |2>&1| | tee rsync.log
"|2>&1" grabs both stdout and stderr. Now you can view rsyn.log at your
leisure."
Additionally, you can use -vv to increase verbosity and use -q so that only
errors get written out to a log file. Also, using the -n optio
On 3/20/24 17:19, Rich Shepard wrote:
> On Wed, 20 Mar 2024, wes wrote:
>
>> why wait a few days? you could run rsync again immediately and you can
>> look for errors.
> wes,
>
> Two reasons:
>
> 1) I'm waiting for the weekend to replace the desktop's internal hard drive.
> I'll run rsync the
On Wed, 20 Mar 2024, wes wrote:
why wait a few days? you could run rsync again immediately and you can
look for errors.
wes,
Two reasons:
1) I'm waiting for the weekend to replace the desktop's internal hard drive.
I'll run rsync then to update what changed from today.
2) The list o
After running for about an hour rsync ended this way:
-
sent 181,880,754,804 bytes received 1,336,778 bytes 43,642,973.39 bytes/sec
total size is 181,831,399,934 speedup is 1.00
rsync error: some files/attrs were not transferred (see previous errors) (code
23) at main.c(1327) [sender=3.2.5
