Re: --partial does not "unhide" the files
I think --partial might be a red herring here. It only applies to what
happens when rsync is aborted in the middle of a file. What happens
without -P?
Also, it is worth trying with --inplace.
On 12/30/18 5:32 PM, Heiko Schlittermann via rsync wrote:
> 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 transferring an empty file
>
> heiko@blade:~/Pictures$ rsync -iavvvP ./x
> platte.local:/shares/Storage/Bilder\\\ von\\\ Heikos\\\ Computer/
> FILE_STRUCT_LEN=24, EXTRA_LEN=4
> cmd= machine=platte.local user= path=/shares/Storage/Bilder\
> von\ Heikos\ Computer/
> cmd[0]=ssh cmd[1]=platte.local cmd[2]=rsync cmd[3]=--server
> cmd[4]=-vvvlogDtpre.iLsfxC cmd[5]=--log-format=%i cmd[6]=--partial
> cmd[7]=. cmd[8]=/shares/Storage/Bilder\ von\ Heikos\ Computer/
> opening connection using: ssh platte.local rsync --server
> -vvvlogDtpre.iLsfxC "--log-format=%i" --partial .
> "/shares/Storage/Bilder\ von\ Heikos\ Computer/" (9 args)
> msg checking charset: UTF-8
> FILE_STRUCT_LEN=16, EXTRA_LEN=4
> (Server) Protocol versions: remote=31, negotiated=31
> (Client) Protocol versions: remote=31, negotiated=31
> sending incremental file list
> [sender] change_dir(/home/heiko/Pictures)
> [sender] make_file(x,*,0)
> [sender] flist start=1, used=1, low=0, high=0
> [sender] i=1 . x mode=0100644 len=0 uid=1000 gid=1000 flags=1005
> send_file_list done
> [sender] flist_eof=1
> file list sent
> send_files starting
> server_recv(2) starting pid=21983
> uid 1000(heiko) maps to 1000
> gid 1000(heiko) maps to 1000
> recv_file_name(x)
> received 1 names
> [Receiver] flist start=1, used=1, low=0, high=0
> [Receiver] i=1 1 x mode=0100644 len=0 uid=1000 gid=1000 flags=1000
> recv_file_list done
> [Receiver] flist_eof=1
> get_local_name count=1 /shares/Storage/Bilder von Heikos Computer/
> [Receiver] change_dir(/shares/Storage/Bilder von Heikos Computer)
> generator starting pid=21983
> delta-transmission enabled
> recv_generator(x,1)
> send_files(1, ./x)
> count=0 n=0 rem=0
> send_files mapped ./x of size 0
> calling match_sums ./x
> sending file_sum
> false_alarms=0 hash_hits=0 matches=0
> 0 100%0.00kB/s0:00:00 (xfr#1, to-chk=0/1)
> sender finished ./x
> generate_files phase=1
> recv_files(1) starting
> recv_files(x)
> got file_sum
> set uid of .x.VITBUv from 0 to 1000
> set gid of .x.VITBUv from 0 to 1000
> set modtime of .x.VITBUv to (1546208608) Sun Dec 30 14:23:28 2018
>
> send_files phase=1
> recv_files phase=1
> generate_files phase=2
> send_files phase=2
> send files finished
> total: matches=0 hash_hits=0 false_alarms=0 data=0
> recv_files phase=2
> recv_files finished
> generate_files phase=3
> generate_files finished
> client_run waiting on 9125
>
> sent 96 bytes received 874 bytes 1,940.00 bytes/sec
> total size is 0 speedup is 0.00
> [sender] _exit_cleanup(code=0, file=main.c, line=1196): entered
> [sender] _exit_cleanup(code=0, file=main.c, line=1196): about to call
> exit(0)
>
> Best regards from Dresden/Germany
> Viele Grüße aus Dresden
> Heiko Schlittermann
> --
> SCHLITTERMANN.de internet & unix support -
> Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
> gnupg encrypted messages are welcome --- key ID: F69376CE -
> ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 -
>
>
--
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
Kevin Korb Phone:(407) 252-6853
Systems Administrator Internet:
FutureQuest, Inc. ke...@futurequest.net (work)
Orlando, Floridak...@sanitarium.net (personal)
Web page: https://sanitarium.net/
PGP public key available on web site.
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
signature.asc
Description: OpenPGP digital signature
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--partial does not "unhide" the files
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 transferring an empty file
heiko@blade:~/Pictures$ rsync -iavvvP ./x
platte.local:/shares/Storage/Bilder\\\ von\\\ Heikos\\\ Computer/
FILE_STRUCT_LEN=24, EXTRA_LEN=4
cmd= machine=platte.local user= path=/shares/Storage/Bilder\
von\ Heikos\ Computer/
cmd[0]=ssh cmd[1]=platte.local cmd[2]=rsync cmd[3]=--server
cmd[4]=-vvvlogDtpre.iLsfxC cmd[5]=--log-format=%i cmd[6]=--partial cmd[7]=.
cmd[8]=/shares/Storage/Bilder\ von\ Heikos\ Computer/
opening connection using: ssh platte.local rsync --server
-vvvlogDtpre.iLsfxC "--log-format=%i" --partial . "/shares/Storage/Bilder\
von\ Heikos\ Computer/" (9 args)
msg checking charset: UTF-8
FILE_STRUCT_LEN=16, EXTRA_LEN=4
(Server) Protocol versions: remote=31, negotiated=31
(Client) Protocol versions: remote=31, negotiated=31
sending incremental file list
[sender] change_dir(/home/heiko/Pictures)
[sender] make_file(x,*,0)
[sender] flist start=1, used=1, low=0, high=0
[sender] i=1 . x mode=0100644 len=0 uid=1000 gid=1000 flags=1005
send_file_list done
[sender] flist_eof=1
file list sent
send_files starting
server_recv(2) starting pid=21983
uid 1000(heiko) maps to 1000
gid 1000(heiko) maps to 1000
recv_file_name(x)
received 1 names
[Receiver] flist start=1, used=1, low=0, high=0
[Receiver] i=1 1 x mode=0100644 len=0 uid=1000 gid=1000 flags=1000
recv_file_list done
[Receiver] flist_eof=1
get_local_name count=1 /shares/Storage/Bilder von Heikos Computer/
[Receiver] change_dir(/shares/Storage/Bilder von Heikos Computer)
generator starting pid=21983
delta-transmission enabled
recv_generator(x,1)
send_files(1, ./x)
count=0 n=0 rem=0
send_files mapped ./x of size 0
calling match_sums ./x
send_files phase=1
recv_files phase=1
generate_files phase=2
send_files phase=2
send files finished
total: matches=0 hash_hits=0 false_alarms=0 data=0
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished
client_run waiting on 9125
sent 96 bytes received 874 bytes 1,940.00 bytes/sec
total size is 0 speedup is 0.00
[sender] _exit_cleanup(code=0, file=main.c, line=1196): entered
[sender] _exit_cleanup(code=0, file=main.c, line=1196): about to call
exit(0)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 -
signature.asc
Description: PGP signature
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Aw: Re: Re: rsync remote raw block device with --inplace
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: > 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 greatly keep two large files in sync between source and > > destination > > (using --inplace), why should it (generally spoken) not also be used to > > keep two > > blockdevices in sync ? > > > > maybe these links are interesting in that context: > > > > https://lists.samba.org/archive/rsync/2010-June/025164.html > > > > https://github.com/dop251/diskrsync > > > > roland > > > >> Gesendet: Sonntag, 30. Dezember 2018 um 19:53 Uhr > >> Von: "Kevin Korb via rsync" > >> An: rsync@lists.samba.org > >> Betreff: Re: rsync remote raw block device with --inplace > >> > >> 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 what it uses). These will know how to skip > >> all the empty parts of the filesystem and will still be capable of > >> restoring a complete image in a bare metal restore. You can still use > >> dd to snag a copy of the MBR since that is outside of any filesystems. > >> > >> Also, if you do have to resort to a plain image use ddrescue instead of > >> dd. It has a status screen and it can resume as long as you used a log > >> file when you ran it. > >> > >> On 12/30/18 1:45 PM, Steve Newcomb via rsync wrote: > >>> 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 > >>> re-reinstall without a raw disk image to start from. Disks fail, and > >>> the ensuing downtime must be minimized. > >>> > >>> We're using dd for this. Most of the nightly work is redundant and > >>> wasteful of elapsed time and storage. Storage is cheap, but it's not > >>> *that* cheap. Elapsed time is priceless. > >>> > >>> Rsync refuses to back up raw devices, and even raw character devices, > >>> with the message "skipping non-regular file" (I think the relevant > >>> message is in generator.c). > >>> > >>> In Linux, anyway, the "raw" command allows a block device to be bound as > >>> a character device, and then even a "cat" command can read the raw data > >>> of the block device. So why does rsync refuse to copy such content, or > >>> why is it a bad idea, or what rsync doctrine conflicts with it? I agree > >>> there are security concerns here, but rsync already disallows some of > >>> its functions unless the super user is requesting them. > >>> > >>> > >> -- > >> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., > >>Kevin Korb Phone:(407) 252-6853 > >>Systems Administrator Internet: > >>FutureQuest, Inc. ke...@futurequest.net (work) > >>Orlando, Floridak...@sanitarium.net (personal) > >>Web page: https://sanitarium.net/ > >>PGP public key available on web site. > >> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., > >> > >> -- > >> Please use reply-all for most replies to avoid omitting the mailing list. > >> To unsubscribe or change options: > >> https://lists.samba.org/mailman/listinfo/rsync > >> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html > > > > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Aw: Re: rsync remote raw block device with --inplace
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 greatly keep two large files in sync between source and destination (using --inplace), why should it (generally spoken) not also be used to keep two blockdevices in sync ? maybe these links are interesting in that context: https://lists.samba.org/archive/rsync/2010-June/025164.html https://github.com/dop251/diskrsync roland Gesendet: Sonntag, 30. Dezember 2018 um 19:53 Uhr Von: "Kevin Korb via rsync" An: rsync@lists.samba.org Betreff: Re: rsync remote raw block device with --inplace 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 what it uses). These will know how to skip all the empty parts of the filesystem and will still be capable of restoring a complete image in a bare metal restore. You can still use dd to snag a copy of the MBR since that is outside of any filesystems. Also, if you do have to resort to a plain image use ddrescue instead of dd. It has a status screen and it can resume as long as you used a log file when you ran it. On 12/30/18 1:45 PM, Steve Newcomb via rsync wrote: 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 re-reinstall without a raw disk image to start from. Disks fail, and the ensuing downtime must be minimized. We're using dd for this. Most of the nightly work is redundant and wasteful of elapsed time and storage. Storage is cheap, but it's not *that* cheap. Elapsed time is priceless. Rsync refuses to back up raw devices, and even raw character devices, with the message "skipping non-regular file" (I think the relevant message is in generator.c). In Linux, anyway, the "raw" command allows a block device to be bound as a character device, and then even a "cat" command can read the raw data of the block device. So why does rsync refuse to copy such content, or why is it a bad idea, or what rsync doctrine conflicts with it? I agree there are security concerns here, but rsync already disallows some of its functions unless the super user is requesting them. -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Aw: Re: rsync remote raw block device with --inplace
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 never been written to would probably still contain nulls and would not be allocated but you will still be copying any deleted file data that still exists. Ntfsclone and partimage understand the filesystem. They will just skip the blocks that don't contain any current data. This will keep your backup file as small as possible. If you ever have to do a restore they will put all the file data back where it was and either skip the parts they didn't save or fill them with nulls. On 12/30/18 3:50 PM, devz...@web.de 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 greatly keep two large files in sync between source and > destination > (using --inplace), why should it (generally spoken) not also be used to keep > two > blockdevices in sync ? > > maybe these links are interesting in that context: > > https://lists.samba.org/archive/rsync/2010-June/025164.html > > https://github.com/dop251/diskrsync > > roland > >> Gesendet: Sonntag, 30. Dezember 2018 um 19:53 Uhr >> Von: "Kevin Korb via rsync" >> An: rsync@lists.samba.org >> Betreff: Re: rsync remote raw block device with --inplace >> >> 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 what it uses). These will know how to skip >> all the empty parts of the filesystem and will still be capable of >> restoring a complete image in a bare metal restore. You can still use >> dd to snag a copy of the MBR since that is outside of any filesystems. >> >> Also, if you do have to resort to a plain image use ddrescue instead of >> dd. It has a status screen and it can resume as long as you used a log >> file when you ran it. >> >> On 12/30/18 1:45 PM, Steve Newcomb via rsync wrote: >>> 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 >>> re-reinstall without a raw disk image to start from. Disks fail, and >>> the ensuing downtime must be minimized. >>> >>> We're using dd for this. Most of the nightly work is redundant and >>> wasteful of elapsed time and storage. Storage is cheap, but it's not >>> *that* cheap. Elapsed time is priceless. >>> >>> Rsync refuses to back up raw devices, and even raw character devices, >>> with the message "skipping non-regular file" (I think the relevant >>> message is in generator.c). >>> >>> In Linux, anyway, the "raw" command allows a block device to be bound as >>> a character device, and then even a "cat" command can read the raw data >>> of the block device. So why does rsync refuse to copy such content, or >>> why is it a bad idea, or what rsync doctrine conflicts with it? I agree >>> there are security concerns here, but rsync already disallows some of >>> its functions unless the super user is requesting them. >>> >>> >> >> -- >> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., >> Kevin Korb Phone:(407) 252-6853 >> Systems Administrator Internet: >> FutureQuest, Inc. ke...@futurequest.net (work) >> Orlando, Floridak...@sanitarium.net (personal) >> Web page: https://sanitarium.net/ >> PGP public key available on web site. >> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., >> >> -- >> Please use reply-all for most replies to avoid omitting the mailing list. >> To unsubscribe or change options: >> https://lists.samba.org/mailman/listinfo/rsync >> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omit
Aw: Re: rsync remote raw block device with --inplace
> 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 two blockdevices in sync ? maybe these links are interesting in that context: https://lists.samba.org/archive/rsync/2010-June/025164.html https://github.com/dop251/diskrsync roland > Gesendet: Sonntag, 30. Dezember 2018 um 19:53 Uhr > Von: "Kevin Korb via rsync" > An: rsync@lists.samba.org > Betreff: Re: rsync remote raw block device with --inplace > > 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 what it uses). These will know how to skip > all the empty parts of the filesystem and will still be capable of > restoring a complete image in a bare metal restore. You can still use > dd to snag a copy of the MBR since that is outside of any filesystems. > > Also, if you do have to resort to a plain image use ddrescue instead of > dd. It has a status screen and it can resume as long as you used a log > file when you ran it. > > On 12/30/18 1:45 PM, Steve Newcomb via rsync wrote: > > 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 > > re-reinstall without a raw disk image to start from. Disks fail, and > > the ensuing downtime must be minimized. > > > > We're using dd for this. Most of the nightly work is redundant and > > wasteful of elapsed time and storage. Storage is cheap, but it's not > > *that* cheap. Elapsed time is priceless. > > > > Rsync refuses to back up raw devices, and even raw character devices, > > with the message "skipping non-regular file" (I think the relevant > > message is in generator.c). > > > > In Linux, anyway, the "raw" command allows a block device to be bound as > > a character device, and then even a "cat" command can read the raw data > > of the block device. So why does rsync refuse to copy such content, or > > why is it a bad idea, or what rsync doctrine conflicts with it? I agree > > there are security concerns here, but rsync already disallows some of > > its functions unless the super user is requesting them. > > > > > > -- > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., > Kevin Korb Phone:(407) 252-6853 > Systems Administrator Internet: > FutureQuest, Inc. ke...@futurequest.net (work) > Orlando, Floridak...@sanitarium.net (personal) > Web page: https://sanitarium.net/ > PGP public key available on web site. > ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., > > -- > Please use reply-all for most replies to avoid omitting the mailing list. > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: rsync remote raw block device with --inplace
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 what it uses). These will know how to skip all the empty parts of the filesystem and will still be capable of restoring a complete image in a bare metal restore. You can still use dd to snag a copy of the MBR since that is outside of any filesystems. Also, if you do have to resort to a plain image use ddrescue instead of dd. It has a status screen and it can resume as long as you used a log file when you ran it. On 12/30/18 1:45 PM, Steve Newcomb via rsync wrote: > 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 > re-reinstall without a raw disk image to start from. Disks fail, and > the ensuing downtime must be minimized. > > We're using dd for this. Most of the nightly work is redundant and > wasteful of elapsed time and storage. Storage is cheap, but it's not > *that* cheap. Elapsed time is priceless. > > Rsync refuses to back up raw devices, and even raw character devices, > with the message "skipping non-regular file" (I think the relevant > message is in generator.c). > > In Linux, anyway, the "raw" command allows a block device to be bound as > a character device, and then even a "cat" command can read the raw data > of the block device. So why does rsync refuse to copy such content, or > why is it a bad idea, or what rsync doctrine conflicts with it? I agree > there are security concerns here, but rsync already disallows some of > its functions unless the super user is requesting them. > > -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync remote raw block device with --inplace
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 re-reinstall without a raw disk image to start from. Disks fail, and the ensuing downtime must be minimized. We're using dd for this. Most of the nightly work is redundant and wasteful of elapsed time and storage. Storage is cheap, but it's not *that* cheap. Elapsed time is priceless. Rsync refuses to back up raw devices, and even raw character devices, with the message "skipping non-regular file" (I think the relevant message is in generator.c). In Linux, anyway, the "raw" command allows a block device to be bound as a character device, and then even a "cat" command can read the raw data of the block device. So why does rsync refuse to copy such content, or why is it a bad idea, or what rsync doctrine conflicts with it? I agree there are security concerns here, but rsync already disallows some of its functions unless the super user is requesting them. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: --dry-run won't say where the files are going to go
/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 --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+ Maildir/ > cd+ Maildir/new/ >> f+ Maildir/new/1546157908.1392_1.jidanni7 > total: matches=0 hash_hits=0 false_alarms=0 data=0 > > sent 155 bytes received 94 bytes 498.00 bytes/sec > total size is 320 speedup is 1.29 (DRY RUN) > > Guess we'll just have to cross our fingers... > > rsync version 3.1.2 protocol version 31 > > (In fact there is no option to show where the files will go, > --dry-run or not.) > -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., Kevin Korb Phone:(407) 252-6853 Systems Administrator Internet: FutureQuest, Inc. ke...@futurequest.net (work) Orlando, Floridak...@sanitarium.net (personal) Web page: https://sanitarium.net/ PGP public key available on web site. ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._., signature.asc Description: OpenPGP digital signature -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
--dry-run won't say where the files are going to go
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+ Maildir/ cd+ Maildir/new/ >f+ Maildir/new/1546157908.1392_1.jidanni7 total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 155 bytes received 94 bytes 498.00 bytes/sec total size is 320 speedup is 1.29 (DRY RUN) Guess we'll just have to cross our fingers... rsync version 3.1.2 protocol version 31 (In fact there is no option to show where the files will go, --dry-run or not.) -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
