On 3/24/24 16:54, Christoph Hellwig wrote:
Use the SCSI host's dma_alignment field and set it in ->init and remove
the now unused config_scsi_dev method.
Reviewed-by: Bart Van Assche
--
You received this message because you are subscribed to the Google Groups
"open-iscs
On 3/24/24 16:54, Christoph Hellwig wrote:
Get drivers out of the business of having to call the block layer
dma alignment limits helpers themselves.
Reviewed-by: Bart Van Assche
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To u
On 3/24/24 16:54, Christoph Hellwig wrote:
Switch scsi_add_lun to use the atomic queue limits API to update the
max_hw_sectors for devices with quirks.
Reviewed-by: Bart Van Assche
--
You received this message because you are subscribed to the Google Groups
"open-iscsi&q
On 3/24/24 16:54, Christoph Hellwig wrote:
Signed-off-by: Christoph Hellwig
Reviewed-by: Bart Van Assche
--
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 emai
On 3/24/24 16:54, Christoph Hellwig wrote:
This is a version of ->slave_configure that also takes a queue_limits
structure that the caller applies, and thus allows drivers to reconfigure
the queue using the atomic queue limits API.
In the long run it should also replace ->slave_configure
On 3/24/24 16:54, Christoph Hellwig wrote:
This allows bsg_setup_queue to pass them to blk_mq_alloc_queue and thus
set up the limits at queue allocation time.
Reviewed-by: Bart Van Assche
--
You received this message because you are subscribed to the Google Groups
"open-iscsi&q
On 3/24/24 16:54, Christoph Hellwig wrote:
Turn __scsi_init_queue into scsi_init_limits which initializes
queue_limits structure that can be passed to blk_mq_alloc_queue.
Reviewed-by: Bart Van Assche
--
You received this message because you are subscribed to the Google Groups
"open-
On 9/22/23 02:36, Wenchao Hao wrote:
SDEV_CANCEL is set when removing device and scsi_device_online() should
return false if sdev_state is SDEV_CANCEL.
IO hang would be caused if return true when state is SDEV_CANCEL with
following order:
T1:
On 9/22/23 02:36, Wenchao Hao wrote:
Fix the issue of skipping scsi_try_bus_device_reset() for devices
which is in progress of removing in following order:
T1: T2:scsi_error_handle
__scsi_remove_device
scsi_device_set_state(sdev, SDEV_DEL)
On 9/22/23 02:38, Wenchao Hao wrote:
Add comment to tell callback function target_destroy of
scsi_host_template is called in atomic context.
Signed-off-by: Wenchao Hao
---
include/scsi/scsi_host.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/scsi/scsi_host.h
On 2020-07-30 21:58, sonu kumar wrote:
> I looked into the TODO list of open-iscsi. It is quite old and written
> on July 7th,2011. Do we have any updated version of it?
>
> I am looking for some low hanging tasks to getting started with
> open-iscsi and iscsi. It would be really helpful if
On 3/6/20 11:59 AM, Gabriel Krisman Bertazi wrote:
+static const char *const connection_state_names[] = {
+ [ISCSI_CONN_UP] = "up",
+ [ISCSI_CONN_DOWN] = "down",
+ [ISCSI_CONN_FAILED] = "failed"
+};
+
+static ssize_t show_conn_state(struct device *dev,
+
On 3/5/20 11:20 AM, Gabriel Krisman Bertazi wrote:
Bart Van Assche writes:
On 3/5/20 7:35 AM, Gabriel Krisman Bertazi wrote:
+static const struct {
+ int value;
+ char *name;
+} connection_state_names[] = {
+ {ISCSI_CONN_UP, "up"},
+ {ISCSI_CONN_D
On 3/5/20 7:35 AM, Gabriel Krisman Bertazi wrote:
+static const struct {
+ int value;
+ char *name;
+} connection_state_names[] = {
+ {ISCSI_CONN_UP, "up"},
+ {ISCSI_CONN_DOWN, "down"},
+ {ISCSI_CONN_FAILED, "failed"}
+};
+
+static const char
On 3/4/20 2:57 PM, Gabriel Krisman Bertazi wrote:
+static const struct {
+ int state;
+ char *name;
+} connection_state_name[] = {
+ {ISCSI_CONN_UP, "up"},
+ {ISCSI_CONN_DOWN, "down"},
+ {ISCSI_CONN_FAILED, "failed"}
+};
+
+static ssize_t
+show_conn_state(struct
On Wed, 2019-05-01 at 12:14 -0400, Christoph Hellwig wrote:
> Use the the GPLv2 SPDX tag instead of verbose boilerplate text.
Acked-by: Bart Van Assche
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this g
On 4/4/19 4:04 PM, Ming Lin wrote:
async_synchronize_full_domain(_sd_pm_domain);
- async_synchronize_full_domain(_sd_probe_domain);
+ async_synchronize_full_domain(>sd_probe_domain);
device_del(>dev);
del_gendisk(sdkp->disk);
SCSI patches should be prepared
This patch avoids that building with W=1 causes the compiler to
complain about fall-through.
Signed-off-by: Bart Van Assche <bart.vanass...@wdc.com>
Cc: Lee Duncan <ldun...@suse.com>
Cc: Chris Leech <cle...@redhat.com>
---
drivers/scsi/libiscsi.c | 1 +
1 file changed, 1 insert
Hello Lee and Chris,
The two patches in this series are what I came up with after a review of the
gcc and sparse warnings reported against kernel v4.16-rc1. Please consider
these patches for kernel v4.17.
Thanks,
Bart.
Bart Van Assche (2):
libiscsi: Annotate locking assumptions
libiscsi
This patch avoids that sparse reports the following:
drivers/scsi/libiscsi.c:1844:23: warning: context imbalance in
'iscsi_exec_task_mgmt_fn' - unexpected unlock
Signed-off-by: Bart Van Assche <bart.vanass...@wdc.com>
Cc: Lee Duncan <ldun...@suse.com>
Cc: Chris Leech <cl
On Thu, 2017-12-07 at 19:59 -0200, Rafael David Tinoco wrote:
> This happens because iscsi_eh_cmd_timed_out(), the transport layer
> timeout helper, would tell the queue timeout function (scsi_times_out)
> to reset the request timer over and over, until the session state is
> back to logged in
On 02/15/2017 06:48 AM, Peter Wang wrote:
> I am investing new ways to discover LUN exposed by iSCSI targets.
>
> Currently, most of tools/libs are using user land shell commands
> "iscsiadm" to login targets or rescan new LUNs.
> sometimes, as I observed, the rescan is time-consuming. in
>
On 02/13/17 07:07, Gorka Eguileor wrote:
While working on Cinder, the block storage service in OpenStack, I
noticed that the autoscan mechanism in iscsid is creating issues for us
and I would like to popose a mechanism to make it optional.
The problem for OpenStack deployment comes from the
On 03/29/2016 11:26 AM, Mike Christie wrote:
On 03/28/2016 03:39 PM, Bart Van Assche wrote:
These five patches are what I came up with after analyzing the output of
"make M=drivers/scsi W=1 C=2" for the iSCSI kernel code. Please consider
these patches for inclusion in kernel v4.7.
The output of "git grep -nHw iscsi_is_flashnode_conn_dev" shows
that this function is only called from inside source file
drivers/scsi/scsi_transport_iscsi.c. Hence unexport this function.
Signed-off-by: Bart Van Assche <bart.vanass...@sandisk.com>
---
drivers/scsi/scsi_trans
Avoid that building with W=1 causes gcc to report warnings about
symbols that have not been declared.
Signed-off-by: Bart Van Assche <bart.vanass...@sandisk.com>
---
drivers/scsi/scsi_transport_iscsi.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/driver
Running "git grep -nHw iscsi_eh_target_reset" shows that this
function is only called from inside the drivers/scsi/libiscsi.c
source file. Hence unexport this function.
Signed-off-by: Bart Van Assche <bart.vanass...@sandisk.com>
---
drivers/scsi/libiscsi.c | 3 +--
1 file chan
Avoid that building with W=1 causes gcc to report warnings about
set-but-not-used variables.
Signed-off-by: Bart Van Assche <bart.vanass...@sandisk.com>
---
drivers/scsi/scsi_transport_iscsi.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/scsi/scsi_transport_iscsi.c
b/d
Avoid that building with W=1 causes gcc to report warnings about
set-but-not-used variables.
Signed-off-by: Bart Van Assche <bart.vanass...@sandisk.com>
---
drivers/scsi/libiscsi.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/libiscsi.c b/driver
On 02/29/16 17:08, Hannes Reinecke wrote:
On 02/29/2016 10:58 PM, Bart Van Assche wrote:
On 02/28/16 23:59, Hannes Reinecke wrote:
libudev has a _massive_ static memory footprint
(Kay doesn't believe in memory allocation).
So when using libudev you might end up having a really large memory
On 02/28/16 23:59, Hannes Reinecke wrote:
libudev has a _massive_ static memory footprint
(Kay doesn't believe in memory allocation).
So when using libudev you might end up having a really large memory
footprint due to all the on-stack allocations in there.
Be especially careful when attempting
On 06/25/2015 11:31 PM, LSZhu wrote:
I have been working for iSCSI in SUSE for half a year, I have some basic
knowledge of iSCSI. I did some debug and performance analyze work
before.I am quite interested in iSCSI-mq, I am not a expert here, but
may I do some contributions for iSCSI-mq? If you
On 02/25/15 18:36, Sagi Grimberg wrote:
- About shared tags. So for scsi commands and TMFs we don't have a
problem since we are guaranteed ITTs are unique. I wander how will we
allocate a unique ITT for iscsi specific tasks (LOGIN, TEXT, LOGOUT,
NOOP_OUT). My implementation did it
On 01/09/15 12:39, Sagi Grimberg wrote:
On 1/8/2015 4:11 PM, Bart Van Assche wrote:
On 01/08/15 14:45, Sagi Grimberg wrote:
Actually I started with that approach, but the independent connections
under a single session (I-T-Nexus) violates the command ordering
requirement. Plus
On 01/08/15 14:45, Sagi Grimberg wrote:
Actually I started with that approach, but the independent connections
under a single session (I-T-Nexus) violates the command ordering
requirement. Plus, such a solution is specific to iSER...
Hello Sagi,
Which command ordering requirement are you
On 10/06/14 18:36, Andy Grover wrote:
struct mac_address {
- u8_t addr[6];
+ union {
+ u8_t addr[6];
+ struct {
+ u16_t first_2_bytes;
+ u32_t last_4_bytes;
+ };
+ };
};
This patch
On 01/04/10 03:46, lancests wrote:
We are currently developing iSCT, a tool which does iSCSI conformance
test for the target. It's written in Python and can be driven by user-
defined test scripts. Using iSCT, it is easy to identify target
protocol conformance problems in user space during
On 11/18/13 22:59, Mike Christie wrote:
On 11/14/2013 05:53 PM, micha...@cs.wisc.edu wrote:
From: Yufei Ren yufei@stonybrook.edu
Got can not connect to iSCSI daemon (111)! error during
starting iscsi service by:
$ iscsiadm -m node --loginall=all
Traced down and found that the sun_path
On Sat, Sep 24, 2011 at 9:40 PM, Vivek S vivek...@gmail.com wrote:
I am on Dell laptop running Ubuntu 11.04, kernel 2.6.38.11.
I'm curious to know who generated kernel 2.6.38.11 ? As far as I know
the latest official kernel in the 2.6.38 series is 2.6.38.8
(https://lkml.org/lkml/2011/6/2/417). A
On Wed, Jul 20, 2011 at 3:06 PM, Jim Ramsay jim_ram...@dell.com wrote:
This allows ^C to exit iscsid but only when it is running in foreground
mode, which is useful for testing.
Signed-off-by: Jim Ramsay jim_ram...@dell.com
---
usr/iscsid.c | 5 +
1 files changed, 5 insertions(+), 0
On Wed, Feb 3, 2010 at 4:30 PM, Or Gerlitz ogerl...@voltaire.com wrote:
The following patch set removes some in efficiencies in the iser data path
through simplification and reducing the amount of code, using less atomic
operations, avoiding TX interrupts, moving to iscsi passthrough mode,
On Wed, Feb 3, 2010 at 4:30 PM, Or Gerlitz ogerl...@voltaire.com wrote:
The following patch set removes some in efficiencies in the iser data path
through simplification and reducing the amount of code, using less atomic
operations, avoiding TX interrupts, moving to iscsi passthrough mode,
On Mon, Feb 1, 2010 at 10:33 AM, Pasi Kärkkäinen pa...@iki.fi wrote:
On Thu, Jan 28, 2010 at 01:44:00PM -0500, Joe Landman wrote:
Pasi Kärkkäinen wrote:
I suspect that they really aren't seeing ~1us latencies, but that with
some neat tricks, it appears to be this.
Physically, it isn't
On Thu, Jan 28, 2010 at 1:36 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
Please check these news items:
http://blog.fosketts.net/2010/01/14/microsoft-intel-push-million-iscsi-iops/
http://communities.intel.com/community/openportit/server/blog/2010/01/19/100-iops-with-iscsi--thats-not-a-typo
On Thu, Jan 28, 2010 at 4:01 PM, Joe Landman
land...@scalableinformatics.com wrote:
Pasi Kärkkäinen wrote:
Please check these news items:
http://blog.fosketts.net/2010/01/14/microsoft-intel-push-million-iscsi-iops/
On Wed, Nov 25, 2009 at 5:57 PM, Shachar f shacharf...@gmail.com wrote:
I'm running open-iscsi with scst on Broadcom 10Gig network and facing write
latency issues.
When using netperf over an idle network the latency for a single block round
trip transfer is 30 usec and with open-iscsi it is
2009/7/24 Mike Christie micha...@cs.wisc.edu
On 07/22/2009 02:56 PM, Artur Piechocki wrote:
Hello
Some time ago I wrote small frontend for iSCSI-Target and Open-iSCSI for
KDE3x and QT3.
Is the goal to get this merged in KDE? Does KDE have any programs for
managing this stuff? What
On Thu, Jun 18, 2009 at 12:12 PM, Hannes Reineckeh...@suse.de wrote:
Joachim Worringen wrote:
On Jun 18, 11:19 am, Boaz Harrosh bharr...@panasas.com wrote:
On 06/18/2009 10:56 AM, Joachim Worringen wrote:
Is there a specific reason for this? iSCSI would surely benefit from
using
On Thu, Jun 18, 2009 at 1:14 PM, FUJITA
Tomonorifujita.tomon...@lab.ntt.co.jp wrote:
On Thu, 18 Jun 2009 03:53:47 -0700 (PDT)
Joachim Worringen worrin...@googlemail.com wrote:
On Jun 18, 12:37 pm, FUJITA Tomonori fujita.tomon...@lab.ntt.co.jp
wrote:
Well, anyway seems that 10GbE is slowly
On Thu, Jun 18, 2009 at 2:14 PM, FUJITA
Tomonorifujita.tomon...@lab.ntt.co.jp wrote:
On Thu, 18 Jun 2009 13:33:42 +0200
Bart Van Assche bart.vanass...@gmail.com wrote:
Numbers please. From the last numbers I have seen the latency
difference between 10 GbE and fast non-Ethernet networks
On Sun, Jun 14, 2009 at 11:23 AM, Boaz Harroshbharr...@panasas.com wrote:
On 06/11/2009 08:41 PM, Mike Christie wrote:
It seems like we have a lot of members on the list that are not kernel
developers, but we now have 5 iscsi drivers (qla4xxx, bnx2i, cxgb3i,
iscsi_tcp and ib_iser) with
On Fri, May 29, 2009 at 5:21 PM, Wido wid...@gmail.com wrote:
Last night i had the idea of building a multipath iSCSI setup with DRBD
in Primary/Primary.
[ ... ]
Is my setup a possibility or should i stay with the old regular setup of
a Primary/Standy with heartbeat?
I strongly recommend
On Wed, Apr 15, 2009 at 8:24 PM, benoit plessis
plessis.ben...@gmail.com wrote:
I wanted to share some infos about a discovery we made using mysql over
iSCSI.
A few questions:
- Was MySQL configured for direct I/O or for buffered I/O ?
- Which mount options were used with the ext2 / ext3
On Wed, Apr 15, 2009 at 9:19 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
noop is usually good for the initiator. cfq has a feature (or a bug?) that
prevents achieving queue depths deeper than 1, and thus limits your
bandwidth a lot when there are (or should be) many ios on the fly at the
same
On Wed, Apr 15, 2009 at 9:19 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
noop is usually good for the initiator. cfq has a feature (or a bug?) that
prevents achieving queue depths deeper than 1, and thus limits your
bandwidth a lot when there are (or should be) many ios on the fly at the
same
On Thu, Apr 16, 2009 at 1:10 PM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
Considering that most remote iSCSI targets have intelligece of their own,
the
use of a no-op i/O scheduler seems justified. I think multiple I/O schedulers
on
both ends don't necessarily make things
On Thu, Apr 16, 2009 at 2:07 PM, Pasi Kärkkäinen pa...@iki.fi wrote:
Iirc it has been with RHEL5/CentOS5 2.6.18 based kernels..
Mike Christie has been writing about this aswell.. dunno about what kernels
he has seen it with.
Then again CFQ was designed for single disk workstations..
I have
On Mon, Apr 13, 2009 at 10:33 PM, Mike Christie micha...@cs.wisc.edu wrote:
I think linux is just not so good with smaller IO sizes like 4K. I do
not see good performance with Fibre Channel or iscsi.
Most people run a filesystem on top of a block device imported via
open-iscsi. It is well
On Wed, Apr 15, 2009 at 8:24 PM, benoit plessis
plessis.ben...@gmail.com wrote:
I wanted to share some infos about a discovery we made using mysql over
iSCSI.
We have a bunch of replicated mysql server, initially all using ext3, due to
perfs problems we
tried comparing persf in ext3 vs
On Mon, Apr 13, 2009 at 10:33 PM, Mike Christie micha...@cs.wisc.edu wrote:
I think linux is just not so good with smaller IO sizes like 4K. I do
not see good performance with Fibre Channel or iscsi.
Can you elaborate on the above ? I have already measured a throughput
of more than 60 MB/s
On Tue, Apr 14, 2009 at 7:09 PM, Dmitry Yusupov dmitry_...@yahoo.com wrote:
NexentaStor also is very good candidate for CIFS workgroups/AD
environments with the whole SMB stack implemented in the kernel, which
boosts performance over the top. And as far as iSCSI target - I would
recommend to
Hello,
While running iSCSI performance tests I noticed that the performance
for certain block sizes deviated significantly (more than ten times)
from the performance for other block sizes, both larger and smaller.
This surprised me.
The test I ran was as follows:
* A file of 1 GB residing on a
On Thu, Jan 29, 2009 at 12:34 AM, Mike Christie micha...@cs.wisc.edu wrote:
strncat(dev_dir, /, FILENAMESZ);
strncat(dev_dir, dent-d_name, FILENAMESZ);
I assume the third argument should have been FILENAMESZ - strlen(dev_dir) ?
Bart.
On Tue, Jan 20, 2009 at 7:20 PM, Konrad Rzeszutek
kon...@virtualiron.com wrote:
I would recommend that you provide as the first variable in all of the
structs
an unsigned int called 'version'. This way if the structs are extended they
would be backwards compatible and there is an easy
On Mon, Jan 19, 2009 at 2:07 PM, Hans de Goede hdego...@redhat.com wrote:
Therefore we would like to export (some) of the functionality of iscsiadm as a
C-library.
Great !
I've got documentation of the proposed API here:
http://people.atrpms.net/~hdegoede/html/libiscsi_8h.html
Not so
On Mon, Jan 19, 2009 at 4:35 PM, Hans de Goede hdego...@redhat.com wrote:
- libiscsi_discover_sendtargets - maybe (very maybe) the int port could be
dropped and
const char *address could be of the form
address_or_host[:port].
On Mon, Jan 12, 2009 at 11:48 AM, avis...@gmail.com wrote:
Here are some statistics from wireshark:
Bad checksum(TCP): 35,963
Usually this means that Wireshark was unable to capture all packets,
not that there was a problem with the packets themselves.
Bart.
On Tue, Jan 13, 2009 at 8:31 PM, Norm normel...@gmail.com wrote:
I've run iozone over a new iscsi mount that we're configuring. The
client is RedHat 5, the server is Solaris on a Sun X4500 (thumper)
with the ZFS filesystem. On the client side, things are formatted with
the ext3 filesystem
On Tue, Jan 13, 2009 at 8:50 PM, Norm normel...@gmail.com wrote:
How much RAM is present in the ZFS server ?
The ZFS server has 16GB. The client has 2GB (I'm not sure how iSCSI
caching works, if any).
Apparently iozone has been run with the following command line options:
iozone -Raz -b
On Thu, Jan 8, 2009 at 12:44 PM, Tomasz Chmielewski man...@wpkg.org wrote:
Anyone using iSCSI over DRBD? And a slow internet link perhaps?
How reliable is the link you are using -- which percentage of packets
is lost ? You can test this e.g. with the ping command. The following
command will
On Fri, Jan 9, 2009 at 3:22 PM, Tomasz Chmielewski man...@wpkg.org wrote:
Bart Van Assche schrieb:
# ping -q -i 0.01 -c1000 -s160 ${remote_ip}
I get about 1% losses.
IMHO running iSCSI over a slow link should work, but a packet loss of
1% is troublesome. On a local network the packet loss
On Tue, Dec 23, 2008 at 9:13 AM, Andrew McGill list2...@lunch.za.net wrote:
From another list, the mail below is a proposal to change the default
partition table for disks from 512 bytes to 4096 bytes. I think that once
implemented (in a few years / days time), it will make some of the
On Tue, Dec 23, 2008 at 3:00 PM, r...@megabit.net wrote:
Hmmm maybe you misunderstood me - a performance improvement would be nice but
that was not the point of my mail: I'm just wondering why there seems to be
such a big overhead on the network while doing synchronus reads and writes to
On Mon, Dec 22, 2008 at 1:18 PM, Ulrich Windl
ulrich.wi...@rz.uni-regensburg.de wrote:
I think since ZBR (Zone Bit Recording) the number of sectors per cylinder is
variable. thus it makes no sense for any higher-level disk software to try to
deal
with heads or cylinders. Since ATA (about
On Mon, Dec 22, 2008 at 2:17 PM, Eric ericvanblokl...@gmail.com wrote:
Thanks for definitive answer and the link to a great thread. I need
one more:
I have to set the heads and cylinders on the disk partitions of the
virtualized servers. Now I assume I also have to set heads and
cylinders
On Tue, Nov 25, 2008 at 3:07 PM, Santi Saez [EMAIL PROTECTED] wrote:
What's the correct way to change configuration parameters for an iSCSI
device? For example I/O scheduler, max_sectors_kb, etc...
Please have a look at the hierarchy created by udevd in /dev. You can
find there soft links
On Fri, Nov 21, 2008 at 9:16 PM, Heady [EMAIL PROTECTED] wrote:
* The target is IET running on a Xen dom0 running Gentoo Linux with [ ... ]
Maybe not the advice you are looking for, but did you already have a
look at the SCST iSCSI target implementation ? It's faster than IET
and better
On Sat, Nov 22, 2008 at 10:58 AM, Tracy Reed [EMAIL PROTECTED] wrote:
On Sat, Nov 22, 2008 at 09:44:09AM +0100, Bart Van Assche spake thusly:
Maybe not the advice you are looking for, but did you already have a
look at the SCST iSCSI target implementation ? It's faster than IET
and better
On Wed, Nov 19, 2008 at 11:03 AM, Ulrich Windl
[EMAIL PROTECTED] wrote:
maybe some of you like to know what I think to have found out:
The HP EVA iSCSI connectivity MPX 100 box seems to be an OEM version of the
Qlogic iSR6140 Universal SAN Connectivity (with different firmware however).
Does
On Thu, Nov 20, 2008 at 8:33 AM, Ulrich Windl
[EMAIL PROTECTED] wrote:
I assume there are quite a few iSCSI boxes without Ethernet interfaces ;-)
iSCSI does not only run over Ethernet but also over e.g. InfiniBand.
The box has two Gb Ethernet interfaces that, AFAIK, have hardware
On Fri, May 23, 2008 at 8:09 PM, Mike Christie [EMAIL PROTECTED] wrote:
I have seen this a couple times in past versions too. If you run mkfs by
hand is it fine?
I get the same error when I run mkfs.ext3 -F directly. Is this an
initiator or a target issue ?
Bart.
Hello,
Due to resetting an iSCSI target (SCST) while an iSCSI session was
active, the iSCSI initiator seems to be locked up. E.g. when I try to
run the command iscsiadm -m session or iscsiadm ... --logout,
these command hangs forever. This is probably not the intended
behavior ?
# cat
Hello,
Does anyone on this list have experience with iSCSI target compliance
testing ? I found some old references to a compliance test by
University of New Hampshire Interoperability Labs (UNH-IOL) but have
been unable so far to find the source code of these tests.
See also:
* November 4,
Hello,
Has anyone here experience with letting the open-iscsi initiator
connect to an iSCSI target system on which many (hundreds) of target
have been configured ? From a certain number of targets on the
open-iscsi initiator starts complaining that the buffer size is too
small. Can I increase
84 matches
Mail list logo
