05-14-2011
Bootinfo shows the old size.
bash-3.00# bootinfo -s hdisk3
256000
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
LEARN ABOUT OPENSOLARIS
libbash
LIBBASH(7) libbash Manual LIBBASH(7)
NAME
libbash -- A bash shared libraries package.
DESCRIPTION
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
using
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
__<library_name>_
For example, internal function myfoosort of hashstash library should be named as
__hashstash_myfoosort
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
AUTHORS
Hai Zaar <haizaar@haizaar.com>
Gil Ran <ril@ran4.net>
SEE ALSO
ldbash(1), ldbashconfig(8), getopts(1), hashstash(1) colors(1) messages(1) urlcoding(1) locks(1)
Linux Epoch Linux