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
sg_inq -E /dev/sdc
# time sg_inq -E /dev/sdc
VPD INQUIRY: extended INQUIRY data page
SPT=0 GRD_CHK=0 APP_CHK=0 REF_CHK=0
UASK_SUP=0 GROUP_SUP=0 PRIOR_SUP=0 HEADSUP=0 ORDSUP=0 SIMPSUP=0
WU_SUP=0 CRD_SUP=0 NV_SUP=1 V_SUP=1
P_I_I_SUP=0 LUICLR=0 CBCS=0 R_SUP=0
Multi I_T nexus
On Aug 28, 2012, at 5:39 PM, Jeffrey Caughel jcaug...@gmail.com wrote:
In order to further dig into performance issues we're seeing, I am trying to
correlate individual iSCSI connections with specific TCP connections. I
don't want to negatively impact performance more than it already is so
On Aug 16, 2012, at 3:02 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
Hi!
I have a problem with iscsiadm version 2.0-872.suse (SLES11 SP2): On boot
my nodes did not log in automatically.
The SUSE script does $ISCSIADM -m node --loginall=automatic 2 /dev/null.
Now my
On Aug 16, 2012, at 10:11 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
Michael Christie micha...@cs.wisc.edu schrieb am 16.08.2012 um 16:16 in
Nachricht 74fc4f8a-86c0-4c90-b29f-d5c665631...@cs.wisc.edu:
On Aug 16, 2012, at 3:02 AM, Ulrich Windl
ulrich.wi...@rz.uni
On Aug 15, 2012, at 1:12 PM, parveen kumar coolbudy1...@gmail.com wrote:
Dear Mike Christie,
:)
Oki tell me that what file to edit for Retry-Relogin from initiator to target
when connection get lost in CentOS5.3.
Like: defaults is 4 tries and 120 sec how to increase this and what file to
Replacing linux-scsi list with linux-kernel.
On Aug 12, 2012, at 9:15 AM, Masatake YAMATO yam...@redhat.com wrote:
In iscsi_free_task, NULL is assigned to task-sc twice: before and
after kfifo_in invocatoin. Allocating and freeing iscsi_task are guarded
with session-lock, so multiple NULL
On Aug 11, 2012, at 9:37 PM, Bob Zscharnagk bob.zscharn...@gmail.com wrote:
I'm new to open-iscsi.
I'm receiveing lots of detected conn error (1001) errors and slow iSCSI
usage.
Are you sure it is conn error 1001 and not 1011?
1001 is really rare. It indicates there was a data
On Aug 9, 2012, at 1:49 AM, squadra j...@internetx.de wrote:
my max_sectors_kb setting is 512 at the moment. you mean i should set it to
192?
64.
I would try Anil's suggestion first.
--
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To
On Aug 9, 2012, at 2:49 AM, squadra j...@internetx.de wrote:
i tried this on a empty system, it leads to:
blk_rq_check_limits: over max size limit.
device-mapper: multipath: Failing path 8:16.
blk_rq_check_limits: over max size limit.
device-mapper: multipath: Failing path 8:32.
In the
On Aug 8, 2012, at 4:42 AM, Fubo Chen fubo.c...@gmail.com wrote:
Anyone seen this before ? Also occurs with 3.4.1.
==
[ INFO: HARDIRQ-safe - HARDIRQ-unsafe lock order detected ]
3.6.0-rc1-debug+ #1 Not tainted
On Aug 8, 2012, at 10:26 AM, squadra j...@internetx.de wrote:
Hi,
we are experiencing some really strange issues in our Setup, Based up on
several Linux Hostsystems and Equallogic Storagesystems. Our normal workload
is 95% write and 5% read (both together about 10mb/sec avg), under this
On Tue, 6 May 2008, Padmanabhan wrote:
Hello Mike,
Let me explain the sequence of events
-- The system reboots
-- Open iscsi is enabled at start up
Issue 1 == From the database, the initiator logins twice to the same
target via TWO TCP connections which are established on IPv4 and IPv6
101 - 113 of 113 matches
Mail list logo
