From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Permission error when trying to rsync over nfs
Date: Wed, 28 May 2025 07:58:18 -0500 [thread overview]
Message-ID: <6fea8d7a-f00c-908e-0b9c-9e1b30096138@gmail.com> (raw)
In-Reply-To: <cb44c8cd-e903-d8f9-932d-4e3279091e54@gmail.com>
Dale wrote:
> I did some digging. I found some info on rsync to a networked system.
> I switched to that method. This is the command I used.
>
>
> time rsync -uivr --progress /home/dale/Desktop/Data/*
> root@10.0.0.5:/mnt/backup
>
>
> My old way did act odd. It would read a lot of data from the main rig,
> transfer across the network and then write to the NAS drive. Then
> repeat. It did not do it in a continuous way tho. It did them one at a
> time. Read a while. Transfer. Then write a while. Repeat. Overall,
> it was kinda slow, ish.
>
> With this new method it is doing it all at the same time in a continuous
> flow but slower. I think the NAS box is slowing things down as it
> doesn't have AES built into the CPU like my other boxes do. When it
> writes to the drive, all the CPU cores max out. I think it would be
> faster if the NAS box could handle encryption better. It would then be
> faster overall as well. The NAS box is basically the bottleneck.
>
> I may start doing this with my backups as well. Then again, I got all
> my scripts set up for nfs already.
>
> Dale
>
> :-) :-)
>
I found something interesting. I bought some extra hard drives over the
past few months. I'm moving data around. Anyway, I have mentioned that
the old NAS box CPU doesn't support AES in the CPU like my old rig or my
new main rig. I've often wondered just what difference that makes. To
do one of my moves, I connected two sets of drives, both encrypted, to
the NAS box. I'm copying the data from one drive set to the other.
Nothing fancy, just a rsync copy. The copy process shows data moving at
about a 70MB/sec rate. According to htop, all CPU cores are almost
maxed out and at times are maxed out.
So, if anyone wonders what difference it makes between a CPU with and
without AES support and encrypted drives, it makes a lot of difference.
I've done this before on my old rig and on my new rig, CPU is almost
idle. Transfer speed is almost the max the drives can do.
I just wanted to add this tidbit of info. I might add, without
encryption, the NAS box can max out the data transfer of the drive
itself. The difference is encryption and lack of AES support in the CPU.
Oh, the 20TB drive with the slow to respond problem is now in my main
rig. By the time I boot up and get ready to unlock the drive, they have
had plenty of time to spin up, likely 2 or 3 minutes at least. Oh, I
ordered another 20TB drive. Gonna see if it does the same thing.
Dale
:-) :-)
next prev parent reply other threads:[~2025-05-28 12:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 13:39 [gentoo-user] Permission error when trying to rsync over nfs Dale
2025-05-20 11:46 ` Michael
2025-05-20 13:27 ` Dale
2025-05-20 14:02 ` Michael
2025-05-20 16:30 ` Dale
2025-05-21 18:16 ` Michael
2025-05-21 19:42 ` Dale
2025-05-21 20:03 ` Michael
2025-05-26 10:09 ` Dale
2025-05-28 12:58 ` Dale [this message]
2025-05-30 23:35 ` Frank Steinmetzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fea8d7a-f00c-908e-0b9c-9e1b30096138@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox