All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] [XM-TEST] block device write verify test 2nd attempt
@ 2006-05-23 10:35 Harry Butterworth
  2006-05-23 11:40 ` Ewan Mellor
  2006-05-24  9:52 ` Harry Butterworth
  0 siblings, 2 replies; 9+ messages in thread
From: Harry Butterworth @ 2006-05-23 10:35 UTC (permalink / raw)
  To: xen-devel

[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]

The only difference from the last version of the patch is that the minor
version number in configure.ac is incremented.

>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 and fancy head in busybox on the ramdisk.  I
have tested the patch with both `make existing' where the tests run but
the new test fails because the ramdisk is missing tee and fancy head and
`make` where the test passes successfully.

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

[-- Attachment #2: block_device_write_verify.patch --]
[-- Type: text/x-patch, Size: 3834 bytes --]

diff -r 14717dedba02 -r 6394ff30dfc0 tools/xm-test/configure.ac
--- a/tools/xm-test/configure.ac	Sun May 21 19:15:58 2006
+++ b/tools/xm-test/configure.ac	Tue May 23 10:26:21 2006
@@ -1,7 +1,7 @@
 # xm-test configure.ac input script
 
 # Basic header information
-AC_INIT([xm-test], [0.7.1])
+AC_INIT([xm-test], [0.7.2])
 AM_INIT_AUTOMAKE([1.7 foreign])
 
 # Check for dependencies
diff -r 14717dedba02 -r 6394ff30dfc0 tools/xm-test/grouptest/default
--- a/tools/xm-test/grouptest/default	Sun May 21 19:15:58 2006
+++ b/tools/xm-test/grouptest/default	Tue May 23 10:26:21 2006
@@ -1,6 +1,7 @@
 block-create
 block-destroy
 block-list
+block-integrity
 console
 create
 destroy
diff -r 14717dedba02 -r 6394ff30dfc0 tools/xm-test/ramdisk/configs/busybox
--- a/tools/xm-test/ramdisk/configs/busybox	Sun May 21 19:15:58 2006
+++ b/tools/xm-test/ramdisk/configs/busybox	Tue May 23 10:26:21 2006
@@ -92,7 +92,7 @@
 CONFIG_FALSE=y
 # CONFIG_FOLD is not set
 CONFIG_HEAD=y
-# CONFIG_FEATURE_FANCY_HEAD is not set
+CONFIG_FEATURE_FANCY_HEAD=y
 CONFIG_HOSTID=y
 CONFIG_ID=y
 CONFIG_INSTALL=y
@@ -127,8 +127,8 @@
 CONFIG_SYNC=y
 CONFIG_TAIL=y
 CONFIG_FEATURE_FANCY_TAIL=n
-CONFIG_TEE=n
-CONFIG_FEATURE_TEE_USE_BLOCK_IO=n
+CONFIG_TEE=y
+CONFIG_FEATURE_TEE_USE_BLOCK_IO=y
 CONFIG_TEST=y
 
 #
diff -r 14717dedba02 -r 6394ff30dfc0 tools/xm-test/tests/block-integrity/Makefile.am
--- a/tools/xm-test/tests/block-integrity/Makefile.am	Sun May 21 19:15:58 2006
+++ b/tools/xm-test/tests/block-integrity/Makefile.am	Tue May 23 10:26:21 2006
@@ -1,7 +1,8 @@
 
 SUBDIRS =
 
-TESTS = 01_block_device_read_verify.test
+TESTS = 01_block_device_read_verify.test \
+        02_block_device_write_verify.test
 
 XFAIL_TESTS = 
 
diff -r 14717dedba02 -r 6394ff30dfc0 tools/xm-test/tests/block-integrity/02_block_device_write_verify.py
--- /dev/null	Sun May 21 19:15:58 2006
+++ b/tools/xm-test/tests/block-integrity/02_block_device_write_verify.py	Tue May 23 10:26:21 2006
@@ -0,0 +1,63 @@
+#!/usr/bin/python
+
+# Copyright (C) International Business Machines Corp., 2006
+# Author: Harry Butterworth <butterwo@uk.ibm.com>
+
+# 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.
+
+import re
+
+from XmTestLib import *
+from XmTestLib.block_utils import *
+
+if ENABLE_HVM_SUPPORT:
+    SKIP("Block-attach not supported for HVM domains")
+
+domain = XmTestDomain()
+
+try:
+    console = domain.start()
+except DomainError, e:
+    FAIL(str(e))
+
+console.setHistorySaveCmds(value=True)
+
+block_attach(domain, "phy:ram1", "hda1")
+
+console.setTimeout(120)
+
+try:
+    run = console.runCmd("head -c `cat /dev/hda1 | wc -c` /dev/urandom | tee /dev/hda1 | md5sum")
+except ConsoleError, e:
+    FAIL(str(e))
+
+domU_md5sum_match = re.search(r"^[\dA-Fa-f]{32}", run["output"])
+
+domain.closeConsole()
+
+domain.stop()
+
+s, o = traceCommand("md5sum /dev/ram1")
+
+dom0_md5sum_match = re.search(r"^[\dA-Fa-f]{32}", o)
+
+if domU_md5sum_match == None:
+    FAIL("Failed to get md5sum of data written in domU.")
+
+if dom0_md5sum_match == None:
+    FAIL("Failed to get md5sum of data read back in dom0.")
+
+if verbose:
+    print "md5sum domU:"
+    print domU_md5sum_match.group()
+    print "md5sum dom0:"
+    print dom0_md5sum_match.group()
+
+if domU_md5sum_match.group() != dom0_md5sum_match.group():
+    FAIL("MISCOMPARE: data read in dom0 did not match data written by domU.")

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-23 10:35 [PATCH] [XM-TEST] block device write verify test 2nd attempt Harry Butterworth
@ 2006-05-23 11:40 ` Ewan Mellor
  2006-05-23 12:35   ` Harry Butterworth
  2006-05-24  9:52 ` Harry Butterworth
  1 sibling, 1 reply; 9+ messages in thread
From: Ewan Mellor @ 2006-05-23 11:40 UTC (permalink / raw)
  To: Harry Butterworth; +Cc: xen-devel

On Tue, May 23, 2006 at 11:35:55AM +0100, Harry Butterworth wrote:

> The only difference from the last version of the patch is that the minor
> version number in configure.ac is incremented.
> 
> >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 and fancy head in busybox on the ramdisk.  I
> have tested the patch with both `make existing' where the tests run but
> the new test fails because the ramdisk is missing tee and fancy head and
> `make` where the test passes successfully.

Why don't you use dd instead of head -c?

Why don't you just fix the size of the datablock that you write to the
ramdisk, instead of determining the current size of the ramdisk with cat
/dev/hda1 | wc -c?

Ewan.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-23 11:40 ` Ewan Mellor
@ 2006-05-23 12:35   ` Harry Butterworth
  2006-05-24 10:20     ` Ewan Mellor
  0 siblings, 1 reply; 9+ messages in thread
From: Harry Butterworth @ 2006-05-23 12:35 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: xen-devel

On Tue, 2006-05-23 at 12:40 +0100, Ewan Mellor wrote:
> On Tue, May 23, 2006 at 11:35:55AM +0100, Harry Butterworth wrote:
> 
> > The only difference from the last version of the patch is that the minor
> > version number in configure.ac is incremented.
> > 
> > >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 and fancy head in busybox on the ramdisk.  I
> > have tested the patch with both `make existing' where the tests run but
> > the new test fails because the ramdisk is missing tee and fancy head and
> > `make` where the test passes successfully.
> 
> Why don't you use dd instead of head -c?

I tried using dd with a block size of 1 and a count of the right number
of bytes but the test was very slow.  I didn't want to assume a 512b
block size and I'm not very good at shell script so didn't manage to
work out how to do it better.

> Why don't you just fix the size of the datablock that you write to the
> ramdisk, instead of determining the current size of the ramdisk with cat
> /dev/hda1 | wc -c?

I wanted to test writing at the device limits.  Sometimes there are off
by one errors that mean you can't write the last sector of a block
device.

cat | wc -c was the most robust way I could think of for getting the
size.

> 
> Ewan.
> 

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-23 10:35 [PATCH] [XM-TEST] block device write verify test 2nd attempt Harry Butterworth
  2006-05-23 11:40 ` Ewan Mellor
@ 2006-05-24  9:52 ` Harry Butterworth
  1 sibling, 0 replies; 9+ messages in thread
From: Harry Butterworth @ 2006-05-24  9:52 UTC (permalink / raw)
  To: xen-devel

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

On Tue, 2006-05-23 at 11:35 +0100, Harry Butterworth wrote:
> The only difference from the last version of the patch is that the minor
> version number in configure.ac is incremented.
> 
> >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 and fancy head in busybox on the ramdisk.  I
> have tested the patch with both `make existing' where the tests run but
> the new test fails because the ramdisk is missing tee and fancy head and
> `make` where the test 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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-23 12:35   ` Harry Butterworth
@ 2006-05-24 10:20     ` Ewan Mellor
  2006-05-24 11:08       ` Harry Butterworth
  0 siblings, 1 reply; 9+ messages in thread
From: Ewan Mellor @ 2006-05-24 10:20 UTC (permalink / raw)
  To: Harry Butterworth; +Cc: xen-devel

On Tue, May 23, 2006 at 01:35:35PM +0100, Harry Butterworth wrote:

> On Tue, 2006-05-23 at 12:40 +0100, Ewan Mellor wrote:
> > On Tue, May 23, 2006 at 11:35:55AM +0100, Harry Butterworth wrote:
> > 
> > > The only difference from the last version of the patch is that the minor
> > > version number in configure.ac is incremented.
> > > 
> > > >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 and fancy head in busybox on the ramdisk.  I
> > > have tested the patch with both `make existing' where the tests run but
> > > the new test fails because the ramdisk is missing tee and fancy head and
> > > `make` where the test passes successfully.
> > 
> > Why don't you use dd instead of head -c?
> 
> I tried using dd with a block size of 1 and a count of the right number
> of bytes but the test was very slow.  I didn't want to assume a 512b
> block size and I'm not very good at shell script so didn't manage to
> work out how to do it better.

dd bs=<number> count=1 should do just fine.

> > Why don't you just fix the size of the datablock that you write to the
> > ramdisk, instead of determining the current size of the ramdisk with cat
> > /dev/hda1 | wc -c?
> 
> I wanted to test writing at the device limits.  Sometimes there are off
> by one errors that mean you can't write the last sector of a block
> device.
> 
> cat | wc -c was the most robust way I could think of for getting the
> size.

How about blockdev --getsize64 /dev/ram1?

Ewan.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-24 10:20     ` Ewan Mellor
@ 2006-05-24 11:08       ` Harry Butterworth
  2006-05-24 12:37         ` Ewan Mellor
  0 siblings, 1 reply; 9+ messages in thread
From: Harry Butterworth @ 2006-05-24 11:08 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: xen-devel

On Wed, 2006-05-24 at 11:20 +0100, Ewan Mellor wrote:
> On Tue, May 23, 2006 at 01:35:35PM +0100, Harry Butterworth wrote:
> 
> > On Tue, 2006-05-23 at 12:40 +0100, Ewan Mellor wrote:
> > > On Tue, May 23, 2006 at 11:35:55AM +0100, Harry Butterworth wrote:
> > > 
> > > > The only difference from the last version of the patch is that the minor
> > > > version number in configure.ac is incremented.
> > > > 
> > > > >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 and fancy head in busybox on the ramdisk.  I
> > > > have tested the patch with both `make existing' where the tests run but
> > > > the new test fails because the ramdisk is missing tee and fancy head and
> > > > `make` where the test passes successfully.
> > > 
> > > Why don't you use dd instead of head -c?
> > 
> > I tried using dd with a block size of 1 and a count of the right number
> > of bytes but the test was very slow.  I didn't want to assume a 512b
> > block size and I'm not very good at shell script so didn't manage to
> > work out how to do it better.
> 
> dd bs=<number> count=1 should do just fine.

The ram disk is 64MB, I thought that this would require a 64MB buffer in
domU which I thought was too big.  It would be better to use dd with the
correct block size and count of blocks.

> 
> > > Why don't you just fix the size of the datablock that you write to the
> > > ramdisk, instead of determining the current size of the ramdisk with cat
> > > /dev/hda1 | wc -c?
> > 
> > I wanted to test writing at the device limits.  Sometimes there are off
> > by one errors that mean you can't write the last sector of a block
> > device.
> > 
> > cat | wc -c was the most robust way I could think of for getting the
> > size.
> 
> How about blockdev --getsize64 /dev/ram1?

blockdev and stat are not available in the ramdisk.  I could use
blockdev to get the blocksize and number of blocks in dom0 and then pass
the values to domU but it would be better to obtain all the information
in domU since that would test whether the size of the device is
correctly passed from the back to the front by the blk driver.

The test as it stands does check that aspect of the blk driver operation
and is only a factor of 2 slower than the limit and the python code is
trivial so I thought it was reasonable.

Can you think of any way to get the block size and number of blocks
using tools available on the ramdisk?

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-24 11:08       ` Harry Butterworth
@ 2006-05-24 12:37         ` Ewan Mellor
  2006-05-24 13:09           ` Harry Butterworth
  0 siblings, 1 reply; 9+ messages in thread
From: Ewan Mellor @ 2006-05-24 12:37 UTC (permalink / raw)
  To: Harry Butterworth; +Cc: xen-devel

On Wed, May 24, 2006 at 12:08:28PM +0100, Harry Butterworth wrote:

> > > > Why don't you just fix the size of the datablock that you write to the
> > > > ramdisk, instead of determining the current size of the ramdisk with cat
> > > > /dev/hda1 | wc -c?
> > > 
> > > I wanted to test writing at the device limits.  Sometimes there are off
> > > by one errors that mean you can't write the last sector of a block
> > > device.
> > > 
> > > cat | wc -c was the most robust way I could think of for getting the
> > > size.
> > 
> > How about blockdev --getsize64 /dev/ram1?
> 
> blockdev and stat are not available in the ramdisk.  I could use
> blockdev to get the blocksize and number of blocks in dom0 and then pass
> the values to domU but it would be better to obtain all the information
> in domU since that would test whether the size of the device is
> correctly passed from the back to the front by the blk driver.
> 
> The test as it stands does check that aspect of the blk driver operation
> and is only a factor of 2 slower than the limit and the python code is
> trivial so I thought it was reasonable.
> 
> Can you think of any way to get the block size and number of blocks
> using tools available on the ramdisk?

dd if=/dev/urandom of=/dev/ram1 bs=512 count=`cat /sys/block/ram1/size`

The value in /sys/block/ram1/size is defined to be in multiples of 512 bytes,
as rd.c shows:

		/* rd_size is given in kB */
                ...
		set_capacity(disk, rd_size * 2);


Catting the whole device to determine its size is vile, and would slow down
the regression suite unnecessarily.  Modifying the ramdisk is not verboten,
but it is a right pain in the backside for everyone, particularly me because I
need to build a new one and upload it and all of its source (because of the
GPL) to xm-test.xensource.com.

Ewan.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-24 12:37         ` Ewan Mellor
@ 2006-05-24 13:09           ` Harry Butterworth
  2006-05-24 22:01             ` Ewan Mellor
  0 siblings, 1 reply; 9+ messages in thread
From: Harry Butterworth @ 2006-05-24 13:09 UTC (permalink / raw)
  To: Ewan Mellor; +Cc: xen-devel

On Wed, 2006-05-24 at 13:37 +0100, Ewan Mellor wrote:
> On Wed, May 24, 2006 at 12:08:28PM +0100, Harry Butterworth wrote:
> 
> > > > > Why don't you just fix the size of the datablock that you write to the
> > > > > ramdisk, instead of determining the current size of the ramdisk with cat
> > > > > /dev/hda1 | wc -c?
> > > > 
> > > > I wanted to test writing at the device limits.  Sometimes there are off
> > > > by one errors that mean you can't write the last sector of a block
> > > > device.
> > > > 
> > > > cat | wc -c was the most robust way I could think of for getting the
> > > > size.
> > > 
> > > How about blockdev --getsize64 /dev/ram1?
> > 
> > blockdev and stat are not available in the ramdisk.  I could use
> > blockdev to get the blocksize and number of blocks in dom0 and then pass
> > the values to domU but it would be better to obtain all the information
> > in domU since that would test whether the size of the device is
> > correctly passed from the back to the front by the blk driver.
> > 
> > The test as it stands does check that aspect of the blk driver operation
> > and is only a factor of 2 slower than the limit and the python code is
> > trivial so I thought it was reasonable.
> > 
> > Can you think of any way to get the block size and number of blocks
> > using tools available on the ramdisk?
> 
> dd if=/dev/urandom of=/dev/ram1 bs=512 count=`cat /sys/block/ram1/size`

> The value in /sys/block/ram1/size is defined to be in multiples of 512 bytes,
> as rd.c shows:
> 
> 		/* rd_size is given in kB */
>                 ...
> 		set_capacity(disk, rd_size * 2);

OK, thanks I'll use that.

> Modifying the ramdisk is not verboten,
> but it is a right pain in the backside for everyone, particularly me because I
> need to build a new one and upload it and all of its source (because of the
> GPL) to xm-test.xensource.com.

The current test is modifying the ramdisk to add `tee` (as well as fancy
head which we don't need anymore).

Are you going to accept the patch if it requires the addition of `tee`
to the ramdisk?  Or should I change the test to read the data back in
domU---which I was specifically trying to avoid.

The problem with reading the data back in domU after having written it
is that it might mask bugs in the block driver.  Reading the data back
might cause it to be committed to the device where otherwise a bug might
cause it to be lost.

Harry.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [PATCH] [XM-TEST] block device write verify test 2nd attempt
  2006-05-24 13:09           ` Harry Butterworth
@ 2006-05-24 22:01             ` Ewan Mellor
  0 siblings, 0 replies; 9+ messages in thread
From: Ewan Mellor @ 2006-05-24 22:01 UTC (permalink / raw)
  To: Harry Butterworth; +Cc: xen-devel

On Wed, May 24, 2006 at 02:09:49PM +0100, Harry Butterworth wrote:

> > Modifying the ramdisk is not verboten,
> > but it is a right pain in the backside for everyone, particularly me because I
> > need to build a new one and upload it and all of its source (because of the
> > GPL) to xm-test.xensource.com.
> 
> The current test is modifying the ramdisk to add `tee` (as well as fancy
> head which we don't need anymore).
> 
> Are you going to accept the patch if it requires the addition of `tee`
> to the ramdisk?  Or should I change the test to read the data back in
> domU---which I was specifically trying to avoid.
> 
> The problem with reading the data back in domU after having written it
> is that it might mask bugs in the block driver.  Reading the data back
> might cause it to be committed to the device where otherwise a bug might
> cause it to be lost.

I think that's a fair point, so yes, we'll have to rev the ramdisk anyway.

Ewan.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2006-05-24 22:01 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-23 10:35 [PATCH] [XM-TEST] block device write verify test 2nd attempt Harry Butterworth
2006-05-23 11:40 ` Ewan Mellor
2006-05-23 12:35   ` Harry Butterworth
2006-05-24 10:20     ` Ewan Mellor
2006-05-24 11:08       ` Harry Butterworth
2006-05-24 12:37         ` Ewan Mellor
2006-05-24 13:09           ` Harry Butterworth
2006-05-24 22:01             ` Ewan Mellor
2006-05-24  9:52 ` Harry Butterworth

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.