The fact that it was successful at least once with the discard option disabled is a progress in my opinion. Did you ever have a successful clone job with discard enabled ?
Also, the error seems to be different in each case... with discard enabled: qemu-img: error while writing at byte 1990201344:* Input/output error* with discard disabled: qemu-img: error while writing at byte 2147483136: *Device or resource busy* Can you check also in dmesg for any clues during each case ? Also, when was the last time this was working without issues ? any changes both on PVE and NAS side after that ? Y. On Wed, 12 Aug 2020 at 09:12, Amin Vakil via pve-user < [email protected]> wrote: > > > > ---------- Forwarded message ---------- > From: Amin Vakil <[email protected]> > To: [email protected] > Cc: > Bcc: > Date: Wed, 12 Aug 2020 12:42:10 +0430 > Subject: [PVE-User] LVM over ISCSI issue > No difference, totally random. > > Also here are the logs of clones in case I'm missing something. > > Error, discard enabled: http://ix.io/2tXB > OK, discard disabled: http://ix.io/2tXC > Error, discard disabled: http://ix.io/2tXD > > > Just out of curiosity, can you temporarily disable discard support on > > the > > target VM disk to see if that will make a difference? > > > > > ---------- Forwarded message ---------- > From: Amin Vakil via pve-user <[email protected]> > To: [email protected] > Cc: Amin Vakil <[email protected]> > Bcc: > Date: Wed, 12 Aug 2020 12:42:10 +0430 > Subject: [PVE-User] LVM over ISCSI issue > _______________________________________________ > pve-user mailing list > [email protected] > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > _______________________________________________ pve-user mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
