No error report with writing (dd of=/dev/sda ...), but can't change
data, (dd if=/dev/sda) dump unchanged.
On Wed, Jun 29, 2011 at 1:47 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Wed, Jun 29, 2011 at 5:47 AM, Fam Zheng famc...@gmail.com wrote:
Stream optimized VMDK image allocates
On Wed, Jun 29, 2011 at 7:18 AM, Fam Zheng famc...@gmail.com wrote:
No error report with writing (dd of=/dev/sda ...), but can't change
data, (dd if=/dev/sda) dump unchanged.
I suggest we return EIO on non-allocating writes. That way the user
will know there is a problem with what they are
Am 29.06.2011 06:47, schrieb Fam Zheng:
Hi,
I have implemented reading for sparse optimized and come to implement
writing. It is a little complicated and I am not sure what is the best
approach. Could you give me some advice?
Here is the details: (pasted from http://warm.la/soc/?p=98)
On Wed, Jun 29, 2011 at 4:15 PM, Kevin Wolf kw...@redhat.com wrote:
Am 29.06.2011 06:47, schrieb Fam Zheng:
Hi,
I have implemented reading for sparse optimized and come to implement
writing. It is a little complicated and I am not sure what is the best
approach. Could you give me some
Hi,
I have implemented reading for sparse optimized and come to implement
writing. It is a little complicated and I am not sure what is the best
approach. Could you give me some advice?
Here is the details: (pasted from http://warm.la/soc/?p=98)
Stream optimized VMDK image allocates minimized
On Wed, Jun 29, 2011 at 5:47 AM, Fam Zheng famc...@gmail.com wrote:
Stream optimized VMDK image allocates minimized space for a compressed
cluster, which means if there is high compress ratio, a cluster
possibly only takes one physical sector in the file. It makes
overwriting hard, especially
