01-29-2019
Quote:
Thanks for your input - actually I had forgotten about the zoning and the new space *was* coming from a different NetAPP. However my storage guy did *not* forget. Plus, as a troubleshooting step he added a new LUN from a NetAPP that was already connected to the server. No luck. Also got another server (did I mention this earlier) that is in the same zoning-group, same OS levels and it could get a new LUN with no problem. So it really seems isolated to this one server. (Which really just makes no sense to me...)
Well, think of it like that: having found out what was NOT the culprit is a step forward, no? ;-)
First off, i suppose you also have checked that the device the disk is supposed to be attached to is also working - if you have all your other NetApp disks attached to FC adapter A and the new one to adapter B then adapter B might be the problem.
I have no experience with the NetApp drivers but maye something is wrong with the ODM entries concerning the device(s). You may try a
rmdev -Rdl on the adapter and then a rediscovery via
cfgmgr to rebuild that. Notice that to
completely clean the ODM you need to
varyoffvg all the volume groups consisting of disks coming from the adapter you are deleting. If they are still online they will hold at least one FC connection (i.e one hdisk device if the driver is multipath enabled) open.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
Can anyone explain me the meanning of the following errors:
LABEL: SC_DISK_ERR2
IDENTIFIER: B6267342
Description
DISK OPERATION ERROR
Probable Causes
DASD DEVICE
Failure Causes
DISK DRIVE
DISK DRIVE ELECTRONICS
Recommended Actions
PERFORM PROBLEM DETERMINATION... (1 Reply)
Discussion started by: gianlu
1 Replies
2. UNIX for Dummies Questions & Answers
getting "NFS mount: netapp : RPC: Program not registered" error
searched the site but none of the fixes from previous threads are helping (2 Replies)
Discussion started by: calamine
2 Replies
3. Solaris
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)
Discussion started by: waibabe
1 Replies
4. UNIX for Advanced & Expert Users
I have the below script which has been written to retrieve files from tape drive i.e. TSM server. Now i have to write the script using UNIX commands for retrieve operation but I am not able to proceed. The script is:
#!/usr/local/bin/expect -f
set timeout 1800
set file
spawn $env(SHELL)... (0 Replies)
Discussion started by: hrsaurav
0 Replies
5. UNIX for Dummies Questions & Answers
Firstly, system setup -
HP900 K460, 3 internal hard drives that make up the system volume group(vg00) no software mirroring
HP-ux version 11.00
2 Nike 20 raid arrays attached, fully populated with 40 4gb hot swap drives(All used in production environment)
I have 3 disks that make up my... (0 Replies)
Discussion started by: rees_a
0 Replies
6. UNIX for Dummies Questions & Answers
Hi Guys,
I have a failing 4gb (c0t5d0) drive that contains lvol4 -8 on hp-ux. It's not the boot disk but is part of VG00 volume group. Within that group, I have a disk (c0t4d0) of the same size that has 1 lvol on it for swap(4gb) I also have a seperate 1.5 gb swap volume on another physical disk... (1 Reply)
Discussion started by: rees_a
1 Replies
7. AIX
Hi Guys,
I tried running the firefox in AIX 6.1 and got the below error..
-bash-3.00# firefox
Could not load program /usr/mozilla/firefox/firefox-bin:
Could not load module /usr/mozilla/firefox/libxul.so.
Dependent module /usr/lib/libgtk-x11-2.0.a(libgtk-x11-2.0.so.0) could not... (0 Replies)
Discussion started by: kkeng808
0 Replies
8. Shell Programming and Scripting
#!/bin/ksh for AIX
used=0
mount=${1:-"/mountpoint"}
threshold=${2:-80}
#message="hello"
#SUBJECT="Disk Space Alert"
#EMAIL="xyz@abcinc.com"
used=`df -k $mount | grep % | awk '{print $5}' | sed 's/%//g'`
#echo "Free Space available under \"$mount\" is `expr 100 - $used`%.\n">$message
... (6 Replies)
Discussion started by: rajeshw61
6 Replies
9. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
10. AIX
I have 2 AIX 6.1 systems running on PowerPCs - production and .. .everything else. :p . Until the installation of a TLS certificate in an application, some copying of files ("cloning an environment") and upgrading a listener, sending a kill -15 worked on any script/application, so long as we were... (6 Replies)
Discussion started by: Mrucker
6 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)