similar to: iscsi target for C5.x

I am trying to install Oracle RAC in a two node cluster for testing purposes, so performance is not something that concerns me. I just want to go through the process all the way to creating a database. I have all the prerequisites except the shared storage and thought I'd give this a try. I'm running: - CentOS 5.3 kernel 2.6.18-164.el5 - iscsitarget-1.4.18-1 -

I was looking up on iSCSI in preparation and became aware that there are different iSCSI software/drivers/whatever-is-the-correct-term available. e.g. IET http://iscsitarget.sourceforge.net/ SCST http://scst.sourceforge.net/ STGT http://stgt.berlios.de/ LIO http://linux-iscsi.org/ Based on what I can see, it seems to be STGT because the site provides a link to Redhat advisory which seems to

I always used IET on CentOS but I have a quick server to setup to backup some VM's, then migrate to DAS on another server and the easiest way for me will be to accomplish this via iSCSI vmfs stores. I figured I would just use the ini that ships with CentOS but have never used it against ESX, anyone do this and have experiences they care to share? Should it be trivial or are there any non

Can someone point me to some documentation on how to set up centos 5.0 as an iscsi target? I'm completely new to iscsi so need something basic. _____________________________________ "He's no failure. He's not dead yet." William Lloyd George -------------- next part -------------- An HTML attachment was scrubbed... URL:

Out of haste I decided for the first time not to pull down and compile iet to export a single volume to a windows machine so I just used tgtd. Well, much more time later than otherwise would be the case had I used iet, when I mount the volume on the windows ini, it can't find and install a driver? WTF? This have anything to do with the tgtd being a tech preview:) Anybody seen this b4? jlc

Hello, I have been using Xen now for several months and have been quite successful until attempting to utilize iscsi within my domU''s. My research has turned up many posts of people using iscsi with no problems, and I have found no others with the problem I seem to be experiencing. If this has been covered on this list in the past, please accept my humble apologies. Configuration:

Hello all, I got some severe iscsi connection loss on my dom0 (Gentoo 2.6.20-xen-r6, xen 3.1.1). Happening several times a day. open-iscsi version is 2.0.865.12. Target iscsi is the open-e DSS product. Here is a snip of my messages log file: May 5 16:52:50 ying connection226:0: iscsi: detected conn error (1011) May 5 16:52:51 ying iscsid: connect failed (111) May 5 16:52:51 ying iscsid:

Hi all, I would like to know if I could share some space on on of my servers, to another server(s) using the iSCSI protocal? I can see that CentOS can connect to an iSCSI server, but can it act as a iSCSI server? Is so, does anyone have some good HOWTO / tutorials / docs on how to set it up? I'm running CentOS 5.2 -- Kind Regards Rudi Ahlers

Hello fellow sysadmins! I've assembled a whitebox system with a SuperMicro motherboard, case, 8GB of memory and a single quad core Xeon processor. I have two 9650SE-8LPML cards (8 ports each) in each server with 12 1TB SATA drives total. Three drives per "lane" on each card. CentOS 5.2 x86_64. I'm looking for advice on tuning this thing for performance. Especially for the

Dear all, I am trying to estimate simultaneous equation model concerning growth in russian regions. I run the analysis by means of FIML in R sem package. I am not familiar with SEM yet, but I've just got several suitable estimated specifications. Nevertheless, sometimes R gives the following warning message: Warning message: Negative parameter variances. Model is probably underidentified.

I made this change (not specifically changing from a list to a string, but changing from a hardcoded value to the value that was actually decided by cmake), and I checked that it works with cmake 2.8.12.2 which is the minimum version set in CMakeLists.txt. So if it doesn’t work with cmake 3.1/3.2 then that looks like something new that was introduced after 2.8.12.2. I’ll have a look at this

Hi everyone, I need some help to setup my configuration failover system. My goal is to have a redundance system using Xen + DRBD + Corosync + Pacemaker On Xen I will have one virtual machine. When this computer has network down, I will do a Live migration to the second computer. The first configuration I will need is a crossover cable, won''t I? It is really necessary? Ok, I did it. eth0

I'm having trouble updating my iscsitarget modules, and it seems to be related to a naming convention mixup? here's the output of the build command: [root at vmhost ~]# rpmbuild --rebuild --sign iscsitarget-0.4.14.96-0.amherst.src.rpm Installing iscsitarget-0.4.14.96-0.amherst.src.rpm error: Failed build dependencies: kernel-devel = 2.6.9-42.0.10.ELlarge is needed by

LLVM_DEFINITIONS used to be defined as set(LLVM_DEFINITIONS "-D__STDC_LIMIT_MACROS" "-D__STDC_CONSTANT_MACROS") Now it is defined as set(LLVM_DEFINITIONS " -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS") (note that it is no longer a cmake list but a string, and the string contains a leading space!) This causes CMake 3.1 to emit g++ -D

Hello, Need anyone's help regarding issues I encountered during make on iscsitarget-1.40.20 which I get from "svn co https://iscsitarget.svn.sourceforge.net/svnroot/iscsitarget/trunkiscsitarget" checkout revision 481 Issues where found below after a series of my command, as shown: [junix at thesisQRMproject iscsitarget]$ make *cc:

Hi List, I've started looking into iSCSI, and I'm wondering if there is an iSCSI target (I've found the initiator in iscsi-initiator-utils) that ships with CentOS, or if not, what the recommended target would be. I'd like to export either a partition or (preferably) a file-as-a-partition. Yours, -S -- Simen Thoresen, Wulfkit Support, Dolphin ICS

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

On Tue, Jan 27, 2015 at 10:02 AM, Mueller-Roemer, Johannes Sebastian <Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote: > Adding -D__MSVCRT_VERSION__=0x900 (or higher) to CMAKE_CXX_FLAGS and > -lmsvcr90 (or higher) to CMAKE_CXX_STANDARD_LIBRARIES appears to work. > -lmsvcrt80 does not work, contrary to the comment on the MinGW bug tracker. > However, if you do not

I am currently setting up my Module with module->setTargetTriple(llvm::sys::getProcessTriple() #ifdef _WIN32 + "-elf" #endif ); And my ExecutionEngine with llvm::EngineBuilder(std::move(module)) .setErrorStr(&err) .setMCPU(llvm::sys::getHostCPUName())

This hotplug script has been tested with IET and NetBSD iSCSI targets, without authentication. This hotplug script will only work with PV guests not using pygrub. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com> Cc: Ian Jackson <ian.jackson@citrix.com> --- Changes due to 4.3 release freeze: * We can no longer provide a