On Thu, Jun 18, 2020 at 04:58:54PM +0200, Dietmar Maurer wrote:
> May I request that you open a bug at: https://bugzilla.proxmox.com
> That way it is easier to track the bug status ...
Sure thing, will do later today.
___
pve-devel mailing list
pve-devel
May I request that you open a bug at: https://bugzilla.proxmox.com
That way it is easier to track the bug status ...
> On 06/18/2020 3:22 PM Dietmar Maurer wrote:
>
>
> > Don't get me wrong, I just wanted to report what IMO is a bug in a
> > backup tool (an actually pretty clever one looking a
> Don't get me wrong, I just wanted to report what IMO is a bug in a
> backup tool (an actually pretty clever one looking at the format), and
> that to me is the point of view that really matters here.
Sure, this is clearly a bug a we should fix it - thanks for reporting.
But AFAIK this does not
On Wed, Jun 17, 2020 at 06:03:25PM +0200, Dietmar Maurer wrote:
> > I initially noticed that backup/restore has a bug when the disk size is
> > not a multiple of 64K for DRBD devices.
>
> But qemu block size is 64K, so disk size should/must always be a multiple of
> 64K?
hm, I think this depend
> I initially noticed that backup/restore has a bug when the disk size is
> not a multiple of 64K for DRBD devices.
But qemu block size is 64K, so disk size should/must always be a multiple of
64K?
AFAIK we never generate such disk sizes?
___
pve-deve
Dear Proxmox developers,
I hope it is fine to report this here, otherwise I can repost on
pve-user.
I initially noticed that backup/restore has a bug when the disk size is
not a multiple of 64K for DRBD devices. Due to DRBD meta-data the user
visible size is almost certainly not 64K aligned. But
