Am 26.11.2013 um 19:02 hat Anthony Liguori geschrieben:
Max Reitz mre...@redhat.com writes:
This series fixes the drive-mirror blockjob in case of none sync mode
to always use the old (current) image file as the backing file of the
newly created mirrored file (in case of absolute-paths
Kevin Wolf kw...@redhat.com writes:
Am 26.11.2013 um 19:02 hat Anthony Liguori geschrieben:
Max Reitz mre...@redhat.com writes:
This series fixes the drive-mirror blockjob in case of none sync mode
to always use the old (current) image file as the backing file of the
newly created
Il 25/11/2013 20:28, Max Reitz ha scritto:
This series fixes the drive-mirror blockjob in case of none sync mode
to always use the old (current) image file as the backing file of the
newly created mirrored file (in case of absolute-paths mode).
It is rather important to get this into 1.7, as
Max Reitz mre...@redhat.com writes:
This series fixes the drive-mirror blockjob in case of none sync mode
to always use the old (current) image file as the backing file of the
newly created mirrored file (in case of absolute-paths mode).
It is rather important to get this into 1.7, as we
This series fixes the drive-mirror blockjob in case of none sync mode
to always use the old (current) image file as the backing file of the
newly created mirrored file (in case of absolute-paths mode).
It is rather important to get this into 1.7, as we will introduce an at
least pretty strange
