Proxmox VE 4.2 MAJOR iSCSI bug?

[tomstephens89]

I have been spending the last 2 days trying to work out why I cannot restore or create any VM's onto my iSCSI backed LVM storage on a brand new 16 node Proxmox VE 4.2 cluster.

The nodes are able to create logical volumes in the volume groups however when data starts writing, things grind to a halt and fail.

I have rebuilt my MPIO config more than once, even removed it and just done iSCSI > LVM through the GUI, but I still have the same results.

Then to my dismay I have come across a known issue and I believe Proxmox 4.2 is effected!

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805252

https://forum.proxmox.com/threads/problem-with-4-0-kernel-and-iscsi-backend.24821/

Help!

Can someone comment on this or confirm that this is still an issue/has been fixed?

Syslog is full of this upon new vm os install:

Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#0 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 01 04 55 10 00 00 3d c8 00 00
Jul 27 18:52:46 apollo01 kernel: blk_update_request: critical target error, dev sdd, sector 17061136
Jul 27 18:52:46 apollo01 kernel: blk_update_request: critical target error, dev dm-7, sector 17061136
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#2 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#2 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#2 CDB: Write(16) 8a 00 00 00 00 00 01 04 15 10 00 00 40 00 00 00
Jul 27 18:52:46 apollo01 kernel: blk_update_request: critical target error, dev sdj, sector 17044752
Jul 27 18:52:46 apollo01 kernel: blk_update_request: critical target error, dev dm-7, sector 17044752
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#0 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#0 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#0 CDB: Write(16) 8a 00 00 00 00 00 01 04 92 d8 00 00 22 e0 00 00
Jul 27 18:52:46 apollo01 kernel: blk_update_request: critical target error, dev sdj, sector 17076952
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#1 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#1 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#1 CDB: Write(16) 8a 00 00 00 00 00 01 04 b6 80 00 00 14 a8 00 00
Jul 27 18:52:46 apollo01 kernel: blk_update_request: critical target error, dev sdd, sector 17086080
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#0 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#0 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#0 CDB: Write(16) 8a 00 00 00 00 00 01 04 cb 40 00 00 17 30 00 00
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 CDB: Write(16) 8a 00 00 00 00 00 01 04 f1 80 00 00 1c d8 00 00
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#5 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#5 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 7:0:0:1: [sdd] tag#5 CDB: Write(16) 8a 00 00 00 00 00 01 06 10 00 00 00 15 b0 00 00
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 Sense Key : Illegal Request [current]
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 Add. Sense: Invalid field in cdb
Jul 27 18:52:46 apollo01 kernel: sd 8:0:0:1: [sdj] tag#1 CDB: Write(16) 8a 00 00 00 00 00 01 06 25 c0 00 00 1b 58 00 00

 

[tomstephens89]

Anyone? Nothing I do is getting iSCSI working. After anything starts writing, I get failures.

 

[tomstephens89]

Well I had a feeling that changing max_sectors_kb to 512 instead of 32767 might help on all sd and dm devices under /sys/block might help, but it done nothing.

 

[tomstephens89]

Well I had a feeling that changing max_sectors_kb to 512 instead of 32767 might help on all sd and dm devices under /sys/block might help, but it done nothing.

So I created udev rules to set the max_sectors_kb to 512 on all block devices however even though I confirm it sets the values, it seems that as soon as something uses the device, it is reset back to 32767.

Help!

 

[tomstephens89]

This appears to be due to the adoption of the Ubuntu kernel?

 

[tomstephens89]

No-one care to shine any light on this then?

 

[anigwei]

No-one care to shine any light on this then?

Tom, did you manage to solve it?

I have the same problem with a SAS Controller... (https://forum.proxmox.com/threads/troubles-iscsi-and-max_sectors_kb.25750/#post-164684)

Thanks!