If lun is having LV(i.e.Virtual Block device) in it,then it should be
exposed as Blockio.
If it is exposing Regular file,then it should use Fileio.
Is it right?
Regular file is exposed as a disk.What is difference between 'Blockio
and Fileio in iSCSI.
Yes to both questions, Konrad.
On Jun 20, 12:28 pm, Konrad Rzeszutek [EMAIL PROTECTED] wrote:
On Fri, Jun 20, 2008 at 08:42:25AM -0700, Michael wrote:
I'm trying to implement the automatic login, by doing:
iscsiadm -m node -T targetname --op update -n node.startup -v
automatic
When I
On Mon, Jun 23, 2008 at 05:22:00AM -0700, HIMANSHU wrote:
If lun is having LV(i.e.Virtual Block device) in it,then it should be
exposed as Blockio.
If it is exposing Regular file,then it should use Fileio.
Is it right?
Regular file is exposed as a disk.What is difference between 'Blockio
On Mon, 2008-06-23 at 05:42 -0700, HIMANSHU wrote:
What is use of exporting Regular File as a disk and LV's as a Disk?
Which one is better?
What is better ? Fileio or Blockio in terms of Performance/Other
issues?
u asked in wrong list. u should go iet list instead of open-iscsi list.
Michael wrote:
I'm trying to implement the automatic login, by doing:
iscsiadm -m node -T targetname --op update -n node.startup -v
automatic
When I run this after inserting the proper target name, it seems to
work fine. But when I do: service open-iscsi restart, I get:
Setting up
Ok, I ran the command I previously noted to set automatic startup,
then ran the command you suggested, with this output:
[EMAIL PROTECTED] ~]# iscsiadm -m node -L automatic -d 8
iscsiadm: Max file limits 1024 1024
iscsiadm: searching target name
iscsiadm: found 10.3.2.7,3260,-1
iscsiadm:
Also, it works perfectly fine if I go into /etc/iscsi/nodes/target
name/10.3.2.1,3260 and edit the node.startup line myself. Am I just
typing the command wrong without realizing it? Again, I'm doing:
iscsiadm -m node -T targetname --op update -n node.startup -v
automatic
On Jun 23, 3:04 pm,
Alex M. wrote:
On Jun 16, 4:29 pm, Mike Christie [EMAIL PROTECTED] wrote:
Do:
iscsiadm -m session -r $SID --rescan
Doing a rescan doesn't appear to pick up the new size of the devices.
When you run that command what gets outputted to /var/log/messages. For
existing devices you should
Michael Kindermann wrote:
Hello,
thanks for quick reply. During weekend I did backups on the iscsi-device
with not one single error on kernel 2.6.22.
Am Freitag, den 13.06.2008, 19:11 +0200 schrieb Mike Christie:
Michael Kindermann wrote:
Hello,
We receive errors below on a standard
Michael wrote:
Hi all,
I've been using open-iscsi to set up an IBM Ultrium LTO-4 tape drive.
I can connect and transfer files and everything, but the maximum read
or write speed I can get is like 16MB/s by tweaking the block size. I
am on a gigabit network, which the tape drive supports.
On Jun 23, 1:27 pm, Mike Christie [EMAIL PROTECTED] wrote:
--snip--
However, there is issue outstanding I think. I think you then need a new
a newer kernel (like 2.6.26 or something) so that the block layer can
see the changes and pick up the scsi layer changes. Also see my comment
on FSs
An Oneironaut wrote:
I posted a little while back about this, but I still seem to be
having trouble with this issue. Originally I tried to setup my iSCSI
connection so that it had a 24 day timeout period and the no-op timers
would be disabled. However this timeout led to a variety of
galitz wrote:
I am evaluating iSCSI in our production environment and have a
question.
When I induce a failure by powering down the iSCSI target while there
is active traffic and then restore the iSCSI target 5+ minutes later,
the filesystem remains in read-only mode. Fair enough, I
Thanks for the info.
One more question, I just looked through the iscsi.conf file and the README
but I do not see a setting for explicitly setting dm-multipath. How do I
enable it?
-geoff
Geoff Galitz
Blankenheim NRW, Deutschland
http://www.galitz.org
-Original Message-
From:
14 matches
Mail list logo
