On Wed, Dec 25, 2013 at 11:48:57PM -0500, Theodore Ts'o wrote:
> Sigh, I've had to revert this change since it is causing test
> failures. **Please** run the regression test suite before you submit
> patches.
I figured out the problem. The issue is that you changed e2image to
no longer truncate the output file (i.e., you removed O_TRUNC).
The test failure was caused by the fact that previously written data
blocks that were in unallocated blocks weren't getting over written,
and so this would cause the md5 checksums to break. I can work around
this in the test by deleting the output files, but I think I'll also
modify your comment to avoid the truncate only when trying to create a
raw image dump. For qcow2 and normal e2image files, it's better to
keep the existing behavior of truncating the output when we first open
it.
This change of your also turned up a bug which I had to fix up. It
could happen today when people used e2image to copy a file system to
another block device:
commit aa2c743331f392e49d5b168b5e3d8c8a8084b8b4
Author: Theodore Ts'o <tytso@xxxxxxx>
Date: Wed Dec 25 16:33:52 2013 -0500
e2image: only skip writing zero blocks when writing to a new file
The e2image progam was originally intended to create image files.
However, some people have started using e2image to copy a file system
from one block device to another, since it is more efficient than
using dd because it only copies the blocks which are in use. If we
are doing this, however, we must not skip writing blocks which are all
zero in the source device, since they may not be zero in the
destination device.
Signed-off-by: "Theodore Ts'o" <tytso@xxxxxxx>
Cc: Phillip Susi <psusi@xxxxxxxxxx>
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
