Re: [PATCH v8] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

2016-06-29 Thread Bryant G. Ly
On 6/29/16, 9:54 AM, "Bart Van Assche" wrote: On 06/29/2016 04:43 PM, Bryant G. Ly wrote: >> It looks like the masking fixes the device mapper’s ability to find the >> disk…. > Is the multipath client available in

Re: [PATCH v8] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

2016-06-29 Thread Bart Van Assche
On 06/29/2016 04:43 PM, Bryant G. Ly wrote: It looks like the masking fixes the device mapper’s ability to find the disk…. Is the multipath client available in your initrd? If so, running multipath -ll -v with n >= 3 should reveal why multipathd ignored certain disks. Bart. -- To

Re: [PATCH v8] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

2016-06-29 Thread Bryant G. Ly
On 6/29/16, 12:49 AM, "Bart Van Assche" wrote: >> I was hoping someone in the community can help answer this: >> >> If I were to remove the masking off of the lun addressing method prior to >>

Re: [PATCH v8] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

2016-06-28 Thread Bart Van Assche
On 06/28/2016 10:57 PM, Bryant G. Ly wrote: I was hoping someone in the community can help answer this: If I were to remove the masking off of the lun addressing method prior to target_submit_cmd/target_submit_tmr then I get a hang within scsi probe on bootup. (srp->lun.scsi_lun[0] &= 0x3f;

Re: [PATCH v8] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

2016-06-28 Thread Bryant G. Ly
On 6/27/16, 3:17 PM, "Michael Cyr" wrote: + cmd->se_cmd.tag = be64_to_cpu(srp->tag); + + spin_lock_bh(>intr_lock); + list_add_tail(>list, >active_q); + spin_unlock_bh(>intr_lock); + +