search for: maxdata

...t should make it easier to plug together clients and servers that have different notions of blocksize limitations. A new blocksize filter makes it possible to specify a minimum blocksize handed to the plugin (everything smaller is rounded out, using read-modify-write as needed), and maximum limits (maxdata for read/write since they have a buffer, and maxlen for zero/trim since they do not). Testing is easy by reusing the log filter and observing that requests were rewritten as expected. Signed-off-by: Eric Blake <eblake at redhat.com> --- TODO | 5 -...

...t should make it easier to plug together clients and servers that have different notions of blocksize limitations. A new blocksize filter makes it possible to specify a minimum blocksize handed to the plugin (everything smaller is rounded out, using read-modify-write as needed), and maximum limits (maxdata for read/write since they have a buffer, and maxlen for zero/trim since they do not). Testing is easy by reusing the log filter and observing that requests were rewritten as expected (well, with the slight complication that different versions of qemu-io vary in whether they obey the NBD spec of li...

Hi: I can't install the R-2.8.1 on the machine IBM AIX according the instruction configuratioin(OBJECT_MODE=64........). I can successfully ./configure ***, and get a Makefile. But during compiling the source code, there is some problem I can't fix it. Please tell me some tips about "how to install the R on my AIX. thankx very much. [[alternative HTML version deleted]]

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops. Dom0 seams to work fine. But i can only boot "old" domU kernel. A pv_ops Kernel hangs after initrd. Regards, Stefan Kuhne _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Since v1: add the blocksize filter, add testsuite coverage of the log filter, several fixes to the log filter based on what adding tests revealed I'm still working on FUA flag support patches on top of this; the patches should all be committed in the same release, as we want to minimize the number of releases that cause a filter ABI/API bump Eric Blake (3): backend: Rework internal/filter

...ksize1.img + --filter=log file logfile=blocksize1.log blocksize1.img nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ - --filter=log file logfile=blocksize2.log file=blocksize2.img \ + --filter=log file logfile=blocksize2.log blocksize2.img \ minblock=1024 maxdata=512k maxlen=1M # We may have to wait a short time for the pid files to appear. diff --git a/tests/test-cache.sh b/tests/test-cache.sh index 6f058b8..215bab1 100755 --- a/tests/test-cache.sh +++ b/tests/test-cache.sh @@ -41,7 +41,7 @@ rm -f $files truncate -s 1G cache.img # Run nbdkit with th...

...ksize1.img + --filter=log file logfile=blocksize1.log blocksize1.img nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ - --filter=log file logfile=blocksize2.log file=blocksize2.img \ + --filter=log file logfile=blocksize2.log blocksize2.img \ minblock=1024 maxdata=512k maxlen=1M # We may have to wait a short time for the pid files to appear. diff --git a/tests/test-cache.sh b/tests/test-cache.sh index 6f058b8..215bab1 100755 --- a/tests/test-cache.sh +++ b/tests/test-cache.sh @@ -41,7 +41,7 @@ rm -f $files truncate -s 1G cache.img # Run nbdkit with th...

Based on Rich's review of my v1 that touched only cache.c, I have now tried to bring all three filters with alignment rounding in line with one another. There is definitely room for future improvements once we teach nbdkit to let filters and plugins advertise block sizes, but I'm hoping to get NBD_CMD_CACHE implemented first. Eric Blake (2): blocksize: Process requests in linear order

Hey Guys and Gals, I'm wondering if the quotas.c file is supposed to fix the problem where a Linux x86 system running with the quota software causes corrupt files to be written by Windows clients. I compiled it in and it didn't seem to make a difference for the following problem. In other words, if I enable quotas on my RH6.2 / 2.2.16-22 kernel box and then write a file via Samba/Windows

...e1.sock \ --filter=log file logfile=blocksize1.log blocksize1.img -nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ +start_nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ --filter=log file logfile=blocksize2.log blocksize2.img \ minblock=1024 maxdata=512k maxlen=1M - -# We may have to wait a short time for the pid files to appear. -for i in `seq 1 10`; do - if test -f blocksize1.pid && test -f blocksize2.pid; then - break - fi - sleep 1 -done - -pid1="$(cat blocksize1.pid)" || : -pid2="$(cat blocksize2.pid...

...lter=log file logfile=blocksize1.log blocksize1.img > -nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ > +start_nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ > --filter=log file logfile=blocksize2.log blocksize2.img \ > minblock=1024 maxdata=512k maxlen=1M If the first process starts but the second fails, then you have not set pid1=, and leak the first process. This is a regression from the old code, which managed to capture pid1 before triggering the trap to cleanup(), and thus killed the successful nbdkit. Several tests are im...

Combine much common code into tests/functions.sh. Patch 1: Preparation for patch 3. Patch 2: Fix a long-standing bug in how man pages links are generated. Patch 3: Common code for iterating a test function over every plugin. Patch 4: Common code for starting nbdkit in a test and waiting for the PID file to appear. This is the largest and most complex of the patches but is

When using a filter that rounds up to alignment boundaries, the tail bytes of the plugin are difficult to access correctly. Rather than duplicating lots of code already in the truncate filter, it's easier to just make the other filters default to rounding down and add doc links on how to round up instead. Eric Blake (2): blocksize: Lift restriction against 0-size file cache, cow: Round

...e1.sock \ --filter=log file logfile=blocksize1.log blocksize1.img -nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ +start_nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ --filter=log file logfile=blocksize2.log blocksize2.img \ minblock=1024 maxdata=512k maxlen=1M -# We may have to wait a short time for the pid files to appear. -for i in `seq 1 10`; do - if test -f blocksize1.pid && test -f blocksize2.pid; then - break - fi - sleep 1 -done - -pid1="$(cat blocksize1.pid)" || : -pid2="$(cat blocksize2.pid...

...= 0 (0x0) Flags1 = 0x8 Flags2 = 0x1 Tree ID = 4105 (0x1009) Proc ID = 2248 (0x8c8) UID = 4099 (0x1003) MID = 9 (0x9) Word Count = 15 (0xf) TRANSACT2_FINDFIRST param_length=44 data_length=0 TotParam=44 (0x2c) TotData=0 (0x0) MaxParam=10 (0xa) MaxData=16644 (0x4104) MaxSetup=0 (0x0) Flags=0x0 TimeOut=0 (0x0) Res1=0x0 ParamCnt=44 (0x2c) ParamOff=68 (0x44) DataCnt=0 (0x0) DataOff=112 (0x70) SetupCnt=1 (0x1) smb_bcc=47 Attribute=HIDDEN SYSTEM DIR SearchCount=1366 (0x556) Flags=0x6 Level=260 (0x104) File=\1989\t\test2\* i.e. the server doesn't...

Remove the need to use file= (and in future other) parameters for many plugins. eg. Using the file plugin becomes: nbdkit file disk.img Rich.

...gfile=blocksize1.log blocksize1.img > >-nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ > >+start_nbdkit -P blocksize2.pid -U blocksize2.sock --filter=blocksize \ > > --filter=log file logfile=blocksize2.log blocksize2.img \ > > minblock=1024 maxdata=512k maxlen=1M > > If the first process starts but the second fails, then you have not > set pid1=, and leak the first process. This is a regression from > the old code, which managed to capture pid1 before triggering the > trap to cleanup(), and thus killed the successful nbdkit....

...n to behave in various manners: > log logfile=>(sed ...|uniq -c) (track how many normal/fast zero > requests the client makes) > nozero $params (fine-tune how zero requests behave - the parameters > zeromode and fastzeromode are the real drivers of my various tests) > blocksize maxdata=256k (allows large zero requests, but forces large > writes into smaller chunks, to magnify the effects of write delays and > allow testing to provide obvious results with a smaller image) > delay delay-write=20ms delay-zero=5ms (also to magnify the effects on a > smaller image, with w...

v1 was here: https://www.redhat.com/archives/libguestfs/2018-September/msg00024.html v2: - As discussed in the patch review, tighten up the characters permitted in keys. - Update documentation to note that relative paths can be made safe by prefixing with ./ and absolute paths do not need any extra steps. - I pushed patch 1/6 from the v1 series since it was just a trivial