Displaying 11 results from an estimated 11 matches for "numblocks".
Did you mean:
num_blocks
2019 Mar 23
2
Re: [PATCH nbdkit 7/8] vddk: Implement extents.
...,
> + struct nbdkit_extents *extents)
> +{
> + struct vddk_handle *h = handle;
> + bool req_one = flags & NBDKIT_FLAG_REQ_ONE;
> + uint64_t position, end, start_sector;
> +
> + position = offset;
> +
...
> +
> + for (i = 0; i < block_list->numBlocks; ++i) {
> + uint64_t offset, length;
> +
> + offset = block_list->blocks[i].offset * VIXDISKLIB_SECTOR_SIZE;
> + length = block_list->blocks[i].length * VIXDISKLIB_SECTOR_SIZE;
> +
> + /* The query returns blocks. We must insert holes between the
> +...
2019 Mar 20
0
[PATCH nbdkit 7/8] vddk: Implement extents.
...AX_CHUNK_NUMBER (512*1024)
+
typedef void *VixDiskLibConnection;
typedef void *VixDiskLibHandle;
@@ -124,4 +127,14 @@ typedef struct VixDiskLibInfo {
char *uuid;
} VixDiskLibInfo;
+typedef struct {
+ uint64_t offset;
+ uint64_t length;
+} VixDiskLibBlock;
+
+typedef struct {
+ uint32_t numBlocks;
+ VixDiskLibBlock blocks[1];
+} VixDiskLibBlockList;
+
#endif /* NBDKIT_VDDK_STRUCTS_H */
diff --git a/plugins/vddk/vddk.c b/plugins/vddk/vddk.c
index 56871cc..d056190 100644
--- a/plugins/vddk/vddk.c
+++ b/plugins/vddk/vddk.c
@@ -45,6 +45,8 @@
#include <nbdkit-plugin.h>
#include "...
2005 Feb 24
6
Rsyncing really large files
Hello everyone,
I have a question regarding syncing of large files. We have a setup where
we need to sync a 500GB file with changes in random blocks.
The changes are made in a manner, so moving blocks is not probable
(actually it will never happen).
As I understand it, the way rsync works is:
- remote server calculates all checksum blocks and transmits these to client
- local client calculates
2019 Mar 25
0
Re: [PATCH nbdkit 7/8] vddk: Implement extents.
On Sat, Mar 23, 2019 at 02:29:54PM -0500, Eric Blake wrote:
> On 3/20/19 5:11 PM, Richard W.M. Jones wrote:
...
> > + for (i = 0; i < block_list->numBlocks; ++i) {
> > + uint64_t offset, length;
> > +
> > + offset = block_list->blocks[i].offset * VIXDISKLIB_SECTOR_SIZE;
> > + length = block_list->blocks[i].length * VIXDISKLIB_SECTOR_SIZE;
> > +
> > + /* The query returns blocks. We must in...
2009 Dec 16
1
WinBUGS - R2WinBUGS problem
...[6] REAL 1.792592453177908E-307
[7] REAL 9.94060079432588E-321
[8] REAL 5.474495960374562E+67
[9] REAL 5.257527858867595E-308
MonitorsSamples.StdMonitor.Update [0000023DH]
.blocks POINTER NIL
.i INTEGER 1655837286
.index INTEGER 7
.monitor MonitorsSamples.StdMonitor [02155B50H]
.numBlocks INTEGER 0
.value REAL 1.0
SamplesMonitors.Monitor.Update [0000091BH]
.chain INTEGER 0
.i INTEGER 4480
.monitor SamplesMonitors.Monitor [01C0A4E0H]
.size INTEGER 6780
SamplesIndex.Monitor.Update [0000030CH]
.chain INTEGER 0
.cursor SamplesIndex.List [01AB2E30H]
.monitor SamplesIndex.Mo...
2019 Mar 27
2
Re: [PATCH nbdkit 7/8] vddk: Implement extents.
On Mon, Mar 25, 2019 at 05:34:25PM +0000, Richard W.M. Jones wrote:
> On Sat, Mar 23, 2019 at 02:29:54PM -0500, Eric Blake wrote:
> > On 3/20/19 5:11 PM, Richard W.M. Jones wrote:
> ...
> > > + for (i = 0; i < block_list->numBlocks; ++i) {
> > > + uint64_t offset, length;
> > > +
> > > + offset = block_list->blocks[i].offset * VIXDISKLIB_SECTOR_SIZE;
> > > + length = block_list->blocks[i].length * VIXDISKLIB_SECTOR_SIZE;
> > > +
> > > + /* The que...
2015 Nov 07
3
Re: mkfs.ext2 succeeds despite nbd write errors?
On Sat, Nov 7, 2015 at 5:03 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
> How about 'strace mkfs.ext2 ..' and see if any system calls are
> returning errors. That would show you whether nbd-client is throwing
> errors away, or whether mkfs is getting the errors and ignoring them
> (seems pretty unlikely, but you never know).
>
> After that, it'd be down
2019 Mar 20
15
[PATCH nbdkit 0/8] Implement extents using a simpler array.
Not sure what version we're up to, but this reimplements extents using
the new simpler structure described in this thread:
https://www.redhat.com/archives/libguestfs/2019-March/msg00077.html
I also fixed most of the things that Eric pointed out in the previous
review, although I need to go back over his replies and check I've got
everything.
This needs a bit more testing. However the
2019 Mar 26
21
[PATCH nbdkit v4 00/15] Implement Block Status.
I'm not sure exactly which version we're up to, but let's say it's
version 4.
I'm a lot happier with this version:
- all filters have been reviewed and changed where I think that's necessary
- can_extents is properly defined and implemented now
- NBD protocol is followed
- I believe it addresses all previous review points where possible
The "only" thing
2019 Mar 19
15
[PATCH nbdkit 0/9] [mainly for discussion and early review] Implement extents.
I want to post this but mainly for discussion and early review. It's
not safe for these patches to all go upstream yet (because not all
filters have been checked/adjusted), but if any patches were to go
upstream then probably 1 & 2 only are safe.
File, VDDK, memory and data plugins all work, although I have only
done minimal testing on them.
The current tests, such as they are, all
2019 Mar 28
32
[PATCH nbdkit v5 FINAL 00/19] Implement extents.
This has already been pushed upstream. I am simply posting these here
so we have a reference in the mailing list in case we find bugs later
(as I'm sure we will - it's a complex patch series).
Great thanks to Eric Blake for tireless review on this one. It also
seems to have identified a few minor bugs in qemu along the way.
Rich.