Oliver Rath | 20 Aug 11:53 2014
Picon

name matter of tpgt_1/lun/lun_0/<link2iblock> ?

Hi list,

I try to reproduce the creating of an iscsi-target via iblock device as
shown in lio_node and tcm_node. Taken from
http://www.thomas-krenn.com/de/wiki/Linux-IO_Target_%28LIO%29_unter_Ubuntu_14.04#FILEIO_.28Linux_VFS_devices.29
with targetcli:

|cd /backstores/iblock|
|create name=iscsi dev=/dev/sdb|
|cd /iscsi|
create
|cd
iscsi/root <at> dmicrash:iqn.2003-01.org.linux-iscsi.dmicrash.x8664:sn.a5bb4cf3e6cd/tpgt1/portals
# in my case
create
cd ../luns|
create /backstores/iblock/iscsi
# works fine, but here is my question point

Now I tried the same with generic commands:
cd /sys/kernel/config/target/core/
mkdir iblock_1
cd iblock_1
mkdir iblock_clone6/
echo "udev_path=/dev/myvg/clone6" > control
echo  -n 1 > enable

# Now we can create the iscsi-Target

cd cd /sys/kernel/config/target/iscsi/
(Continue reading)

Andreea-Cristina Bernat | 18 Aug 14:05 2014
Picon

[PATCH] tcm_fc: Replace rcu_assign_pointer() with RCU_INIT_POINTER()

The use of "rcu_assign_pointer()" is NULLing out the pointer.
According to RCU_INIT_POINTER()'s block comment:
"1.   This use of RCU_INIT_POINTER() is NULLing out the pointer"
it is better to use it instead of rcu_assign_pointer() because it has a
smaller overhead.

The following Coccinelle semantic patch was used:
 <at>  <at> 
 <at>  <at> 

- rcu_assign_pointer
+ RCU_INIT_POINTER
  (..., NULL)

Signed-off-by: Andreea-Cristina Bernat <bernat.ada <at> gmail.com>
---
 drivers/target/tcm_fc/tfc_sess.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/target/tcm_fc/tfc_sess.c b/drivers/target/tcm_fc/tfc_sess.c
index 21ce508..ccee7e3 100644
--- a/drivers/target/tcm_fc/tfc_sess.c
+++ b/drivers/target/tcm_fc/tfc_sess.c
 <at>  <at>  -98,7 +98,7  <at>  <at>  static void ft_tport_delete(struct ft_tport *tport)
 	ft_sess_delete_all(tport);
 	lport = tport->lport;
 	BUG_ON(tport != lport->prov[FC_TYPE_FCP]);
-	rcu_assign_pointer(lport->prov[FC_TYPE_FCP], NULL);
+	RCU_INIT_POINTER(lport->prov[FC_TYPE_FCP], NULL);

(Continue reading)

CDR | 13 Aug 08:16 2014
Picon

Fwd: targetcli does not compile

I am using opensuse latest version

make rpm
Exporting the repository files...
Cleaning up the target tree...
Fixing version string...
Generating rpm specfile from template...
Generating rpm changelog...
Generating debian changelog...
Generated release tarball:
    dist/targetcli-3.0~pre2-5-g7e32595.tar.gz
Building rpm packages...
error: line 7: Illegal char '-' in: Version:        3.0~pre2-5-g7e32595
make: *** [build/rpm-stamp] Error 1
jgross | 8 Aug 09:43 2014

Add XEN pvSCSI support

This series adds XEN pvSCSI support. With pvSCSI it is possible to use physical
SCSI devices from a XEN domain.

The support consists of a backend in the privileged Domain-0 doing the real
I/O and a frontend in the unprivileged domU passing I/O-requests to the backend.

The code is taken (and adapted) from the original pvSCSI implementation done
for Linux 2.6 in 2008 by Fujitsu.

[PATCH V2 1/4] Add XEN pvSCSI protocol description
[PATCH V2 2/4] Introduce xen-scsifront module
[PATCH V2 3/4] Introduce XEN scsiback module
[PATCH V2 4/4] add xen pvscsi maintainer

Changes in V4:
- Re-add define for VSCSIIF_ACT_SCSI_SG_PRESET to vscsiif.h to indicate this
  action value should not be used in future enhancements

Changes in V3:
- added some comments to the protocol header file
- removed the CDB emulation from xen-scsiback, handled by core target
  infrastructure
- several changes in xen-scsifront after comments from Christoph Hellwig

Changes in V2:
- use core target infrastructure by backend instead of pure SCSI passthrough
- add support for larger SG lists by putting them in grant page(s)
- add command abort capability

(Continue reading)

Sebastian Herbszt | 5 Aug 00:07 2014
Picon
Picon

Emulex target mode support

Hello Nicholas,

few years ago you had WIP code for lpfc TM / tcm_lpfc.
Any plans to resurrect it?

Sebastian
jgross | 4 Aug 10:27 2014

[PATCH V3 0/4] Add XEN pvSCSI support

This series adds XEN pvSCSI support. With pvSCSI it is possible to use physical
SCSI devices from a XEN domain.

The support consists of a backend in the privileged Domain-0 doing the real
I/O and a frontend in the unprivileged domU passing I/O-requests to the backend.

The code is taken (and adapted) from the original pvSCSI implementation done
for Linux 2.6 in 2008 by Fujitsu.

[PATCH V2 1/4] Add XEN pvSCSI protocol description
[PATCH V2 2/4] Introduce xen-scsifront module
[PATCH V2 3/4] Introduce XEN scsiback module
[PATCH V2 4/4] add xen pvscsi maintainer

Changes in V3:
- added some comments to the protocol header file
- removed the CDB emulation from xen-scsiback, handled by core target
  infrastructure
- several changes in xen-scsifront after comments from Christoph Hellwig

Changes in V2:
- use core target infrastructure by backend instead of pure SCSI passthrough
- add support for larger SG lists by putting them in grant page(s)
- add command abort capability

Jerome Martin | 31 Jul 20:00 2014
Picon

targetcli/rtslib reunification

Hi Christoph, Andy et al.,

I am splitting this reply out the the original thread, as I feel this 
deserves a topic on its own.

On 07/29/2014 06:47 PM, Andy Grover wrote:> On 07/29/2014 06:24 AM, 
Christoph Hellwig wrote:
 >> Btw, what's the status of the targetcli trees?  I though with the
 >> licensing updates we'd be able to get a unified version again.

First of all thanks Christoph for bringing the reunification topic on 
the table, and thanks Andy for confirming below your are all for it :-)

This would be really beneficial for all users if we can make that happen 
as soon as possible.

 > The status of the trees is.. they've diverged. targetcli-fb in many
 > smaller ways, and Datera targetcli in the addition of a new config API.
 > See below.

Yes, diverged is the word. I even think the -fb API diverged so much as 
to have compatibility problems with the main branch API :-(

 > Both are Apache-licensed now, so licensing is fixed. The remaining
 > issues I see are reunifying the code and cooperating on development.

<nod>

 > Regarding the code, Jerome, I'd really like to carry across the
 > improvements in -fb, but think there were things that I removed
(Continue reading)

Noemi Alvarez | 29 Jul 10:23 2014
Picon

Hello


I want to keep up with you with hope for friendship if you are interested.
If you don't mind i will like you to write me back. I am waiting to read
from you, because i have something important and urgent to discuss with
you. I will also send some of my beautiful photos to you.

Lee Duncan | 26 Jul 01:46 2014

Can VPD Unit Serial Number be persistent?

Hi:

I am creating an iSCSI LUNs using iblock back end storage.

I notice that my VPD Unit Serial Number is different each time my server
reboots. That does not seem right.

Is this a bug?

I looked back through the list archives and saw that you do not allow
this attribute to be set at back store creation time, but there is an
option to tell it not generate a WWN. (using generate_wwn=false)

But when I do that I get no VPD Page 0x83 data at all, and the name of
the resulting target, once connected, in /dev/disk/by-id is scsi-1LIO-ORG.

It does not seem right that the identity of the disc changes each time
the server is rebooted.
--

-- 
Lee Duncan

jgross | 25 Jul 13:37 2014

[PATCH V2 0/4] Add XEN pvSCSI support

This series adds XEN pvSCSI support. With pvSCSI it is possible to use physical
SCSI devices from a XEN domain.

The support consists of a backend in the privileged Domain-0 doing the real
I/O and a frontend in the unprivileged domU passing I/O-requests to the backend.

The code is taken (and adapted) from the original pvSCSI implementation done
for Linux 2.6 in 2008 by Fujitsu.

[PATCH V2 1/4] Add XEN pvSCSI protocol description
[PATCH V2 2/4] Introduce xen-scsifront module
[PATCH V2 3/4] Introduce XEN scsiback module
[PATCH V2 4/4] add xen pvscsi maintainer

Changes in V2:
- use core target infrastructure by backend instead of pure SCSI passthrough
- add support for larger SG lists by putting them in grant page(s)
- add command abort capability
Fabian Morision | 24 Jul 14:47 2014
Picon

Re: Very Urgent............

Greetings from gulf region

Thanks for the e-mail. I am very interested on funding lucrative
business partnership with you acting as the manager and sole
controller of the investment while i remain a silent investor for a
period of ten yrs , though I am only looking at investment
opportunities within the range you specified for a start. You can
reply me here (fmorision <at> yahoo.com)

Let me know your thought asap.

Regards

Financial Consultant

Mr.Fabian Morision

Gmane