LVM over ISCSI issue

[Amin Vakil]

> 
> 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 ?
> 

I should've mentioned that I have cloned successfully with discard
enabled, but it randomly faults, right now with discard enabled
everything is fine and I clone from iscsi to local and from local to
iscsi with no problem. I tried multiple times to reproduce the errors
you see below.

> 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 ?
> 
Just regular PVE updates, latest update right now.
root at myhostname:~# pveversion
pve-manager/6.2-10/a20769ed (running kernel: 5.4.34-1-pve)


Error, discard enabled: http://ix.io/2tY3 http://ix.io/2tY4
Notice the time of errors. dmesg was giving errors at first, but proxmox
didn't. Second time dmesg and proxmox both gave error and proxmox
migration failed.

OK, discard disabled: http://ix.io/2tY6 http://ix.io/2tY7
Notice the dmesg error, there was an error but proxmox continues to do
the migration.

I just think for some reason somehow proxmox continues sometimes when it
gets the error below and sometimes not. I've faced the error with
enabled discard too. http://ix.io/2tXD, Although as you've noticed
proxmox errors are different.

kernel: sd 1:0:0:0: [sdb] tag#74 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
kernel: sd 1:0:0:0: [sdb] tag#74 Sense Key : Not Ready [current]
kernel: sd 1:0:0:0: [sdb] tag#74 Add. Sense: Logical unit communication
failure
kernel: sd 1:0:0:0: [sdb] tag#74 CDB: Write Same(10) 41 00 69 09 a7 f7
00 ff ff 00

Do you have any reason leading you to believe enabling discard is the
problem? Because I got error with discard enabled right now only once
and unfortunately I cannot reproduce the error again neither with
discard enabled nor discard disabled.

Thank you for your replies.


> Y.
> 
> 
> On Wed, 12 Aug 2020 at 09:12, Amin Vakil via pve-user <
> pve-user at lists.proxmox.com> wrote:
> 
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Amin Vakil <info at aminvakil.com>
>> To: pve-user at lists.proxmox.com
>> 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 <pve-user at lists.proxmox.com>
>> To: pve-user at lists.proxmox.com
>> Cc: Amin Vakil <info at aminvakil.com>
>> Bcc:
>> Date: Wed, 12 Aug 2020 12:42:10 +0430
>> Subject: [PVE-User] LVM over ISCSI issue
>> _______________________________________________
>> pve-user mailing list
>> pve-user at lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> pve-user mailing list
> pve-user at lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> 
> 
> ------------------------------
> 
> End of pve-user Digest, Vol 149, Issue 8
> ****************************************
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20200812/59953e8b/attachment.sig>