Le 17/07/2023 à 09:38, Andrei Borzenkov a écrit :

And post full output including the complete command line, not some random lines of unknown command.

I can't share private data :-( on my "test" folder, I add a "fichier.txt" empty file: with -rv: jdd@localhost:~> rsync -rv --delete -e ssh --exclude .dtrash /run/media/jdd/Seagate_6To/multimedia/retouches-gallerie/test/ jdanield@olium.o2switch.net:/home6/jdanield/galleries/test/ sending incremental file list Fichier texte.txt sent 290 bytes received 42 bytes 221,33 bytes/sec total size is 56.921.540 speedup is 171.450,42 jdd@localhost:~> rsync -rv --delete -e ssh --exclude .dtrash /run/media/jdd/Seagate_6To/multimedia/retouches-gallerie/test/ jdanield@olium.o2switch.net:/home6/jdanield/galleries/test/ sending incremental file list Fichier texte.txt sent 290 bytes received 42 bytes 664,00 bytes/sec total size is 56.921.540 speedup is 171.450,42 same result on two successive runs :-) with -rvv (I masqued some data): jdd@localhost:~> rsync -rvv --delete -e ssh --exclude .dtrash /run/media/jdd/Seagate_6To/multimedia/retouches-gallerie/test/ jdanield@olium.o2switch.net:/home6/jdanield/galleries/test/ opening connection using: ssh -l jdanield olium.o2switch.net rsync --server -vvre.iLsfMasqued --delete . /home6/jdanield/galleries/test/ (10 args) sending incremental file list delta-transmission enabled 08-ladygaga.mp4 is uptodate pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg is uptodate Fichier texte.txt total: matches=1 hash_hits=1 false_alarms=0 data=0 sent 302 bytes received 194 bytes 992,00 bytes/sec total size is 56.921.540 speedup is 114.761,17 jdd@localhost:~> rsync -rvv --delete -e ssh --exclude .dtrash /run/media/jdd/Seagate_6To/multimedia/retouches-gallerie/test/ jdanield@olium.o2switch.net:/home6/jdanield/galleries/test/ opening connection using: ssh -l jdanield olium.o2switch.net rsync --server -vvre.iLsfMasqued --delete . /home6/jdanield/galleries/test/ (10 args) sending incremental file list delta-transmission enabled 08-ladygaga.mp4 is uptodate pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg is uptodate Fichier texte.txt total: matches=1 hash_hits=1 false_alarms=0 data=0 sent 302 bytes received 194 bytes 992,00 bytes/sec total size is 56.921.540 speedup is 114.761,17 the ladygaga jpg file is old, the Fichier.txt nex but only because it's done today, no change by me between the two runs thanks jdd -- c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet

Le 17/07/2023 à 13:10, Andrei Borzenkov a écrit :

On Mon, Jul 17, 2023 at 1:59 PM jdd@dodin.org <jdd@dodin.org> wrote: ...

...

jdd@localhost:~> rsync -rvv --delete -e ssh --exclude .dtrash /run/media/jdd/Seagate_6To/multimedia/retouches-gallerie/test/ jdanield@olium.o2switch.net:/home6/jdanield/galleries/test/ opening connection using: ssh -l jdanield olium.o2switch.net rsync --server -vvre.iLsfMasqued --delete . /home6/jdanield/galleries/test/ (10 args) sending incremental file list delta-transmission enabled 08-ladygaga.mp4 is uptodate pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg is uptodate Fichier texte.txt total: matches=1 hash_hits=1 false_alarms=0 data=0

So where is the problem? rsync compared the files and should not send the actual file content.

but why the Fichier.txt file is listed when it din't change? jdd -- c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet

Le 17/07/2023 à 13:45, Andrei Borzenkov a écrit :

And how is the remote side supposed to know that Fichier.txt did not change? Local side must send the list of files to check first.

of course it does jdd -- c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet

On 18.07.2023 00:52, Robert Webb via openSUSE Users wrote:

On Mon, 17 Jul 2023 14:45:55 +0300, Andrei Borzenkov <arvidjaar@gmail.com> wrote:

...

On Mon, Jul 17, 2023 at 2:29 PM jdd@dodin.org <jdd@dodin.org> wrote:

...

but why the Fichier.txt file is listed when it din't change?

And how is the remote side supposed to know that Fichier.txt did not change? Local side must send the list of files to check first.

Also, rsync is only guessing, really, by default.

That is incorrect and rsync output shown in this discussion demonstrates it.

Its 'quick check' algorithm looks for files that have changed in size or changed "significantly" in modification time. -- Robert Webb

On Mon, 17 Jul 2023 13:24:23 +0200, "jdd@dodin.org" <jdd@dodin.org> wrote:

Le 17/07/2023 à 13:10, Andrei Borzenkov a écrit :

...

On Mon, Jul 17, 2023 at 1:59 PM jdd@dodin.org <jdd@dodin.org> wrote: ...

...

jdd@localhost:~> rsync -rvv --delete -e ssh --exclude .dtrash /run/media/jdd/Seagate_6To/multimedia/retouches-gallerie/test/ jdanield@olium.o2switch.net:/home6/jdanield/galleries/test/ opening connection using: ssh -l jdanield olium.o2switch.net rsync --server -vvre.iLsfMasqued --delete . /home6/jdanield/galleries/test/ (10 args) sending incremental file list delta-transmission enabled 08-ladygaga.mp4 is uptodate pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg is uptodate Fichier texte.txt total: matches=1  hash_hits=1  false_alarms=0 data=0

So where is the problem? rsync compared the files and should not send the actual file content.

but why the Fichier.txt file is listed when it din't change?

I ran a test using the same filenames as yours, and with the '-i' (--itemize-changes) rsync option to show more info.  Created a 'b' hierarchy the same as 'a', except for the one file:   $ mkdir -p a/pwg_representative   $ touch a/{08-ladygaga.mp4,pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg}   $ cp -aT a b   $ touch a/'Fichier texte.txt'   $ rsync -r -ivv --delete -e ssh -- a/ b/   sending incremental file list   delta-transmission disabled for local transfer or --whole-file   .d          ./   .f          08-ladygaga.mp4   >f+++++++++ Fichier texte.txt   .d          pwg_representative/   .f          pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg   total: matches=0  hash_hits=0  false_alarms=0 data=0   sent 279 bytes  received 119 bytes  796.00 bytes/sec   total size is 0  speedup is 0.00 A second identical rsync run produces the same output except for this line:   >f..T...... Fichier texte.txt What the characters in the coded string mean:   .  not being updated (besides attributes)   +  the file is newly created   >  a file is being transferred to [ b ]   f  it's a file   d  it's a directory   T  the modification time will be set to the transfer time, which      happens when a file/symlink/device is updated without --times and      when a symlink is changed and the receiver can't set its time. So, the file 'Fichier texte.txt' is "transferred" (no data) because its modification time in the destination does not match that in the source. And that is because you used the '-r' (--recursive) option instead of '-a' (--archive, equivalent to -rlptgoD), which everybody else uses (already suggested by Masaru).  You got that from stackexchange? Shame on them! :-) Along with the '-a' option, '-H' is good to preserve hard links. Sometimes you may also want '-AX' to preserve ACLs and extended attributes.  I always use '-i', instead of '-v', to see what's going on. Forget rsync, though: [1] [1]  The Rolling Stones - Gimme Shelter (with Lady Gaga)      https://www.youtube.com/watch?v=Gd0YcFWlvOc -- Robert Webb

On 2023-07-18 03:06, Robert Webb via openSUSE Users wrote:

On Mon, 17 Jul 2023 13:24:23 +0200, "jdd@dodin.org" <jdd@dodin.org> wrote:

...

Le 17/07/2023 à 13:10, Andrei Borzenkov a écrit :

...

On Mon, Jul 17, 2023 at 1:59 PM jdd@dodin.org <jdd@dodin.org> wrote: ...

...

jdd@localhost:~> rsync -rvv --delete -e ssh --exclude .dtrash

...

...

but why the Fichier.txt file is listed when it din't change?

I ran a test using the same filenames as yours, and with the '-i' (--itemize-changes) rsync option to show more info.  Created a 'b' hierarchy the same as 'a', except for the one file:

Interesting. -i.

  $ mkdir -p a/pwg_representative   $ touch a/{08-ladygaga.mp4,pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg}   $ cp -aT a b   $ touch a/'Fichier texte.txt'

  $ rsync -r -ivv --delete -e ssh -- a/ b/   sending incremental file list   delta-transmission disabled for local transfer or --whole-file   .d          ./   .f          08-ladygaga.mp4   >f+++++++++ Fichier texte.txt   .d          pwg_representative/   .f          pwg_representative/20140721-col-auterive-rex-08-ladygaga.jpg   total: matches=0  hash_hits=0  false_alarms=0 data=0

  sent 279 bytes  received 119 bytes  796.00 bytes/sec   total size is 0  speedup is 0.00

A second identical rsync run produces the same output except for this line:

  >f..T...... Fichier texte.txt

What the characters in the coded string mean:   .  not being updated (besides attributes)   +  the file is newly created   >  a file is being transferred to [ b ]   f  it's a file   d  it's a directory

  T  the modification time will be set to the transfer time, which      happens when a file/symlink/device is updated without --times and      when a symlink is changed and the receiver can't set its time.

So, the file 'Fichier texte.txt' is "transferred" (no data) because its modification time in the destination does not match that in the source. And that is because you used the '-r' (--recursive) option instead of '-a' (--archive, equivalent to -rlptgoD), which everybody else uses (already suggested by Masaru).  You got that from stackexchange?

I must be low on morning tea. Why...? (I also use -a)

Shame on them! :-)

Along with the '-a' option, '-H' is good to preserve hard links. Sometimes you may also want '-AX' to preserve ACLs and extended attributes.  I always use '-i', instead of '-v', to see what's going on.

Forget rsync, though: [1]

[1]  The Rolling Stones - Gimme Shelter (with Lady Gaga)      https://www.youtube.com/watch?v=Gd0YcFWlvOc

-- Robert Webb

-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)

On 2023-07-18 12:37, Robert Webb via openSUSE Users wrote:

On Tue, 18 Jul 2023 10:39:45 +0200, "Carlos E. R." <robin.listas@telefonica.net> wrote:

...

On 2023-07-18 03:06, Robert Webb via openSUSE Users wrote:

...

   On Mon, 17 Jul 2023 13:24:23 +0200, "jdd@dodin.org" <jdd@dodin.org> wrote:

...

Le 17/07/2023 à 13:10, Andrei Borzenkov a écrit :

...

On Mon, Jul 17, 2023 at 1:59 PM jdd@dodin.org <jdd@dodin.org> wrote: ...

...

jdd@localhost:~> rsync -rvv --delete -e ssh --exclude .dtrash

...

...

...

So, the file 'Fichier texte.txt' is "transferred" (no data) because its modification time in the destination does not match that in the source. And that is because you used the '-r' (--recursive) option instead of '-a' (--archive, equivalent to -rlptgoD), which everybody else uses (already suggested by Masaru).  You got that from stackexchange?

I must be low on morning tea. Why...?

The critical difference between the rsync '-a' and '-r' options is that '-a' implies the '-t' (--times) option to preserve modification times, so the mtime on the destination file is set to be the same as the source file.  Whereas with '-r', the time is set to the current time ("transfer time"), like using 'cp' without the '-p' or other time-preserving option.

Ah, of course. Gottit :-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)

Thu, 10 Aug 2023 15:58:20 -0700 Carl Spitzer {L Juno} <lynux@juno.com> :

https://www.pragmaticlinux.com/2021/05/how-to-backup-your-home-directory-in-...

Someone had brought up the question of backing up before reinstall. Well this will help not bootable you just save what you want and you do not need to worry about Clonezilla or more complex solutions.

BTW as I remember there is still autoyast which allows you to make a automatic install for replicating installations already performed.

CWSIV

I use rsync to make full backups of data partitions which include home directories, example rsync -ahcEWXd /somepath/data /somepath/sc01 This will make a data folder such as /0/sc01/data which I then rename with date such as /0/sc01/data-2023-08-10 I've had issues backing up to existing backups and also using other switches but the above makes so far faultless 'new' copies. I keep sveral in row like little ducks going back half a dozen dates. My 100gb OS partitions I back up with dd creating 100gb image files which I extend with *.dd which tells me how I made them. dd if=/dev/sda8 of=/somepath/partition8-2023-08-10.dd When it counts (a backup isn't a backup if you can tell the difference or if you need the OS or app that made it to recover it) then you cannot beat dd.

Hi, all -- ...and then Carl Spitzer {L Juno} said... % ... % BTW as I remember there is still autoyast which allows you to make a % automatic install for replicating installations already performed. This is quite interesting. One of the biggest pains of an install is going through all of the selections and grabbing the extra software I like and so on. Where can I learn more about replicating my config on another machine? TIA :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

From: Dave Howorth <dave@howorth.org.uk> Date: Sat, 12 Aug 2023 11:58:02 +0100 On Sat, 12 Aug 2023 01:55:37 +0000 David T-G <davidtg-robot@justpickone.org> wrote:

This is quite interesting . ..

The first hit when I google for autoyast is https://doc.opensuse.org/documentation/leap/autoyast/single-html/book-autoya... and section 3.2.1 says "... create a profile containing the complete system configuration by launching YaST › Miscellaneous › Autoinstallation Cloning System or running sudo yast clone_system from the command line." Maybe that is what you want. One caveat: When I investigated Autoyast at my place of work 8 or so years ago, I found that the profile, a large XML document, was very machine-specific. In particular, it specifies the partitioning details, which makes it awkward to adapt to different machines, especially with the wildy varying stable of machines I had to support; I would have had to maintain a profile for each machine. In particular, my strategy with a new release has always been to do fresh installs rather than in-place upgrades, keeping the old installation available for rescue in case the system won't boot after an update. That would have required editing the profile for each system on every upgrade to change the root location, with the potential for big problems if I get it wrong. So I decided Autoyast wasn't going to save me enough time to be worth the trouble. Note also that (IIRC) it captures only what the installer actually installs. You still have to replace the default configuration files (Postfix, sshd, Apache, etc.) with your own. -- Bob Rogers http://www.rgrjr.com/

From: Georg Pfuetzenreuter via openSUSE Users <users@lists.opensuse.org> Date: Sat, 12 Aug 2023 19:55:00 +0200 On 8/12/23 19:36, Bob Rogers wrote:

One caveat: When I investigated Autoyast at my place of work 8 or so years ago, I found that the profile, a large XML document, was very machine-specific. In particular, it specifies the partitioning details, which makes it awkward to adapt to different machines . . .

This is if you use "clone_system", which, as the name suggests, clones the current system and generates a very big configuration containing all aspects of the running environment. You can either use that template and strip out parts you don't need on other systems or write a custom profile from scratch. Most of the options which can be set are not required to be set and can either be omitted or replaced by the "semi-automatic" alternatives (for example, you can have the user be prompted to make a partitioning choice whilst leaving package decisions automated). There are also more advanced implementations where parts of the profile are generated dynamically based on machine specific data stored in a central place. Then my experience is out of date (I had wondered if it might be). -- Bob

* jdd@dodin.org <jdd@dodin.org> [08-12-23 16:11]:

Le 12/08/2023 à 19:36, Bob Rogers a écrit :

...

One caveat: When I investigated Autoyast at my place of work 8 or so years ago, I found that the profile, a large XML document, was very machine-specific.(...)

that's the reason why, recently, I switched all my machines to Thumbleweed. TW is mature enough to be very stable. It's much easier now (was not 10 years ago, remember "evergreen" :-) than to upgrade from 15.x to 15.y.

And I start from fresh when I build a new machine, usually I don't have exactly the same tasks to do on the new one than I had, then not exactly the same software. I just keep somewhere a list of the special soft I really need (think of "detox", for example)

and, contrary to many beliefs, one may delay rebooting until it is convenient. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

On 8/12/23 10:36, Bob Rogers wrote:

In particular, my strategy with a new release has always been to do fresh installs rather than in-place upgrades, keeping the old installation available for rescue in case the system won't boot after an update.

I also did fresh-install releases for many years.  But a  year or so ago I started doing the in-place upgrades and haven't encountered any problems.  Fresh installs were always a PITA when porting the configuration files over, not to mention that the UID and GID numbers got scrambled. I run about 30 machines, and in-place upgrades have saved me lots of time without issue.  Of course, YMMV. But as usual, make sure you have up-to-date and reliable backups! Regards, Lew