similar to: Making --inplace and --sparse compatible

Is there a way to find the holes in sparse files, other than assuming contiguous blocks of zeroes are holes? Thanks, Sean

Hi, We are trying to use OCFS2 as VM storage. After running into problems with qemu's disk_mirror feature we now think there could be a problem with the FIEMAP ioctl in OCFS2. As far as I understand the situation looks like this: Qemu inquiries the FS if the given section of the image is already allocated via the FIEMAP ioctl [1] It especially checks if fm_mapped_extents is greater 0.

https://bugzilla.samba.org/show_bug.cgi?id=8918 Summary: Use fiemap to quickly detect zero ranges of source file Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org

https://bugzilla.samba.org/show_bug.cgi?id=12305 Bug ID: 12305 Summary: --fallocate and --sparse works wrong Product: rsync Version: 3.1.1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

https://bugzilla.samba.org/show_bug.cgi?id=11651 Bug ID: 11651 Summary: Can we allow --inplace and --sparse to coexist when --whole-file is in play? Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core

hi, is it possible to enable efficient treatment of sparse files along with -u -inplace option? the algo could fall back to regular logic for -S. thanks, javed -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20140325/89c0d9a3/attachment.html>

https://bugzilla.samba.org/show_bug.cgi?id=7194 Summary: Getting --inplace and --sparse to work together Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: jansen at

Hi Steven, Hi ext3-users list! We encountered a reproduceable problem with ext3: When issuing a FIBMAP ioctl for a block written right before while the FS is under high load (RH build universe), the assertion !journal->j_running_transaction fails at the bottom of journal_flush() in fs/jbd/journal.c. We encountered this problem with the arch=s390x (64 bit big endian) bootloader zipl, I'll

I've posted a couple of patches towards the ultimate goal of implementing NBD_CMD_BLOCK_STATUS / base:allocation in nbdkit. Before I can do the final patch I think we need to discuss how this would be exposed to plugins since at the end of the day they need to implement the feature. Background reading: - preparatory patches:

https://bugzilla.samba.org/show_bug.cgi?id=11588 Bug ID: 11588 Summary: missing option: preallocate for all files except for sparse Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: core

I would like to run a logistic regression on some factor variables (main effects and eventually an interaction) that are very sparse. I have a moderately large dataset, ~100k observations with 1500 factor levels for one variable (x1) and 600 for another (X2), creating ~19000 levels for the interaction (X1:X2). I would like to take advantage of the sparseness in these factors to avoid using GLM.

https://bugzilla.samba.org/show_bug.cgi?id=7854 Summary: Abysmal sparse file performance Product: rsync Version: 3.0.7 Platform: x86 OS/Version: FreeBSD Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: grarpamp at gmail.com

Wayne, I noticed that rsync will let me apply a non-inplace batch file in inplace mode. This corrupts the destination file if the batch file copies any data forward (from earlier offsets to later ones). Of course, the post-transfer checksum detects the corruption and gives the "ERROR: <file> failed verification" message, but rsync doesn't give the user a clue why the

I have a 5.5GB file, mostly sparse. Tar performs far[!] better than rsync. I have no ideas yet, so just an FYI as to current state. FreeBSD 8.1 i386 zfs Yes, I know the blocks used differs but don't know why yet, could be just how zfs does things or related to the large amount of sparseness. There are no media errors, CPU/IO load or anything like that and the source and dest paths are on the

https://bugzilla.samba.org/show_bug.cgi?id=5201 Summary: Rsync lets user corrupt dest by applying non-inplace batch in inplace mode Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

I just downloaded the pre48 and ran make. It ran fine for everything, but ended with a number of errors related to the syslxcom program. Usually, I only see the messages about the windows build since I am doing the make on a Fedora 10 system. Is there something new that has been added that requires something that I am missing? From looking at the program this isn't related to the isolinux

Please let me know -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20120905/15183c58/attachment.html>

There is the problem which I discribed here https://bugs.centos.org/view.php?id=12820. rsync does not break hard-link into destination if hard-link has be broken in source with option inplace. The problem remains in the latest version of rsync? -- View this message in context: http://samba.2283325.n4.nabble.com/There-is-problem-of-rsync-with-options-hard-links-inplace-tp4714872.html Sent from

Hi! As I commonly spell --inplace as --in-place, I'd like to suggest this simple patch: commit 5689f99b702788044a45e13582559832cf986328 Author: Jan-Benedict Glaw <jbglaw at lug-owl.de> Date: Wed Jun 26 22:49:31 2019 +0200 Allow "--in-place" as an alternative option name for "--inplace". diff --git a/options.c b/options.c index e5b0cb68..7ff0c51d 100644 ---

Hello list! How dangerous is acctually the --inplace option if you want to run rsync to update files that are only read and not written to? What is the worst that can happen? The file is not readable, the reader gets half the file of an old version and the rest is from the new version? There is not a simple way to make it update the file in the standard way and then change the ownership