04-22-2011
Any tips to grow iSCSI LUN
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 and that will not be good. chvg -g <vgname> is not working. I'm thinking I need to varyoff, then varyon this disk in order to get it to work, but I can't afford that now.
If anyone has any tips and have successfully did this without take the fs offline, I would love to hear it.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi,
i have a volume on a LUN of an EMC-storage and i need to increase the
size.
i could increase the size of the LUN on the EMC, i could increase the
size of the disk for solaris, but how can i tell the veritas volume
manager that the disk is larger now?
what i've done:
1. LUN on EMC
2.... (3 Replies)
Discussion started by: pressy
3 Replies
2. 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
3. AIX
Hi,
I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size.
How can I get the OS to see the additional 50GB?
---------- Post updated at 03:22 PM ---------- Previous update... (9 Replies)
Discussion started by: bbbngowc
9 Replies
4. 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
5. 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
6. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
7. Red Hat
Hi,
I have a SAN LUN of 550 GB created as an ext3 partition of the entire lun and need to make the lun and partition larger... 600 GB
# fdisk -l /dev/sdj
Disk /dev/sdj: 590.5 GB, 590558003200 bytes
255 heads, 63 sectors/track, 71797 cylinders
Units = cylinders of 16065 * 512 = 8225280... (3 Replies)
Discussion started by: jamba1
3 Replies
8. 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
9. 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
10. 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
format(1M) format(1M)
NAME
format - format an HP SCSI disk array LUN
SYNOPSIS
device_file
DESCRIPTION
formats one LUN of the HP SCSI disk array associated with device file, device_file. The format will usually be a soft or zeroing format,
in which the controller writes zeroes to the data area and parity area, if any, of the LUN.
NOTE: The above should always be true of a sub-LUN, but the controller might decide, based on certain conditions, to do a full format of a
regular LUN, which consists of sending a mode select and a media initialization command to the physical drive(s) in question, fol-
lowed by zeroing the data and parity area, if any. The conditions which will cause a full format to be done are as follows:
1. The controller received a Mode Select command which requires a drive sector size change.
2. The controller received a Mode Select command which changed a parameter in the Format Device Page(0x03).
3. The LUN contains one or more failed drives. In this case only a certain subset of the drives containing the failed drives
will be formatted.
4. Either the FmtData or the CmpLst bit in the Format Unit CDB is set.
RETURN VALUE
returns the following values:
0 Successful completion.
-1 Command failed.
DIAGNOSTICS AND ERRORS
Errors can originate from problems with:
o
o SCSI (device level) communications
o system calls
Error messages generated by format:
An error in command syntax has occurred.
Enter command again with all required arguments, in the order shown.
To ensure that
does not modify a disk array that is being used by another process, attempts to obtain exclusive access to the disk array. If the
disk array is already opened by another process (for example, LVM -- the Logical Volume Manager), a "" error message is returned by
the driver. To eliminate the "" condition, determine what process has the device open. In the case of LVM, it is necessary to
deactivate the volume group containing the array before formatting array LUNs (see vgchange(1M)).
The LUN number, which is derived from the device file name, is out of range.
The addressed LUN
is not configured, and thus is not known to the array controller.
Utilities must be able to open the device file for raw access.
The device being addressed is not an HP SCSI disk array.
SCSI (device level) communication errors:
Sense data associated with the failed operation is printed.
Error messages generated by system calls:
uses the following system calls:
and
Documentation for these HP-UX system calls contains information about the specific error conditions associated with each call. does not
alter the value of The interpretation of for printing purposes is performed by the system utility
EXAMPLES
To format the HP SCSI disk array LUN on a Series 800:
WARNING
The command will destroy all user data on the addressed LUN.
DEPENDENCIES
The HP C2425 and HP C2427 disk arrays are only supported on Series 700 systems running HP-UX version 9.0X.
The HP C2430 disk array is supported on Series 700 and 800 systems running HP-UX versions 9.0X and 10.0X.
AUTHOR
was developed by HP.
format(1M)