Hello,
You didn't say what iSCSI target you are using. This PDF below covers
how to use open-iSCSI with RHEL v6.x / 7.x with Dell PS Series SANs. The
open-iSCSI part is basically the same for all iSCSI. With one major
exception. Dell PS Series iSCSI SANs have all the IPs for iSCSI in the
As Ulrich replied, there's not much we can do with the data you provided.
On Wednesday, December 16, 2020 at 12:29:20 PM UTC-8 go xayyasang wrote:
> [root@target ~]# iscsiadm -m node -o show
> iscsiadm: No records found
>
>
That's normal if you have no records in your database. If you want
>>> go xayyasang schrieb am 06.12.2020 um 15:38 in
Nachricht :
> [root@target ~]# iscsiadm -m node -o show
> iscsiadm: No records found
Hi!
Obviously something is not as you expect. Without knowing details, nobody can
help you.
Please take the time to explain what you did
[root@target ~]# iscsiadm -m node -o show
iscsiadm: No records found
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To
If you enter the mount command at this point, what mount points are still
mounted? Screenshot has some contradictions.
On Thu, Dec 12, 2019 at 8:08 PM can zhu wrote:
>
> @The Lee-Man Thanks, In my environment， the default value of the
> node.startup is automatic in config
>
>
>
> The
@The Lee-Man Thanks, In my environment， the default value of the
node.startup is automatic in config
The Lee-Man 于2019年12月13日周五 上午5:17写道：
> Okay, I checked CentOS 8, and the services seem very similar to what I'm
> familiar with.
>
> You do indeed need to make sure your nodes have startup
Okay, I checked CentOS 8, and the services seem very similar to what I'm
familiar with.
You do indeed need to make sure your nodes have startup set to automatic.
Use something like:
> zsh> sudo iscsiadm -m node --op update --name 'node.conn[0].startup'
--value automatic
to update all nodes
On Tuesday, December 10, 2019 at 6:25:00 AM UTC-8, can zhu wrote:
>
> os version:
>
> CentOS Linux release 7.4.1708 (Core)
>
> kernel version:
>
> 3.10.0-693.el7.x86_64
>
>
> systemd version:
>
> *systemd*-219-42.el7.x86_64
>
>
> Mount iscsi devices on the node(iscsi client node) and reboot os,
Have you encountered such a problem? Could you give me some suggestions?
Ulrich Windl 于2019年12月10日周二 下午10:31写道：
> Hi!
>
> I think the problem is more related to systemd, rather than iscsi.
> Personally I hate systemd, but you don't wnat to know that...
>
> Regards,
> Ulrich
>
> >>> can zhu
Hi!
I think the problem is more related to systemd, rather than iscsi.
Personally I hate systemd, but you don't wnat to know that...
Regards,
Ulrich
>>> can zhu schrieb am 10.12.2019 um 15:25 in Nachricht
<372db1a3-424d-4063-bcdb-ccb0b821d...@googlegroups.com>:
> os version:
>
> CentOS Linux
os version:
CentOS Linux release 7.4.1708 (Core)
kernel version:
3.10.0-693.el7.x86_64
systemd version:
*systemd*-219-42.el7.x86_64
Mount iscsi devices on the node(iscsi client node) and reboot os, hangs:
[image: WechatIMG2178.png]
--
You received this message because you are
>>> "Ulrich Windl" schrieb am 14.02.2019 um
09:05 in Nachricht <5c65213302a10002f...@gwsmtp1.uni-regensburg.de>:
> filesystems like ext3 occasionally make bug requests (like 1000 sectors), and
Sorry: s/bug/big/
--
You received this message because you are subscribed to the Google Groups
>>> ASVINCHANDAR SELVARAJ schrieb am 14.02.2019 um
>>> 06:03
in Nachricht
:
> I tried this
>
> Centos 7.4
>
> echo '4096000' > /sys/block/sdb/queue/max_sectors_kb
>
> But I am getting Input/output error
Actually for FC SAN storage we made the opposite experience: Some filesystems
like ext3
I tried this
Centos 7.4
echo '4096000' > /sys/block/sdb/queue/max_sectors_kb
But I am getting Input/output error
On Wed, Feb 13, 2019 at 7:29 PM Chan wrote:
> Hello
>
> I am having few severe performance issues on my ceph cluster.
>
>
> Scenario 1 )When I mount a rbd volume directly
Hello
I am having few severe performance issues on my ceph cluster.
Scenario 1 )When I mount a rbd volume directly using rbd map command to
a linux kernel. I am getting good performance.
when I do dd on the above volume, I am getting 380 - 430 MB's. -- I am good
with this.
Scenario 2 )
what is old code?
在 2007年5月11日星期五 UTC+8上午3:00:51，Mike Christie写道：
>
> Thomas Eyre wrote:
> > I have iscsid started now, but iscsiadm is still having the same
> problem. Running strace iscsiadm -V still gives the same output.
> >
> > Any further suggestions?
> >
>
> If you are using the old
What distro are you running and what version?
Why are you using such a old kernel? Is this a RHEL 5 based distro? If so, it
is best to use the tools/kernel modules that come with it. They are pretty up
to date and stable.
On Aug 20, 2014, at 10:44 PM, loulang...@163.com wrote:
Any help
the function in
my program
much helply you can help me.thank you very much!
2013-08-11
cxywms
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an
email to open-iscsi
I modified it with a funciton ,and I use the function in my
program
much helply you can help me.thank you very much!
2013-08-11
cxywms
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails
On 05/29/2013 04:45 AM, Jack Daniels wrote:
[root@promax17 ~]# *iscsiadm -m discovery -t sendtargets -p 192.168.124.
iscsiadm: Discovery session to 192.168.124.245:3260 timed out.
[root@promax17 ~]# *tail -f /var/log/messages*
May 29 17:38:59 promax17 iscsid: connection2:0 is
: Device offlined - not
ready after error recovery
May 29 17:40:05 promax17 kernel: scsi 17:0:0:0: timing out command, waited
22s
[root@promax17 ~]# *iscsiadm -m session*
tcp: [2] 192.168.124.***:3260,1
iqn.2002-12.com.4bridgeworks.0013e2:eui.00041B00010013E2.0
Can anyone please help
-m session*
tcp: [2] 192.168.124.***:3260,1
iqn.2002-12.com.4bridgeworks.0013e2:eui.00041B00010013E2.0
Can anyone please help?
Thanks in advance
GB
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving
can you please contact me at liano...@gmail.com thank-you.
On Monday, April 8, 2013 1:04:01 AM UTC-4, kunhua...@gmail.com wrote:
Yes, I can provide help.
- Kun
Sent from my iPhone
On Apr 5, 2013, at 9:14 AM, lian...@gmail.com javascript: wrote:
if so please contact me, thank-you
weeks now. I have some things working but others are not. I am
running out of time and am willing to to hire someone with the
skill and experience to help me out. If this kind of request
is not accepted on this list I apologize and will stop posting
On 04/04/2013 01:46 PM, geeo...@gmail.com wrote:
Hello,
I have been trying to setup an iSCSI storage array for several weeks
now. I have some things working but others are not. I am running out of
time and am willing to to hire someone with the skill and experience to
help me out
and experience to
help me out. If this kind of request is not accepted on this list I
apologize and will stop posting at the first notice I receive. If it's
ok then please respond.
Here is what I have and need help with. I have purchased a Synology
DS1812+, running the latest DSM management
On 04/08/2013 11:16 AM, Sebastian Riemer wrote:
For Centos 6.4 you should be able to use the default bnx2i ifaces.
These also require special free and nonfree firmware. Check your kernel
config! Check your firmware-nonfree package!
Look at:
CONFIG_BNX2
CONFIG_SCSI_BNX2_ISCSI
Maybe not
to setup an iSCSI storage array for several weeks now.
I have some things working but others are not. I am running out of time and
am willing to to hire someone with the skill and experience to help me out.
If this kind of request is not accepted on this list I apologize and will
stop posting
On 08.04.2013 13:25, liano...@gmail.com wrote:
Created and iface config with the following:
# BEGIN RECORD 6.2.0-873.2.el6
ace.iscsi_ifacename = eth2
iface.transport_name = bnx2i
iface.hwaddress = 00:10:18:F3:43:00
iface.ipaddress = 192.x.x.x
iface.bootproto = static
iface.subnet_mask =
...@gmail.com wrote:
Hello,
I have been trying to setup an iSCSI storage array for several
weeks now. I have some things working but others are not. I am
running out of time and am willing to to hire someone with the
skill and experience to help me out
Hello,
I have been trying to setup an iSCSI storage array for several weeks now. I
have some things working but others are not. I am running out of time and
am willing to to hire someone with the skill and experience to help me out.
If this kind of request is not accepted on this list I
if so please contact me, thank-you.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to
Yes, I can provide help.
- Kun
Sent from my iPhone
On Apr 5, 2013, at 9:14 AM, liano...@gmail.com wrote:
if so please contact me, thank-you.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To unsubscribe from this group and stop receiving
while those hang up in the kernel, After the network is restored, it no effect
。
2012/8/28 guangjie qu qu.guang...@gmail.com
Thanks for reply Michael Christie.
I have set the open-iscsi timeout seconds:
node.session.timeo.replacement_timeout = 0
The output of command :
iscsiadm -m
On Aug 27, 2012, at 8:37 PM, guangjie qu qu.guang...@gmail.com wrote:
Thanks for reply Michael Christie.
I have set the open-iscsi timeout seconds:
node.session.timeo.replacement_timeout = 0
Do
iscsiadm -m node -T yourtarget | grep replacement_timeout
--
You received this message
It was a firewall issue my admin had me change the iptables.conf to allow
the port 3260 and the 10.address. Thanks for the help
everyone...please delete or edit any addresses for security. Thanks.
On Saturday, June 30, 2012 3:42:34 AM UTC-5, Uli wrote:
rgc-iscsi rgcoy1...@gmail.com
rgc-iscsi rgcoy1...@gmail.com schrieb am 29.06.2012 um 21:19 in Nachricht
3e8acdf5-19da-4543-aaf3-809781f49...@googlegroups.com:
How do I setup the acls?
The var/log/messages is very long.
Here some lines:
I'm not sure of the 139.169.246.129 address.
Feb 27 12:07:40 ddshost kernel:
:
connection to discovery address failed. I don't understand why this isn't
working when it seems so straightforward. Is it a firewall issue? If
anyone can help me please do.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To view this discussion
(ipa):3260. I get iscsiadm: connection to discovery address failed. I
don't understand why this isn't working when it seems so
straightforward. Is it a firewall issue? If anyone can help me please do.
Do you have the linux iscsi initiator name in whatever acls you have
setup on the target
this
isn't working when it seems so straightforward. Is it a firewall issue?
If anyone can help me please do.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To view this discussion on the web visit
https://groups.google.com/d/msg/open-iscsi
and
I don't think the server has it either. I also only have root on the
alternate debian vm's but not the host. I am getting the same errors on
the other as well even when logged in as root. My administrator is on
vacation so I can't have him help me troubleshoot for another week...and he
On 06/29/2012 02:53 PM, rgc-iscsi wrote:
Yes the 10.29... address is correct. I can ping it from the linux
though with response and I can connect and mnt the cifs share on the
drive also. It is not currently connected to the cifs share though. I
will see if my coworker can check with
Could you also tell me what type of NAS drive you have? And you are sure
it has iscsi enabled, right? When you said Windows can easily connect
did you meant with iscsi and you still have it setup to do iscsi?
On 06/29/2012 08:56 PM, Mike Christie wrote:
On 06/29/2012 02:53 PM, rgc-iscsi
I seem to be getting this over and over again in the logs:
Jun 12 09:13:40 example-server kernel: connection0:0: iscsi: detected conn
error (1011)
Jun 12 09:13:40 example-server iscsid: Kernel reported iSCSI connection 0:0
error (1011) state (3)
Jun 12 09:13:43 example-server iscsid:
On 06/12/2012 11:18 AM, awiddersh...@hotmail.com wrote:
I seem to be getting this over and over again in the logs:
Jun 12 09:13:40 example-server kernel: connection0:0: iscsi: detected conn
error (1011)
1011 is just a generic error code meaning there was a connection
problem. We do not
This indicates something went screwy. The kernel has that el5 string, so
are you using Centos or RHEL? If so what is the iscsi tools version
It is RHEL5 and the tools are as follows:
iscsi-initiator-utils-6.2.0.872-13.el5
Is there anything else in the log before or after that? Something about
On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote:
This indicates something went screwy. The kernel has that el5 string, so
are you using Centos or RHEL? If so what is the iscsi tools version
It is RHEL5 and the tools are as follows:
iscsi-initiator-utils-6.2.0.872-13.el5
Is
On 06/12/2012 11:41 AM, Mike Christie wrote:
On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote:
This indicates something went screwy. The kernel has that el5 string, so
are you using Centos or RHEL? If so what is the iscsi tools version
It is RHEL5 and the tools are as follows:
On 06/12/2012 11:45 AM, Mike Christie wrote:
On 06/12/2012 11:41 AM, Mike Christie wrote:
On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote:
This indicates something went screwy. The kernel has that el5 string, so
are you using Centos or RHEL? If so what is the iscsi tools version
It
Awesome. I'll do that and hopefully everything is happy afterward including
these random connection issues.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To view this discussion on the web visit
On 06/12/2012 11:55 AM, Mike Christie wrote:
On 06/12/2012 11:45 AM, Mike Christie wrote:
On 06/12/2012 11:41 AM, Mike Christie wrote:
On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote:
This indicates something went screwy. The kernel has that el5 string, so
are you using Centos or
On 06/12/2012 12:09 PM, Mike Christie wrote:
On 06/12/2012 11:55 AM, Mike Christie wrote:
On 06/12/2012 11:45 AM, Mike Christie wrote:
On 06/12/2012 11:41 AM, Mike Christie wrote:
On 06/12/2012 11:33 AM, awiddersh...@hotmail.com wrote:
This indicates something went screwy. The kernel has that
Understood.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com.
To unsubscribe from this group, send email to
Thanks for the help Mike. I was able to get a wireshark trace of this
problem and found that the target was misbehaving by returning
out-of-order DataIn PDUs even though open-iscsi initiator had
negotiated DataPDUInOrder=Yes. Turns out there was a firmware update
available that fixed
. It is normally a bad target type of issue, or a race/code bug.
Would setting the iscsid debug level to a non-zero value help? If so,
No.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com
Any update ?
On Tue, Aug 30, 2011 at 8:44 PM, Vivek S vivek...@gmail.com wrote:
Added comments for structures and functions.
As for being a masochist, I tried, but couldn't take it ;-P.
On Tue, Aug 30, 2011 at 12:31 PM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
Vivek S
On 09/03/2011 04:02 AM, Vivek S wrote:
Any update ?
Looks ok. Thanks for all your work on it. And thanks to Ulrich for the
review.
Just one stye comment though. The coding style we follow has us put the
leading { on the first line for structs, for, and if/else blocks. So
+struct option_help
Thanks a lot Mike !
Will follow the coding style more rigourously the next time I submit a
patch.
On Sat, Sep 3, 2011 at 10:08 PM, Mike Christie micha...@cs.wisc.edu wrote:
On 09/03/2011 04:02 AM, Vivek S wrote:
Any update ?
Looks ok. Thanks for all your work on it. And thanks to Ulrich
Vivek S vivek...@gmail.com schrieb am 29.08.2011 um 21:00 in Nachricht
CAAPU5rPY1F3bkYYyASAFbOtb6JrfGw7JSb6m=--KKUEZVmc=w...@mail.gmail.com:
Removed ordering constrains between #defines and structure elements.
Removed calculating tab width and defaulting to 8.
Hope this will do :-)
Hi!
It
vivek...@gmail.com
Date: Tue, 30 Aug 2011 20:41:05 +0530
Subject: [PATCH 1/1] Added descriptive help for iscsiadm with a few examples.
Signed-off-by: Vivek Subbarao vivek...@gmail.com
---
usr/iscsiadm.c | 407 +---
1 files changed, 387 insertions
for the port.},
...
}
would make things easier to understand and maintain (In Perl I'd use a hash to
access the help texts by the option character).
Somehow it still looks a bit messy, and I'd put those (and alike) items on a
separate line each:
opt_help[CMD_LINE_OPTION_PORTAL], opt_help
Ich schrieb am 29.08.2011 um
10:29 in Nachricht 4e5b69f102a17...@gwsmtp1.uni-regensburg.de:
[...]
Also the comment Calling tgetent again frees the buffer allocated by it.
seems to to apply to ncurses as it ignored the buffer altogether (according
Oops: Meant to write seems not to
?hl=en.
From 1220434a4d65c8e3ddc00e3cb25bbfdc17d735eb Mon Sep 17 00:00:00 2001
From: Vivek Subbarao vivek...@gmail.com
Date: Tue, 30 Aug 2011 00:25:36 +0530
Subject: [PATCH 1/1] Made iscsiadm command line help more descriptive and user friendly
by adding options description and a few examples
the end_idx in find_last_space(). Maybe using
strchr(), strrchr() or strtok(str, \t) could help you also.
For texts like:
+ printf(discoverydb\ndiscovery [DEPRECATED]\nnode\n
+ session\niface\nfw\nhost\n\n);
I'd prefer the formatting like this (if you
- 1. It's also confusing that your
start_idx is larger than the end_idx in find_last_space(). Maybe using
strchr(), strrchr() or strtok(str, \t) could help you also.
For texts like:
+ printf(discoverydb\ndiscovery [DEPRECATED]\nnode\n
+ session\niface
);
On find_last_space(str[cols-1], (cols-1), 0);:
str[cols-1] is simply str + cols - 1. It's also confusing that your
start_idx is larger than the end_idx in find_last_space(). Maybe using
strchr(), strrchr() or strtok(str, \t) could help you also.
For texts like
text.
Roughly
like
struct help {
const char *option;
const char *explanation;
};
struct help the_help[] = {
{p, Portal in ip:port format. If only ip address is specified then the
value 3260 is assumed for the port.},
{n, Name of the field to use in the update operation
-regensburg.de wrote:
Hi!
The idea is good, but I'd use a different implementation, trying to put
most text into one data structure, and then select the correct text.
Roughly
like
struct help {
const char *option;
const char *explanation;
};
struct help the_help
On 07/22/2011 12:09 PM, Vivek S wrote:
Changed the way iscsiadm displays usage help about its commands. Rather than
simply displaying each possible mode along with its options on a single
line,
the user can now ask help for each mode separately which describes the
various options and also
most text into one data structure, and then select the correct text. Roughly
like
struct help {
const char *option;
const char *explanation;
};
struct help the_help[] = {
{p, Portal in ip:port format. If only ip address is specified then the
value 3260 is assumed for the port.},
{n
ulrich.wi...@rz.uni-regensburg.de wrote:
Hi!
The idea is good, but I'd use a different implementation, trying to put
most text into one data structure, and then select the correct text.
Roughly
like
struct help {
const char *option;
const char *explanation;
};
struct
implementation, trying to put
most text into one data structure, and then select the correct text.
Roughly
like
struct help {
const char *option;
const char *explanation;
};
struct help the_help[] = {
{p, Portal in ip:port format. If only ip address is specified
Hi!
The idea is good, but I'd use a different implementation, trying to put most
text into one data structure, and then select the correct text. Roughly like
struct help {
const char *option;
const char *explanation;
};
struct help the_help[] = {
{p, Portal in ip:port format. If only ip
like
struct help {
const char *option;
const char *explanation;
};
struct help the_help[] = {
{p, Portal in ip:port format. If only ip address is specified then the
value 3260 is assumed for the port.},
{n, Name of the field to use in the update operation.},
...
};
I'd do the line
. Roughly like
struct help {
const char *option;
const char *explanation;
};
struct help the_help[] = {
{p, Portal in ip:port format. If only ip address is specified
then the value 3260 is assumed for the port.},
{n, Name of the field to use in the update
Changed the way iscsiadm displays usage help about its commands. Rather than
simply displaying each possible mode along with its options on a single
line,
the user can now ask help for each mode separately which describes the
various options and also provides some examples.
Signed-off
Hi mate,
I have fixed that problem. The reason why I cannot see the block
device is I mounted the target device(a block device) at the target
server. So nothing exported.
Thanks.
Eric
On Tue, May 10, 2011 at 1:45 PM, Mike Christie micha...@cs.wisc.edu wrote:
On 05/08/2011 12:33 AM, Lee Eric
On 05/08/2011 12:33 AM, Lee Eric wrote:
Hi,
I use iscsi-initiator to login the target it said successful. But I
cannot see any added block device.
[root@server /]# iscsiadm -m node -T
iqn.2011-05.internal.herdingcat:storage.lvm1 -l
Logging in to [iface: default, target:
Hi,
I use iscsi-initiator to login the target it said successful. But I
cannot see any added block device.
[root@server /]# iscsiadm -m node -T
iqn.2011-05.internal.herdingcat:storage.lvm1 -l
Logging in to [iface: default, target:
iqn.2011-05.internal.herdingcat:storage.lvm1, portal:
On 03/18/2010 05:29 PM, Martin wrote:
ERROR: Build failed.
make: *** [source/open-iscsi-2.0-871/usr] Fehler 1
any hints for me?
Where are you running make from? You cannot run it from the usr dir. You
have to run it from the top open-iscsi dir. From there do
make user
If that does not
2010/3/18 Martin hein...@googlemail.com
hi there,
i'm tring to crosscompile for mips arch.
build fails with:
/home/heini66/freetz-trunk/source/open-iscsi-2.0-871/utils/
fwparam_ibft'
/home/heini66/freetz-trunk/toolchain/target/bin/mipsel-linux-uclibc-
gcc -Os -pipe -march=4kc -Wa,--trap
hi there,
i'm tring to crosscompile for mips arch.
build fails with:
/home/heini66/freetz-trunk/source/open-iscsi-2.0-871/utils/
fwparam_ibft'
/home/heini66/freetz-trunk/toolchain/target/bin/mipsel-linux-uclibc-
gcc -Os -pipe -march=4kc -Wa,--trap -D_LARGEFILE_SOURCE -
D_LARGEFILE64_SOURCE
Using a single path (without MPIO) as a baseline:
With bonding I saw, on average 99-100% of the speed (worst case 78%)
of a single path.
With MPIO (2 nics) I saw, on average 82% of the speed (worst case 66%)
of the single path.
With MPIO with one nic (ifconfig downed the second), I saw, on
On 12/30/2009 11:48 AM, Kyle Schmitt wrote:
On Wed, Dec 9, 2009 at 8:52 PM, Mike Christiemicha...@cs.wisc.edu wrote:
So far single connections work: If I setup the box to use one NIC, I
get one connection and can use it just fine.
Could you send the /var/log/messages for when you run the
. Measurably. Not significantly.
If you have just a single iscsi connection/login from the initiator to the
target, then you'll have only one tcp connection, and that means bonding
won't help you at all - you'll be only able to utilize one link of the
bond.
bonding needs multiple tcp/ip
On Thu, Dec 31, 2009 at 8:23 AM, Pasi Kärkkäinen pa...@iki.fi wrote:
If you have just a single iscsi connection/login from the initiator to the
target, then you'll have only one tcp connection, and that means bonding
won't help you at all - you'll be only able to utilize one link of the
bond
Note, the EMC specific bits of that multipath.conf were just copied
from boxes that use FC to the SAN, and use MPIO successfully.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-is...@googlegroups.com.
To
On Wed, Dec 9, 2009 at 8:52 PM, Mike Christie micha...@cs.wisc.edu wrote:
So far single connections work: If I setup the box to use one NIC, I
get one connection and can use it just fine.
Could you send the /var/log/messages for when you run the login command
so I can see the disk info?
Sorry
On Fri, Dec 11, 2009 at 3:29 PM, Mike Christie micha...@cs.wisc.edu wrote:
Lee Amy wrote:
Hi all,
I got some problems when I set up iface. The initiator node has two
NIC eth0 is eth1. I set up eth0 to connect the router by browsing Web.
And eth1 will link to a disk array. In the default mode
-iscsi@googlegroups.com
Subject: Re: Need help with multipath and iscsi in CentOS 5.4
Kyle Schmitt wrote:
I'm cross-posting here from linux-iscsi-users since I've seen no
linux-scsi-users would be for centos 4. Centos 5 uses a different
initiator, but you are the right place finally :)
traffic
On Wed, Dec 9, 2009 at 8:52 PM, Mike Christie micha...@cs.wisc.edu wrote:
Kyle Schmitt wrote:
What do you mean by works? Can you dd it, or fdisk it?
it works by most any measure sdc: I can dd it, fdisk it, mkfs.ext3 it,
run iozone, etc.
In contrast sdb sdd and sde cant be fdisked, dded, or
Hi all,
I got some problems when I set up iface. The initiator node has two
NIC eth0 is eth1. I set up eth0 to connect the router by browsing Web.
And eth1 will link to a disk array. In the default mode iscsi will log
in the target machine by using eth0 so I wanna change into eth1.
I followed
Lee Amy wrote:
Hi all,
I got some problems when I set up iface. The initiator node has two
NIC eth0 is eth1. I set up eth0 to connect the router by browsing Web.
And eth1 will link to a disk array. In the default mode iscsi will log
in the target machine by using eth0 so I wanna change into
Kyle Schmitt wrote:
I'm cross-posting here from linux-iscsi-users since I've seen no
linux-scsi-users would be for centos 4. Centos 5 uses a different
initiator, but you are the right place finally :)
traffic in the weeks since I posted this.
Hi, I needed a little help or advice with my
I'm cross-posting here from linux-iscsi-users since I've seen no
traffic in the weeks since I posted this.
Hi, I needed a little help or advice with my setup. I'm trying to
configure multipathed iscsi on a CentOS 5.4 (RHEL 5.4 clone) box.
Very short version: One server with two NICs for iSCSI
Ricky wrote:
sda: got wrong page
You mean this right? The linux scsi layer was trying to figure out the
cache type. It got an unexpected answer and so ...
sda: assuming drive cache: write through
it used the default of write through cache.
sd 6:0:0:0: Attached scsi disk sda
sd 6:0:0:0:
This information will also come out when I fdisk /dev/sda. And I can not
mkfs this disk.
I think the cache type should be write back.
But I do not how to handle this situation.
2009/11/26 Mike Christie micha...@cs.wisc.edu
Ricky wrote:
sda: got wrong page
You mean this right? The linux
On Mon, Nov 23, 2009 at 05:31:06PM -0600, Mike Christie wrote:
xi qihao wrote:
What distro are you using? If you look in /dev/disk/by-id there should
be names that are persistent across reboots.
It is CentOS (2.6.18-128.1.16.el5xen) x86_64
[r...@master ~]# ls -l /dev/disk/by-id/
total 0
On Thu, Nov 19, 2009 at 02:04:32PM -0600, Mike Christie wrote:
xi qihao wrote:
Hi all:
I a newbie of iscsi. Now I use two PC to test software iscsi.
My problem is how to fix connect of iscsi target?
The below are the detail:
SAN: iscsi target device ip: 192.168.3.2
master: iscsi
xi qihao wrote:
What distro are you using? If you look in /dev/disk/by-id there should
be names that are persistent across reboots.
It is CentOS (2.6.18-128.1.16.el5xen) x86_64
[r...@master ~]# ls -l /dev/disk/by-id/
total 0
lrwxrwxrwx 1 root root 9 Nov 20 11:00
1 - 100 of 160 matches
Mail list logo
