similar to: [PATCH 0/2] pxzcat preallocation

--- pxzcat.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pxzcat.c b/pxzcat.c index 4ab8689..9bcdc36 100644 --- a/pxzcat.c +++ b/pxzcat.c @@ -29,10 +29,11 @@ * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. */ +#define _GNU_SOURCE #include <config.h>

--- pxzcat.c | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/pxzcat.c b/pxzcat.c index 9bcdc36..55ccfc0 100644 --- a/pxzcat.c +++ b/pxzcat.c @@ -44,10 +44,11 @@ #include <sys/types.h> #include <error.h> #include <errno.h> #include <getopt.h> #include <pthread.h> +#include <linux/falloc.h> #include <lzma.h> #define DEBUG

On 10/22/2013 05:56 PM, Gabriel de Perthuis wrote: > --- > pxzcat.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/pxzcat.c b/pxzcat.c > index 4ab8689..9bcdc36 100644 > --- a/pxzcat.c > +++ b/pxzcat.c > @@ -29,10 +29,11 @@ > * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT > * OF THE USE OF THIS SOFTWARE,

On Wed, Oct 23, 2013 at 03:38:30AM +0100, Pádraig Brady wrote: [...] By the way, Eric Sandeen solved the problem. It's a genuine misfeature in ext4 called auto_da_alloc which causes a flush on close if the file has been truncated (ftruncate or O_TRUNC) and the file size is zero bytes. I added these patches which work around the issue:

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

https://bugzilla.samba.org/show_bug.cgi?id=8775 Summary: Preallocate option doesn't work with recursive? Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: wgordonharris at

On Tue, Jun 02, 2015 at 09:14:03AM +0530, Jatin Davey wrote: > Hi All > > I was reading through this: > > http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/ In my testing, the above method gives near-raw performance as it preallocated all the space ahead of time. The above test can now be done in a single command -- see option (3)

Greetings, I would like to write a patch for rsync but need some help getting started. Here is my situation. I am using cwrsync to copy files from one Windows server to another Windows server. One file that I need to backup is 130 GB. The daily changes occur all throughout the file, not just at the end of the file. File names look like this: Db_20080402_0003_DB.BAK Db_20080403_0003_DB.BAK

I've read in Phil Spector's new book that it's a good idea to preallocate a big matrix, like u <- matrix(0,nrow,ncol) # (1) Now, I read contents of a huge matrix from a Fortran binary dump. u <- readBin(con,what="double",n=nrow*ncol) # (2) If I do (1) and then (2), u is a vector, obviously it's either reallocated or its matrix nature is lost -- overridden?

Hi All I was reading through this: http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/ I was basically searching for pointers on improving disk I/O. I wanted to know the purpose of preallocation=full & preallocation=metadata , What is the difference between them ? and which one would yield a better disk I/O speed ? Appreciate your

On Tue, May 17, 2016 at 6:01 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > > wrote: > > > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > > On Tue, May 17, 2016 at

For raw, this allows "off" as a synonym for "sparse" (to make it consistent with qcow2). For qcow2, this allows "sparse" as a synonym for "off". It also adds qcow2 "full" preallocation, which is actually mapped to the qemu option "falloc" (see arguments about this on the qemu-devel mailing list, which we lost). This also updates the

I am looking at possibility of using OCFS2 with an existing application that requires very high throughput for read and write file access. Files are created by single writer (process) and can be read by multiple reader, possibly while the file is being written. 100+ different files may be written simultaneously, and can be read by 1000+ readers. I am currently using XFS on a local filesystem,

On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > When creating qcow2 images using virt-builder, is there a way to specify > the qcow2 preallocation, as possible with qemu-img create -o > preallocation=metada , for example? No .. but .. it does default to preallocation=metadata provided that the output format is qcow2:

On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > When creating qcow2 images using virt-builder, is there a way to > specify > > > the qcow2 preallocation, as possible with qemu-img create -o

When creating qcow2 images using virt-builder, is there a way to specify the qcow2 preallocation, as possible with qemu-img create -o preallocation=metada , for example? TIA, Y.

I believe that the changes to support --preallocate and --sparse together have broken --preallocate by itself (commit f3873b3d88b61167b106e7b9227a20147f8f6197) The previous behavior of --preallocate was to do just that: reserve blocks in the filesystem WITHOUT setting the size of the file to the final length. The reported filesize would change as the preallocated blocks were actually written.

On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > > When creating qcow2 images using virt-builder, is there a way to

On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > When creating qcow2 images using virt-builder, is there a way to specify > > the qcow2 preallocation, as possible with qemu-img create -o > > preallocation=metada , for example? > > No .. but .. it does default to preallocation=metadata

https://gist.github.com/ad2accc5b4655753923d So here I am creating a database with no values for each small document and one with a bunch of blank values (uuid_blank). Once those are flushed then I reopen them and start replacing the documents of each with identical documents that have an identical large set of values. I am using replace_document and a specific document ID. Is there a specific