From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Copying root to SSD in one go...a good idea...or?
Date: Sun, 5 Apr 2020 14:25:51 -0500 [thread overview]
Message-ID: <79d0c1d4-78c7-8705-8e05-a6094f3652fc@gmail.com> (raw)
In-Reply-To: <20200405183704.djcsxqtnrn2equd5@solfire>
tuxic@posteo.de wrote:
>
> ...I just wanted to check, whether there is water in the pool... :)
>
> I minute ago I found this:
> https://unix.stackexchange.com/questions/203018/interrupting-rsync-with-ctrl-c-should-i-use-partial-or-append
>
> which rises a question about how to resume an interrypted
> rsync-session.
> It looks like the final answer was not found...
>
> Any additional ideas about that?
> Cheers!
> Meino
>
I have interrupted rsync quite a few times and never had it fail on
resume. I've tested it to be sure. I always use the -v and --progress
options so I can watch what it is doing. If I restart it, it picks up
right where it left off, if no other files have changed since I stopped
it. On occasion Seamonkey or Firefox will write to a file and it
catches those too but it updates the file it was stopped on and either
completes it or updates it one. I don't know about the technical answer
but that's my experience with it.
Another thing, if you do have to stop it and feel the need, rerun it
with a complete run afterwords to let it double check. If nothing
changes, you should be fine. Using du to check data sizes may help to,
although sometimes different file systems can change those.
Just a couple thoughts.
Dale
:-) :-)
next prev parent reply other threads:[~2020-04-05 19:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 17:12 [gentoo-user] Copying root to SSD in one go...a good idea...or? tuxic
2020-04-05 17:33 ` Mark Knecht
2020-04-05 17:54 ` tuxic
2020-04-05 18:08 ` Dale
2020-04-05 18:29 ` Neil Bothwick
2020-04-05 19:09 ` Dale
2020-04-05 19:28 ` Neil Bothwick
2020-04-05 19:43 ` Dale
2020-04-05 18:39 ` tuxic
2020-04-05 19:19 ` Dale
2020-04-05 18:12 ` Mark Knecht
2020-04-05 18:37 ` tuxic
2020-04-05 19:25 ` Dale [this message]
2020-04-05 19:29 ` Neil Bothwick
2020-04-05 20:05 ` [gentoo-user] " Grant Edwards
2020-04-05 18:22 ` [gentoo-user] " Michael
2020-04-05 19:03 ` tuxic
2020-04-05 19:31 ` Neil Bothwick
2020-04-05 18:41 ` J. Roeleveld
2020-04-05 20:12 ` tuxic
2020-04-06 6:06 ` William Kenworthy
2020-04-06 13:35 ` [gentoo-user] " Grant Edwards
2020-04-06 14:19 ` Jack
2020-04-06 14:34 ` Grant Edwards
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=79d0c1d4-78c7-8705-8e05-a6094f3652fc@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