similar to: Rsync friendly zlib/gzip compression - revisited

Hi all- My test results so far indicate a pretty decent improvement in overall rsync performance when using a slightly more sophisticated checksum calculation. The attached patch has the required changes (in hindsight, I should have compressed this using zlib with the new algorithm :-) ). Some things to know about the patch: First, it is against the zlib library - NOT the gzip application. By

I was startled to find that the --csum-length option is not implemented even though it is documented in the manpage. Not a good thing. Here's a patch that removes the manpage entry. I'd much rather not see this option and actually have the csum_length be per-file dynamic. Either way this patch should be applied at least until the code changes. The patch also brings rsync.1 and

Hi All, I am using rsync to backup our office server to our Internet server (RHE). As an association for doctors we are looking at providing a backup service for their practices using rsync. As it would be patient data it would need to be encrypted. I have found a few options, namely esync wurt rsyncrypto Does anyone have experience with the above and perhaps like to recommend one? On the

(this may be a duplicate post since I attached a file to the previous try...sorry about that) Below are the first few lines of a zlib compressed byte array written from Java with the Deflator class. > readBin("row_1",raw(),10000000) [1] 4c 45 50 e2 49 d5 86 bc 48 a1 32 5d 49 9d f5 90 48 e0 14 33 49 8f 54 6a 49 77 c9 48 48 d9 ec 56 47 91 48 f0 47 25 56 ef 47 b8 f5 7b 46 35 25 00

https://bugzilla.samba.org/show_bug.cgi?id=10552 Summary: Sender checksum calculation significantly slower with compression enabled Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

I don't know if this is the propper place to ask for new funcionality, but after searching the website i didn't find another place to do it. I'm very sorry if I`m asking this in the wrong place. It would be greatful to have crypting funcionality added to rsync, appart from using ssh to crypt transmissions. I know this is not the original purpose for rsync, but anyway it's a fact

My understanding is that if I "zfs set checksum=<different>" to change the algorithm that this will change the checksum algorithm for all FUTURE data blocks written, but does not in any way change the checksum for previously written data blocks. I need to corroborate this understanding. Could someone please point me to a document that states this? I have searched and searched

Before anyone yells at me, yes, you can use rsync's --checksum to detect (and fix) files that are incorrect despite having correct timestamps and sizes. This would mean that a previous rsync had been corrupted not the current one. But it is important to note that this would only be reported to you if you also use --itemize-changes and what to look for (a file with a c but not an s or a t).

On Tuesday, January 28, 2020 9:00:22 AM CET Nataraj wrote: > On 1/26/20 5:44 PM, hw wrote: > > On Sunday, January 26, 2020 11:18:36 PM CET Pete Biggs wrote: > >> First of all - disclaimer - I'm no network specialist, I just read and > >> am interested in it. I may get things wrong!! > >> > >>> Both physical interfaces show the same. But does

On Wednesday, January 29, 2020 10:10:48 AM CET Nataraj wrote: > On 1/28/20 12:39 PM, hw wrote: > > On Tuesday, January 28, 2020 9:00:22 AM CET Nataraj wrote: > >> On 1/26/20 5:44 PM, hw wrote: > >>> On Sunday, January 26, 2020 11:18:36 PM CET Pete Biggs wrote: > >>>> First of all - disclaimer - I'm no network specialist, I just read and >

Moin, I wrote a backup script, that use rsync and its hardlink features. Now I want to implement a new feature to my script: crypt the backuped files. But I wonder how this can be done? Because rsync check if the source file is different from the target file. But the target file will be allways different if it is crypt; right? Any idea? Thanks -- |Michael Renner E-mail:

On Fri, Oct 04, 2002 at 01:57:03PM -0400, Hod McWuff wrote: > Agreed that the oversampling isn't useful in the long term. I'm not sure > what you mean by 'dictioniary overhead'. > > I'd like to see an easy-to-invoke set of parameters that will spare no > cpu expense and produce the tightest theoretically possible output. > > I'm guessing the best of

Hi, Assume you are in hostile environment, as in you can't trust the DHCP serversss nor the TFTP/HTTP server. So you would want a checksum on kernel and initrd. Which checksum algoritme is available in pxelinux.0? Which checksum algoritme could be integrate into pxelinux.0? In other words: Please advice what could be done to verify what pxelinux.0 did download. Cheers Geert Stappers --

Dear all is it possible to rsync in a master-slave scenario saving to slave gzip content? i'm not talking about compression during transfer, i'm talking about -saving- the destination in a compressed format. Example: FROM: -folder_A --file_A --file_B TO: -folder_A --file_A.gz --file_B.gz I know that this won't be a "real" rsync between two folder, but it will be an

Hi I am using "rsync" to send files from a source machine to a remote machine as one typically does. I would like to clarify that the "-c" option will cause the checksum on the receiving end to be created by reading the already written file and NOT the data stream on the receiving end. This would help in catching disk I/O errors if the checksum is done on the file on disk.

I apologize if this has already been discussed before, but as of yet I have been unable to find any info on the topic. I have a very simple (and common) disk based backup system using rsync, hard links, and a little bit of perl to glue it together. Remote machines are backed up regularly using hardlinks across each snapshot to reduce disk usage. Recently I learned that rsync does a

I have and old dump format backup done under fedora 7 which is stored on disk and has an sha256sum file that indicates there are no data errors in the backup file.? When I try to read the file with restore under CentOS 6,? I get the following error: cat /etc/redhat-release CentOS release 6.10 (Final) restore tvf u1_l0_04-29-09_md1.dump Verify tape and initialize maps Input is from a local

Hi, Is it possible for you to compile flac/metaflac yourself? Then you'll only need to remove a few lines, namely these 4: https://github.com/xiph/flac/blob/28e4f0528c76b296c561e922ba67d43751990599/src/libFLAC/stream_decoder.c#L2118-L2121 and these 7: https://github.com/xiph/flac/blob/28e4f0528c76b296c561e922ba67d43751990599/src/libFLAC/stream_decoder.c#L2141-L2147 As you can see these lines

Hi, I have problem getting the standard deviation from the manova output. I have used the manova function: myfit <- manova(cbind(y1, y2) ~ x1 + x2 + x3, data=mydata) . I tried to get the predicted values and their standard deviation by using: predict(myfit, type="response", se.fit=TRUE) But the problem is that I don't get the standard deviation values, I only

I need some help for a curious question of a friend of mine. She usually does some experiments (3-5 repeats for each exp) and then she calculates mean and standard deviation. In microsoft excel she writes something like the following sample mean sd a 1.25 0.35 b 2.65 0.65 c 3.45 0.50 She can do a vertical barplot graph just giving mean value and specifying the