Xen devel - May 2006 - [PATCH] [XM-TEST] block device write verify test 3rd attempt

Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com>

The differences from the last version of the patch are that...

1) The patch no longer enables fancy head in the BusyBox config.
2) The patch uses `dd` rather than `head -c`.
3) The patch uses `cat /sys/block/hda1/size` in place of `cat /dev/hda1
| wc -c`.  This gives maybe a 30% performance improvement at the cost of
a dependency on the sys filesystem layout and contents.
>From the patch:
+# This test imports a ram disk device as a physical device into a domU.
+# The domU initialises the ram disk with data from /dev/urandom and
calculates
+# the md5 checksum of the data (using tee as it is written so as to
avoid
+# reading it back from the device which might potentially mask
problems).
+# The domU is stopped and the md5 checksum of the data on the device is
+# calculated by dom0.  The test succeeds if the checksums match,
indicating
+# that all the data written by domU was sucessfully committed to the
device.
+

This patch also enables tee in BusyBox on the ramdisk and increments the
xm-test minor version number.  I have tested the patch (again for this
3rd version) with both `make existing'' where the tests run but the new
test fails because the ramdisk is missing tee and `make` where the test
builds the new ramdisk and passes successfully.

The patch also installs the block-integrity tests in the default test
set so they get executed.


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thu, May 25, 2006 at 12:46:58PM +0100, Harry Butterworth wrote:
> Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com>
> 
> The differences from the last version of the patch are that...
> 
> 1) The patch no longer enables fancy head in the BusyBox config.
> 2) The patch uses `dd` rather than `head -c`.
> 3) The patch uses `cat /sys/block/hda1/size` in place of `cat /dev/hda1
> | wc -c`.  This gives maybe a 30% performance improvement at the cost of
> a dependency on the sys filesystem layout and contents.
> 
> >From the patch:
> 
> +# This test imports a ram disk device as a physical device into a domU.
> +# The domU initialises the ram disk with data from /dev/urandom and
> calculates
> +# the md5 checksum of the data (using tee as it is written so as to
> avoid
> +# reading it back from the device which might potentially mask
> problems).
> +# The domU is stopped and the md5 checksum of the data on the device is
> +# calculated by dom0.  The test succeeds if the checksums match,
> indicating
> +# that all the data written by domU was sucessfully committed to the
> device.
> +
> 
> This patch also enables tee in BusyBox on the ramdisk and increments the
> xm-test minor version number.  I have tested the patch (again for this
> 3rd version) with both `make existing'' where the tests run but the
new
> test fails because the ramdisk is missing tee and `make` where the test
> builds the new ramdisk and passes successfully.
> 
> The patch also installs the block-integrity tests in the default test
> set so they get executed.
Applied, thanks Harry.  I''ve bumped the version number to 0.8, not
0.7.2 --
if the ramdisk changes, you need to bump the middle digit.

Everyone -- this means that you''ll have to download or build a new
ramdisk.  A
new one will be on xm-test by the end of the day.

Cheers,

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel