From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] rsync not deleting removed directory and drive PW DIS 3.3v question
Date: Sat, 3 Sep 2022 22:18:02 +0200 [thread overview]
Message-ID: <YxO2eroXKVuYAu8E@kern> (raw)
In-Reply-To: <98d16301-9555-10de-6828-ceab211f6eed@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
Am Fri, Sep 02, 2022 at 03:35:56AM -0500 schrieb Dale:
> time rsync -auv --progress --delete /home/dale/Desktop/Crypt/Video/*
> /mnt/10tb/Video/
A little OT, but still related:
Instead of -v, give -i a try. -v only shows you the path of synced files. In
addition to that, -i also shows you *why* a file is synced and what exactly is
synced (the whole file, or only permissions or timestamps or other attributes).
An example:
## create source and destination dir, and a source file
$ mkdir a b
$ touch a/foo
## rsync the -v way
$ rsync -av a/ b/
sending incremental file list
./
foo
## update timestamp of first file, create another file, and rsync with -i
$ touch a/{foo,bar}
$ rsync -ai a/ b/
.d..t...... ./
>f+++++++++ bar
>f..t...... foo
See what it did there? Rsync tells you that it copied the new file "bar",
but "foo" only had its timestamp changed, the same as for the root dir,
because we added a file to it.
--
Grüße | Greetings | Salut | Qapla’
Please do not share anything from, with or about me on any social network.
Three nuns cycle along a country road.
1: “I’ve never come this way before.”
2: “It’s the cobblestones.”
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-09-03 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 8:35 [gentoo-user] rsync not deleting removed directory and drive PW DIS 3.3v question Dale
2022-09-02 9:27 ` Arve Barsnes
2022-09-02 10:53 ` Ramon Fischer
2022-09-02 20:29 ` Sebastiaan L. Zoutendijk
2022-09-02 23:43 ` Dale
2022-09-03 20:18 ` Frank Steinmetzger [this message]
2022-09-05 19:46 ` Dale
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=YxO2eroXKVuYAu8E@kern \
--to=warp_7@gmx.de \
--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