On Fri, 2017-09-29 at 09:21 -0400, Martin K. Petersen wrote: > Laurence, > > > I am testing this but its not being picked up so I want to know if > > I > > have the kernel command line wrong here. > > > > scsi_dev_flags=LIO-ORG:thin2:0x80000000 > > > > What am I doing wrong to pass the BLIST flags. > > This worked for me: > > [root@kvm ~]# echo "Linux:scsi_debug:0x80000000" > > /proc/scsi/device_info > [root@kvm ~]# grep Linux /proc/scsi/device_info > 'Linux ' 'scsi_debug ' 0x80000000 > [root@kvm ~]# modprobe scsi_debug unmap_max_blocks=10 > unmap_max_desc=1 write_same_length=20 lbpws=1 > [root@kvm ~]# lsblk -D > NAME DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO > sda 0 512B 5K 0 > > (With the caveat that I tweaked scsi_debug to report the UNMAP > parameters despite lbpu being 0). > OK, Thanks, that is working now and I pick up the correct size now. Its going to be very useful for these corner case array inconsistencies. Tested-by: Laurence Oberman <loberman@xxxxxxxxxx> Sep 29 09:56:11 localhost kernel: scsi 1:0:0:50: Direct-Access LIO- ORG thin2 4.0 PQ: 0 ANSI: 5 Sep 29 09:56:11 localhost kernel: scsi 1:0:0:50: alua: supports implicit and explicit TPGS Sep 29 09:56:11 localhost kernel: scsi 1:0:0:50: alua: device naa.6001405f7aa27ca453f4381a00f22ea6 port group 0 rel port 2 Sep 29 09:56:11 localhost kernel: sd 1:0:0:50: Attached scsi generic sg64 type 0 Sep 29 09:56:11 localhost kernel: RHDEBUG: unmap_limit_for_ws set by kernel flag for case SD_LBP_WS16 Sep 29 09:56:11 localhost kernel: sd 1:0:0:50: [sdbl] 81920000 512-byte logical blocks: (41.9 GB/39.1 GiB) Sep 29 09:56:11 localhost kernel: sd 1:0:0:50: [sdbl] Write Protect is off Sep 29 09:56:11 localhost kernel: sd 1:0:0:50: [sdbl] Write cache: enabled, read cache: enabled, supports DPO and FUA Sep 29 09:56:11 localhost kernel: sd 1:0:0:50: alua: transition timeout set to 60 seconds