This is documentation we have tested and verified in our QA lab, and its known to be working on RHEL 5.5 with a P2000 G3 FC. Its based on the RH online storage guide. It assumes you're using multipathing.
List the disks by typing
multipath -l
This will give you the current host and lun numbers (x:0:0:n, where x is the host number, n is the lun number).
A sample output is below:
Once you've created the lun on the SAN, type (again, where x is the host number, n is the lun)
For each host number that should have access to the lun.
So looking back at our sample it'd be:
Next type
and you should now see the new device. At that point you should be able to add the volume to oracle ASM.
Officially, we had high of 96°F with a relative humidity of 52% here in Rockville Md today. But my car's thermometer said the outside temp was 110° when I first got in this afternoon. After driving for 30 minutes it cooled down to 103°. I actually have a nasty burn on my hand just from leaning... (19 Replies)
Hi,
I need to install Oracle Enterprise Linux 5.0 on IBM3400.Before start it,I expect your valuable suggestions regarding partition size...etc.
This server is having 146 GB of hard disk and 4GB of RAM.I need to create 15 restricted users on this server.These 15 users will access their folders... (1 Reply)
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
hi all :)
i'd like to remove a broken scsi tape device from a system p5 520. it is the only device on the external scsi hookup.
then i would like to add a new scsi tape device (same model).
is this, and if - how ?, doable without rebooting? (using aix 5.3)
best regards,
deuter (2 Replies)
Hi,
Anyone can help me, just want to confirm, if possible adding a disk storage that we have a RAWDATA with +ASM in our database. If possible, what would you recommend "workaround used" from us to do and the preparation. And also how long the downtime will take.
Our disk continuous to grow,... (0 Replies)
Hi all,
I have an Oracle Enterprise Linux 5.5 server which is a virtual guest on a vSphere host.
I have provisioned 500GB disk space from SAN. I then migrated the VM from a 200GB disk onto the new 500GB disk. I then increased the disk space allocated to the VMware to the maximum size of... (7 Replies)
Hello,
I have DS4000 IBM SAN Storage ( aka FastT Storage )
One of my disks has failed and I had a hot spare disk covering all the arrays. As the disk failed, immediately the hotspare disk took over the failed disk ( see the JPEG in the attachment )
My Question: How can I make the hotspare... (1 Reply)
Server Model
HP Proliant DL380P, Gen 8
Raid Controller= HP smart Array P420i
Operating system Installation OEl5.8
On first boot after OS installation
ERROR:
Red Hat nash Version 5.119.6 starting -300.10.1.el5uek)’
Mounting proc Filesystem
Reading all physical volume this may take a... (0 Replies)
Server Model
HP Proliant DL380P, Gen 8
Raid Controller= HP smart Array P420i
Operating system Installation OEl5.8
On first boot after OS installation
ERROR:
Red Hat nash Version 5.119.6 starting -300.10.1.el5uek)'
Mounting proc Filesystem
Reading all physical volume this may take... (1 Reply)
Hi, Here is the issue. Some more memory has been added from vCenter to the virtual machine. From the virtual machine running SuSE 11 SP3.
# modprobe acpiphp
# modprobe acpi-memhotplug
# grep -v online /sys/devices/system/memory/*/state
#
It looks like there is no offline memory, but free... (1 Reply)
Discussion started by: aixlover
1 Replies
LEARN ABOUT OSF1
voldiskadd
voldiskadd(8) System Manager's Manual voldiskadd(8)NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager
SYNOPSIS
/usr/sbin/voldiskadd disk-address-list
DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for
use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility.
One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp
(for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names
in the /dev/disk directory.
For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a
The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk
to exclude (for example, dsk5).
The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified,
that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for
future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the
disk group.
If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated.
Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should
not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage
Manager. For new disks, all space on the disk becomes free space in the disk's disk group.
Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target
disks for an operation.
The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions.
Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group.
This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk
group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot
spare device. Creating new disk groups in which to import new disks.
If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist-
ing contents.
This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a
disk label. Encapsulation is performed by calling volencap. Reconnecting a drive that was temporarily inaccessible.
This situation is detected automatically, by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the volrecover script.
ERRORS
You may receive the following messages when using the voldiskadd command:
Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open.
This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be
a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device.
special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data.
Would you like to continue?? [y,n,q,?] (default: n)
This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints
this message to warn that a disk partition may have valid data which could be destroyed.
If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning
message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM.
FILES
A list of disks to exclude from use by voldiskadd.
SEE ALSO disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8)voldiskadd(8)