AIX 6.1's iSCSI-initiator works with IETd target [SOLVED]
At the risk of looking spammy, here my final remark on this subject: I've successfully ran 'mkvg' on an iSCSI disk, exported from an RHEL5
machine running IET (http://iscsitarget.sourceforge.net/).
Code:
# chdev -l hdisk2 -a pv=clear
hdisk2 changed
# lspv
hdisk0 00c9a1fbe1fd35d0 rootvg
active
hdisk1 00c9a1fbe5bf8aaf rootvg
active
hdisk2 none None
hdisk3 00c9a1fb6f64e590 None
hdisk4 00c9a1fb6f652404 None
# chdev -l hdisk2 -a pv=yes
hdisk2 changed
# lspv
hdisk0 00c9a1fbe1fd35d0 rootvg
active
hdisk1 00c9a1fbe5bf8aaf rootvg
active
hdisk2 00c9a1fbad59e652 None
hdisk3 00c9a1fb6f64e590 None
hdisk4 00c9a1fb6f652404 None
# mkvg -y foovg hdisk2
foovg
# lspv
hdisk0 00c9a1fbe1fd35d0 rootvg
active
hdisk1 00c9a1fbe5bf8aaf rootvg
active
hdisk2 00c9a1fbad59e652 foovg
active
hdisk3 00c9a1fb6f64e590 None
hdisk4 00c9a1fb6f652404 None
Thanks to everyone that helped me fix this really _really_ annoying
issue!
--edit--
Useful to add that (or at least so I think) is that the odious 'devices.iscsi.array' warning by cfgmgr no longer appears since using IET.
hey programmers!
1-why won't gcc accept as an argument? i tried the recommendations on the man page of getch(),..etc. nothing worked.
2-why it won't see <iostream> && <fstream> even if i implemented the function as follow
std::cout<<"..etc"<<endl;
3-after i type this code in it gives... (6 Replies)
I'm trying to figure out why this if statement won't work:
if || $zipcount != 6 ]]
then
echo ${myline}
echo "ZIPCODE WARNING! ${zipcode} ${zipcount}"
fi
if ]]
then
echo ${myline}
echo "STATE WARNING!... (3 Replies)
Hi All,
can anybody tell me what's wrong with this code?
# SEARCH replaced by REPLACE
#!/bin/bash
SEARCH="95$$ 0 t"
REPLACE="95$$ 1 t"
for I in `ls *000.inp | cut -c-12`;
do
echo $I
sed 's/$SEARCH/$REPLACE/' ${I}-000.inp > ${I}-100.inp
done
It don't replace the string... (5 Replies)
I typed:
echo "echo hi > at_log.txt" | at now +1minute
to test the at command on my terminal. I got the message:
job 8 at Thu Feb 25 18:42:00 2010
I waited for a minute but nothing happened. I tried listing at_log.txt, but it said there was no such file. Am I doing something... (2 Replies)
I just installed a fork of opensolaris, and I really like it.
I would hate going back to Ubuntu, But one issue, I cannot get my Dell Wireless 1450 Wireless USB Adapter working.
On Ubuntu 10.4 I just installed nonfree firmware, but I guess it doesn't work that way on Solaris, any help would be... (5 Replies)
Hi,
I have a very frustrating issue! I hope you guys can assist
When a disk is presented out the iSCSI target display a lower disk capacity
SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31
ISCSI Patch 119090-31, 141878-11
Unix Commands To discover Target
bash-3.00# i... (0 Replies)
Hi! I'm sure that somebody here installed freeBSD from a download of a virtual disc (.iso). But I made 5 downloads of 5 differents freeBSD installation (and no one has worked).Can somebody tell me where to download and how (if needed) to prepare the cd? (8 Replies)
Hello,
Images won't work on UNIX when I try posting them on my website I'm working on. It doesn't show the image, and it's simply erroring.
Help! Thanks! (5 Replies)
Previous forum threads have noted that AIX cannot use iSCSI disks because it fails when trying to add them to a volume group using mkvg. The failure is caused by AIX's use of the SCSI "WRITE AND VERIFY"(0x2e) command which some iSCSI targets do not support.
We experienced the same problem using... (1 Reply)
Hi all,
Is there anyway i can control the naming of the disk device ?
I have added an iscsi disk on server1 using iscsiadm , devfsadm and it is now showing as
/dev/dsk/c2t0d0 in node1
However, i am worried that the same disk will appear as
/dev/dsk/cXtXd0 in node2
This iscsi disk(lun)... (0 Replies)
Discussion started by: javanoob
0 Replies
LEARN ABOUT FREEBSD
iscsi
ISCSI(4) BSD Kernel Interfaces Manual ISCSI(4)NAME
iscsi -- iSCSI initiator
SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file:
device iscsi
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
iscsi_load="YES"
DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar-
get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are
configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol.
SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables:
kern.iscsi.ping_timeout
The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time
the session gets forcibly restarted.
kern.iscsi.iscsid_timeout
The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry.
kern.iscsi.login_timeout
The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry.
kern.iscsi.maxtags
The maximum number of outstanding IO requests.
kern.iscsi.fail_on_disconnection
Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes
the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left
intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished.
SEE ALSO iscsi.conf(5), iscsictl(8), iscsid(8)HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0.
AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.
BSD September 11, 2014 BSD