10-16-2009
before using chvg -g <vg>, you could verify if the LUN has been extended with bootinfo -s <hdisk##>
9 More Discussions You Might Find Interesting
1. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
2. Solaris
Hi,
I need to set up iscsi LUN on Solaris 9. I've done it on Solaris 10 with iscsiadm. How do you do it on Solaris 9 though? Currently using Solaris 9 update 2. Your help is appreciated.
Thanks,
Sparcman (6 Replies)
Discussion started by: sparcman
6 Replies
3. Solaris
We "lose" the iscsi device after a reboot - i.e., it appears in /dev/rdsk and /dev/dsk but format cannot find it. Obviously, it won't mount either. This happens for two separately defined luns.
We must be missing a step in iscsiadm.
The luns are defined as targets, we can see them in... (2 Replies)
Discussion started by: jim mcnamara
2 Replies
4. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
5. AIX
Hi,
I have an iSCSI LUN attached to an AIX 5.3 box. It's initial size is 250GB, I just grew it on the SAN to 300GB, but AIX is not seeing the change. Right now I have some processes going and it's eating up the disk space. I need to grow this lun by atleast 30GB otherwise the process with bomb... (5 Replies)
Discussion started by: bbbngowc
5 Replies
6. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
7. Red Hat
Hi,
I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is :
node 1 shows the shared iscsi lun as sdc
node 2 shows the same as sdg (changes on reboots)
Due to this (i guess) i get i/o error & i can not read files created by... (0 Replies)
Discussion started by: heman96
0 Replies
8. Solaris
trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try... (2 Replies)
Discussion started by: os2mac
2 Replies
9. AIX
Hello,
I have a filesystem that I'm trying to grow but it's giving me the error:
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The... (5 Replies)
Discussion started by: bbbngowc
5 Replies
LEARN ABOUT NETBSD
libiscsi
LIBISCSI(3) BSD Library Functions Manual LIBISCSI(3)
NAME
libiscsi -- iSCSI network storage protocol implementation
LIBRARY
iSCSI protocol library (libiscsi, -liscsi)
SYNOPSIS
#include <iscsi.h>
int
iscsi_target_set_defaults(iscsi_target_t *target);
int
iscsi_target_start(iscsi_target_t *target);
int
iscsi_target_listen(iscsi_target_t *target);
int
iscsi_target_shutdown(iscsi_target_t *target);
void
iscsi_target_write_pidfile(const char *filename);
int
iscsi_target_setvar(iscsi_target_t *target, const char *name, const char *value);
char *
iscsi_target_getvar(iscsi_target_t *target, const char *name);
int
iscsi_initiator_set_defaults(iscsi_initiator_t *initiator);
int
iscsi_initiator_start(iscsi_initiator_t *initiator);
int
iscsi_initiator_discover(iscsi_initiator_t *initiator, char *x, uint64_t a, int b);
int
iscsi_initiator_shutdown(iscsi_initiator_t *initiator);
int
iscsi_initiator_setvar(iscsi_initiator_t *initiator, const char *name, const char *value);
char *
iscsi_initiator_getvar(iscsi_initiator_t *initiator, const char *name);
DESCRIPTION
libiscsi is a library interface to the iSCSI target and initiator. This conforms to IETF RFC 3720. The corresponding command line utilities
for libiscsi are iscsi-initiator(8) and iscsi-target(8).
In normal operation, a process acting as a target (i.e. presenting storage to the network) will call iscsi_target_set_defaults() and will
then set various values using the iscsi_target_setvar() function. The value of a variable can be retrieved at any time using the
iscsi_target_getvar() function. When all of the variables have been set, the iscsi_target_start() function is called, and the block storage
will be served up by the process.
A useful illustration of the use of these functions can be found in the source code to the iscsi-target(8) utility.
The libiscsi library also provides an implementation of the client end of the iSCSI subsystem, which is known as the initiator. The process
acting as an initiator will first call the iscsi_initiator_set_defaults() function, to set default values for the initiator variables. Once
all the values have been set to the user preferences using the iscsi_initiator_setvar() function, then the iscsi_initiator_start() function
is called.
The libiscsi library can be used to perform iSCSI device discovery by calling the iscsi_initiator_discovery() function. This will return a
list of all the iSCSI targets which are serving up block storage according to the variables which have already been set.
SEE ALSO
iscsi-initiator(8), iscsi-target(8)
HISTORY
The libiscsi library first appeared in NetBSD 4.0. This programmatic interface to the iSCSI subsystem first appeared in NetBSD 6.0.
AUTHORS
Alistair Crooks <agc@NetBSD.org>.
BSD
February 19, 2011 BSD