--dry-run won't say where the files are going to go

2018-12-30 Thread 積丹尼 Dan Jacobson via rsync
Try as we may (--dry-run), it still won't tell us where it intends to put the files, $ rsync --dry-run --remove-source-files --relative --verbose --itemize-changes -Cavz Maildir/new /tmp/ sending incremental file list delta-transmission disabled for local transfer or --whole-file cd+

Re: --dry-run won't say where the files are going to go

2018-12-30 Thread Kevin Korb via rsync
/tmp/Maildir/new/1546157908.1392_1.jidanni7 Also, don't use -z on a local copy. Rsync is dumb enough to do what you tell it to. On 12/30/18 3:40 AM, 積丹尼 Dan Jacobson via rsync wrote: > Try as we may (--dry-run), it still won't tell us where it intends to put the > files, > > $ rsync --dry-run

Re: rsync remote raw block device with --inplace

2018-12-30 Thread Kevin Korb via rsync
There have been addons to rsync in the past to do that but rsync really isn't the correct tool for the job. Neither is dd. The right tool is something that understands the filesystem within the block device such as ntfsclone (what I use) or partimage (if you have ever used Clonezilla this is

Re: Aw: Re: rsync remote raw block device with --inplace

2018-12-30 Thread Kevin Korb via rsync
Rsync would only benefit you in terms of reducing network bandwidth (assuming it is even networking). The resulting file will be the size of the block device just like you get with dd[rescue]. You can tell rsync to write the file sparsely which would mean that any parts of the disk that have

rsync remote raw block device with --inplace

2018-12-30 Thread Steve Newcomb via rsync
It would be very nice to be able to rsync the raw data content of, e.g., a non-mounted disk partition, particularly in combination with --inplace. Our reality: several dual-boot machines running Windows during the day and Linux at night, during backups. Windows is very tedious and iffy to

Aw: Re: rsync remote raw block device with --inplace

2018-12-30 Thread devzero--- via rsync
> There have been addons to rsync in the past to do that but rsync really > isn't the correct tool for the job. why not correct tool ? if rsync can greatly keep two large files in sync between source and destination (using --inplace), why should it (generally spoken) not also be used to keep

Aw: Re: Re: rsync remote raw block device with --inplace

2018-12-30 Thread devzero--- via rsync
maybe this could also be useful: https://github.com/RyanHow/block2file > Gesendet: Sonntag, 30. Dezember 2018 um 22:52 Uhr > Von: "Rolf Fokkens via rsync" > An: rsync@lists.samba.org > Betreff: Re: Aw: Re: rsync remote raw block device with --inplace > > It was broucht up before indeed: >

Re: Aw: Re: rsync remote raw block device with --inplace

2018-12-30 Thread Rolf Fokkens via rsync
It was broucht up before indeed: https://lists.samba.org/archive/rsync/2012-June/027680.html On 12/30/18 9:50 PM, devzero--- via rsync wrote: There have been addons to rsync in the past to do that but rsync really isn't the correct tool for the job. why not correct tool ? if rsync can

--partial does not "unhide" the files

2018-12-30 Thread Heiko Schlittermann via rsync
Hi, I used --partial to transfer files from my local computer (rsync 3.1.2, Debian) to a remote computer (rsync 3.1.1 WD MyPassport Storage device) The files get transferred, but after successful transfer, the files are not renamed from . to . Where to go next? Here is the verbose output after