Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.
John R Pierce wrote:
Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.
You can, if you want to use IET, look at the RPMs at http://atrpms.net/dist/el5/iscsitarget/. Have no experience with them, so cannot vouch for them.
You can also look at the tech-preview TGT implementation included in CentOS 5.3. Install the scsi-target-utils package and maybe look at http://www.cyberciti.biz/tips/howto-setup-linux-iscsi-target-sanwith-tgt.htm... or similar (Google) for inspiration. -Alan
i use the atrpm iscsitarget for a long time now in high traffic setups. it performs very well, and is rock solid. no problems until now. go for it :) but disabling the atrpms repo after installing the iscsitarget wouldnt be a bad idea.
i wont go with userspace solutions like tgt, my benchmarks showed much more higher system load, lower transfer rates and lags from time to time. go for the kernel implemention
cheers
Juergen
Alan Sparks wrote:
John R Pierce wrote:
Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.
You can, if you want to use IET, look at the RPMs at http://atrpms.net/dist/el5/iscsitarget/. Have no experience with them, so cannot vouch for them.
You can also look at the tech-preview TGT implementation included in CentOS 5.3. Install the scsi-target-utils package and maybe look at http://www.cyberciti.biz/tips/howto-setup-linux-iscsi-target-sanwith-tgt.htm... or similar (Google) for inspiration. -Alan
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Juergen Gotteswinter wrote:
i use the atrpm iscsitarget for a long time now in high traffic setups. it performs very well, and is rock solid. no problems until now. go for it :) but disabling the atrpms repo after installing the iscsitarget wouldnt be a bad idea.
i wont go with userspace solutions like tgt, my benchmarks showed much more higher system load, lower transfer rates and lags from time to time. go for the kernel implemention
according to what I read, tgt uses kernel drivers that are built into the 2.6.x kernel including rhel5.3 and are based on the IET drivers.
On Oct 16, 2009, at 8:24 PM, John R Pierce pierce@hogranch.com wrote:
Juergen Gotteswinter wrote:
i use the atrpm iscsitarget for a long time now in high traffic setups. it performs very well, and is rock solid. no problems until now. go for it :) but disabling the atrpms repo after installing the iscsitarget wouldnt be a bad idea.
i wont go with userspace solutions like tgt, my benchmarks showed much more higher system load, lower transfer rates and lags from time to time. go for the kernel implemention
according to what I read, tgt uses kernel drivers that are built into the 2.6.x kernel including rhel5.3 and are based on the IET drivers.
Not really one of the original developers of IET got together with one of the original developers of open-iscsi and they made a universal target, tgt. The target was designed to handle iSCSI, FCoE, and more as plugins. The kernel module handles the plugin framework part, but all the iSCSI processing and IO happens in user space.
It's a nifty piece of software, but in my opinion it's like a Swiss army knife, does a lot, but is complicated and doesn't really do any one thing very well.
IET was designed to be simple, do iSCSI and only iSCSI and do it well.
As for building from tarball, there is an RPM spec file included in there, so to build an RPM you just download the tarball then do a:
# rpmbuild -ta iscsitarget-1.4.18.tar.gz
Then after a little while, presto, RPMs in /usr/src/redhat/RPMS.
You of course need, gcc, kernel-devel, make, patch, binutils, rpm- build, redhat-rpm-config and openssl-devel installed first as a prerequisite.
-Ross
Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.
The current trunk of iet has a good spec. The inbox target is still a bit weak.
jlc
On Oct 16, 2009, at 2:42 PM, John R Pierce pierce@hogranch.com wrote:
Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.
If you do compile it yourself start with the 1.4.18 release and use the .spec that comes with it to rpmbuild either a kabi tracking module or a dkms module so the maintenance is minimal.
-Ross
Ross Walker wrote:
On Oct 16, 2009, at 2:42 PM, John R Pierce pierce@hogranch.com wrote:
Does anyone have any recommendations for the best way to bring up a iSCSI Target on a C5.3+ server ? Various blogs suggest compiling IET from source, but thats not real appealing to me (not that I can't do it, I just don't want to have to support it long term). I looked in rpmforge but didn't see anything.
If you do compile it yourself start with the 1.4.18 release and use the .spec that comes with it to rpmbuild either a kabi tracking module or a dkms module so the maintenance is minimal.
i haven't gotten desperate enough to try a tarball build yet, rather, I've been trying to rpmbuild from various -supposed to work with rhel5/centos5- .src.rpm's... rotten karma so far.
can't use ATRPM's prebuilt RPMs, they want vmlinuz-2.6.18-164.2.1.el5 and I have 2.6.18-164.el5 which afaik is the latest centos5.3+ kernel
I've tried variations on http://sourceforge.net/apps/mediawiki/iscsitarget/index.php?title=RedHat_ins... using about every .src.rpm there and they all get various build errors, typically culminating in...
.../BUILD/iscsitarget-0.4.12/kernel/iscsi_dbg.h:39:5: warning: "D_IOV" is not defined .../BUILD/iscsitarget-0.4.12/kernel/iscsi_dbg.h:51:5: warning: "D_DUMP_PDU" is not defined .../BUILD/iscsitarget-0.4.12/kernel/event.c: In function 'event_init': .../BUILD/iscsitarget-0.4.12/kernel/event.c:102: warning: passing argument 2 of 'netlink_kernel_create' makes integer from pointer without a cast .../BUILD/iscsitarget-0.4.12/kernel/event.c:102: error: too few arguments to function 'netlink_kernel_create'
I've tried all three of these .src.rpm's from http://www.cryptoforge.net/iscsi/RPMS/ anyways... iscsitarget-0.4.12-6.src.rpm iscsitarget-0.4.13-0.1264.2.src.rpm iscsitarget-0.4.13-0.1266.1.src.rpm
afaik, I have all the required -devel packages installed. this is a virgin install of 5.3 x86_64 w/ yum -y update as of now.....
OH WAIT. now why didn' someone tell me about this earlier? http://bitbud.com/2009/05/27/installing-the-iscsi-target-framework-tgt/
its a NATIVE FEATURE, not IET, rather, the new kernel iscsi is in 5.3
well, THAT was Easy!
-
Alan Sparks -
John R Pierce -
Joseph L. Casale -
Juergen Gotteswinter -
Ross Walker