<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Frank Steinmetzger wrote:<br>
</div>
<blockquote type="cite" cite="mid:ZRBq1xQAKIJdaaGs@kern">
<pre class="moz-quote-pre" wrap="">Am Sat, Sep 23, 2023 at 02:30:32PM -0500 schrieb Dale:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre class="moz-quote-pre" wrap="">I read the other replies and I think it is caching the data, the drives
writes and catches up and then it asks for more data again.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Tool tip: dstat
It puts out one line of values every x seconds (x == 1 by default).
With arguments you can tell it what to show. To see disks in action, I like
to run the following during upgrades that involve volumous packages:
dstat --time --cpu --disk -D <comma-list of disks you want to monitor> --net --mem-adv --swap'
The cpu column includes IO wait.
The disk columns show read and write volume. If you omit the -D option, you
will only see a total over all disks, which might still be enough for your
use case.
The mem-adv shows how much data is in the file system write cache (the --mem
option does not).</pre>
</blockquote>
<br>
<br>
Interesting command. Basic but shows some good info. While I been
recuperating, my backups finished. Now I can't test it as easily
until I need to update again, which is usually after my weekend OS
updates. May look into that again. I saved the command in my
frequent commands file. ;-)<br>
<br>
However, this may be something related to either LVM, the encryption
or both. I needed to copy a LARGE directory that is on the same rig
and on the same LV. I noticed while it was copying, gkrellm showed
the same behavior as it did when copying to the NAS box with rsync.
It would read a while, then write, read a while, then write and
repeat. I might add, by eye, it looked like about the same timing
as when copying to the NAS box. This seems to rule out network or
maybe even issues on the NAS box, unless this affects both at the
same time I guess. <br>
<br>
I have no idea how to track down the cause of this but at least this
should rule out some things, like network. At this point, this
looks like something I'm going to just have to live with. If it's
LVM, I can't fix it. If it's the encryption, I likely can't fix it
either. I may try the options posted by Tsukasa in another reply
but given this happens even when on the same rig, I doubt mount
options are going to change anything given the copy was on the same
rig and all. <br>
<br>
I guess it was worth looking into at least. Maybe. Just odd to
notice it doing the same thing even when on the same rig. :/<br>
<br>
Dale <br>
<br>
:-) :-) <br>
</body>
</html>