Frank Steinmetzger wrote:
> 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.
>
>
While it may be a tiny bit off topic, not that I mind, it is certainly
interesting. I added the i to the commands to see what info it
included. Then I googled for more details on what things meant. It
shows a d for directory, t for time stamp change etc etc. While I
rarely use dry-run, it is still neat to see why it is doing something.
It doesn't take up much room but does provide lots of info. So, while
it may be of more use if I were using dry-run, I'm still adding it.
I might add, I got all my so called scripts updated and it is deleting
removed stuff like I expect. It also hit me why it would add but not
delete. It would add because there were files inside those
directories. It had to create one to update the other. However, if I
removed the directory, well, it wasn't exactly looking since my method
was telling it not too. ;-)
For anyone running up on this, the same logic of trailing / or * will
likely apply to cp or scp as well.
I also had a brain storm about my new 14TB drive. I'm going to make it
my backup drive in place of the 10TB which is almost full already. I'll
replace a 8TB with the 10TB, which is well tested by now, and it will
add more space. Later on, maybe another 14TB and remove a 8TB or
something. As I'm doing this, I'm building up a stock pile of spare
drives, either in the event of a failure or building a nifty new
machine. o_O
I just wish I had a better way of tracking passwords for encrypted
drives. I have a different one for each drive with similar methodology
but no one else would likely guess what they are. Plus, they are very
secure according to several password checker websites. Still, good
passwords tend to also be hard to remember. The more passwords one has,
the harder it gets. Having a tool sort of defeats the purpose so not
sure of a better way.
Thanks to all. Backups are looking great, I just have to do them more
often with this faster internet. ;-)
Dale
:-) :-)
