11-26-2009
A question about HPUX PV link...
Are "/dev/dsk/c58t6d7" and "/dev/dsk/c94t0d4" assigning to a same disk?
results of "vgdisplay -v"
PV Name /dev/dsk/c58t6d7
PV Name /dev/dsk/c94t0d4 Alternate Link
PV Name /dev/dsk/c75t6d7 Alternate Link
PV Name /dev/dsk/c95t0d4 Alternate Link
PV Name /dev/dsk/c57t6d7 Alternate Link
PV Name /dev/dsk/c93t0d4 Alternate Link
PV Name /dev/dsk/c76t6d7 Alternate Link
PV Name /dev/dsk/c96t0d4 Alternate Link
PV Status available
Total PE 1759
Free PE 0
Autoswitch On
results of "ioscan"
disk 1643 0/0/8/0/0.97.0.0.0.6.7 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c58t6d7 /dev/rdsk/c58t6d7
disk 1887 0/0/8/0/0.97.2.0.0.0.4 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c94t0d4 /dev/rdsk/c94t0d4
disk 1600 0/0/10/0/0.97.0.0.0.6.7 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c75t6d7 /dev/rdsk/c75t6d7
disk 1921 0/0/10/0/0.97.2.0.0.0.4 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c95t0d4 /dev/rdsk/c95t0d4
disk 1569 1/0/8/0/0.97.0.0.0.6.7 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c57t6d7 /dev/rdsk/c57t6d7
disk 1837 1/0/8/0/0.97.2.0.0.0.4 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c93t0d4 /dev/rdsk/c93t0d4
disk 1607 1/0/10/0/0.97.0.0.0.6.7 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c76t6d7 /dev/rdsk/c76t6d7
disk 1936 1/0/10/0/0.97.2.0.0.0.4 sdisk CLAIMED DEVICE
HP OPEN-9
/dev/dsk/c96t0d4 /dev/rdsk/c96t0d4
Thanks in advance!
9 More Discussions You Might Find Interesting
1. IP Networking
We have an HPUX machine that is having a routing problem. Any traffic sent on the local network (same switch) works fine. However, when we try to send traffic to any other ip the machine NAT's the ip to that of the gatway and nothing goes any further.
For example if I try to ping 10.1.1.1 from... (3 Replies)
Discussion started by: robanic
3 Replies
2. UNIX for Dummies Questions & Answers
I am curious about one thing.
Lets say I have a file file-a to which new generations are created on demand by simply archiving it (ex: file-a.tar.gz) and having the new one created with the same original filename file-a.
Now what I want to know is if I create a hard/soft link to file-a, what... (1 Reply)
Discussion started by: Browser_ice
1 Replies
3. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
4. HP-UX
why is that I need to go to /usr/sbin> in order to run send mail
how can I run sendmail where ever folder I'm in...
e.g. like
/stuff/games/sendmail
ksh: sendmail: not found (7 Replies)
Discussion started by: makaveli
7 Replies
5. Post Here to Contact Site Administrators and Moderators
Members who crossed 100s in answering might have felt this already:
This forum has many topics, nobody could be expert in all ( is it not !!), so i suggest there should be someway to see the posts which are all of my kind.
How to find my kind ... ( or anybodies expertise )..
after 100 posts... (8 Replies)
Discussion started by: thegeek
8 Replies
6. HP-UX
Hi,
Hoping someone can offer some advice on something i have not dealt with before.
We have a server that seems to have some very strange configuration done on it. It has 2 physical NIC's and rather than both be aggregated into LAN900 we have 1 in LAN900 and 1 in LAN901? (See Below)... (2 Replies)
Discussion started by: Andyp2704
2 Replies
7. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
8. Programming
Hello All,
I've encountered a strange behaviour from g++ that doesn't make sense to me. Maybe you can shed some light on it:
I have a bunch of source files and want to compile them and link them with a static library liba.a located in /usr/local/lib64 into an executable
Approach 1 works... (0 Replies)
Discussion started by: magelord
0 Replies
9. UNIX for Advanced & Expert Users
Simple question: how to package from source in hpux?
On Linux slackware i Use configure,make,make install DESTDIR=$pkg,etc..
and then makepkg -l y -c n.
Is possible something similar on hpux?
I want to create a depot for samba because,the official
doesn't had the winbind pam,and the package on... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
volfs(7FS) File Systems volfs(7FS)
NAME
volfs - Volume Management file system
DESCRIPTION
volfs is the Volume Management file system rooted at root_dir. The default location for root-dir is /vol, but this can be overridden using
the -d option of vold (see vold(1M)). This file system is maintained by the Volume Management daemon, vold, and will be considered to be
/vol for this description.
Media can be accessed in a logical manner (no association with a particular piece of hardware), or a physical manner (associated with a
particular piece of hardware).
Logical names for media are referred to through /vol/dsk and /vol/rdsk. /vol/dsk provides block access to random access devices. /vol/rdsk
provides character access to random access devices.
The /vol/rdsk and /vol/dsk directories are mirrors of one another. Any change to one is reflected in the other immediately. The dev_t for a
volume will be the same for both the block and character device.
The default permissions for /vol are mode=0555, owner=root, group=sys. The default permissions for /vol/dsk and /vol/rdsk are mode=01777,
owner=root, group=sys.
Physical references to media are obtained through /vol/dev. This hierarchy reflects the structure of the /dev name space. The default per-
missions for all directories in the /vol/dev hierarchy are mode=0555, owner=root, group=sys.
mkdir(2), rmdir(2), unlink(2) (rm), symlink(2) (ln -s), link(2) (ln), and rename(2) (mv) are supported, subject to normal file and direc-
tory permissions.
The following system calls are not supported in the /vol filesystem: creat(2), only when creating a file, and mknod(2).
If the media does not contain file systems that can be automatically mounted by rmmount(1M), users can gain access to the media through the
following /vol locations:
+-----------------------------------+------------------------------------+
| Location | State of Media |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unnamed_floppy | formatted unnamed floppy-block |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unnamed_floppy | formatted unnamed floppy-raw |
| | device access |
+-----------------------------------+------------------------------------+
|/vol/dev/diskette0/unlabeled | unlabeled floppy-block device |
| | access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdiskette0/unlabeled | unlabeled floppy-raw device access |
+-----------------------------------+------------------------------------+
|/vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM-block device access |
+-----------------------------------+------------------------------------+
|/vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM-raw device access |
+-----------------------------------+------------------------------------+
For more information on the location of CD-ROM and floppy media, see System Administration Guide: Basic Administration or rmmount(1M).
Partitions
Some media support the concept of a partition. If the label identifies partitions on the media, the name of the media becomes a directory
with partitions under it. Only valid partitions are represented. Partitions cannot be moved out of a directory.
For example, if disk volume 'foo' has three valid partitions, 0, 2, and 5, then:
/vol/dsk/foo/s0
/vol/dsk/foo/s2
/vol/dsk/foo/s5
for block access and
/vol/rdsk/foo/s0
/vol/rdsk/foo/s2
/vol/rdsk/foo/s5
for character access.
If a volume is relabeled to reflect different partitions, the name space changes to reflect the new partition layout.
A format program can check to see if there are others with the volume open and not allow the format to occur if it is. Volume Management,
however, does not explicitly prevent the rewriting of a label while others have the volume open. If a partition of a volume is open, and
the volume is relabeled to remove that partition, it will appear exactly as if the volume were missing. A notify event will be generated
and the user may cancel the operation with volcancel(1), if desired.
SEE ALSO
volcancel(1), volcheck(1), volmissing(1) rmmount(1M), vold(1M), rmmount.conf(4), vold.conf(4)
System Administration Guide: Basic Administration
SunOS 5.10 8 Feb 1995 volfs(7FS)