12-15-2008
Wouldn't the LUN serial numbers or target numbers allow you to correlate the two? The WWNs should be enough to identify the physical Filer heads you are talking to.
10 More Discussions You Might Find Interesting
1. Solaris
All solaris rescue gurus out there ....
I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory.
The machine is (was) running Vxvm with the root volume encapsulated.
I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies
2. Solaris
Is there a way to create "softpartitions" with Veritas Volume Manager?
I have a bunch of disks and i want to create a RAID 5 with them. On that RAID5, i want to split that RAID into two separated file systems like i could do it with SDS/LVM or ZFS, but i don't want to create two RAID5 in the... (3 Replies)
Discussion started by: pressy
3 Replies
3. Solaris
Hi all,
I have a compatibly issues with a new hardware
My config is the following one :
Solaris 10
V490 Hardware
2 X HBA Qlogic 2310f cards
An HP EVA 5000 for storage ...
Veritas VxVM 4.1 MP1
When I reboot my server, VxVM is trying to mount/use the volume before it's... (0 Replies)
Discussion started by: unclefab
0 Replies
4. Filesystems, Disks and Memory
whats the command line to find vxvm (veritas volume manager) version installed in solaris OS? (3 Replies)
Discussion started by: na75369
3 Replies
5. Solaris
Hi Friends,
This is suresh reddy. Recently i download veritas cluster & volume manager package from internet. I didn't found any key inside the package. If any body having the VxVM key kindly send to me.
mail id: cvsureshreddy@gmail.com
Regards,
C V Suresh Reddy (1 Reply)
Discussion started by: suresha2lu
1 Replies
6. Solaris
Hi,
Could any one tel me VxVM simulator is available in market or can it be downloaded from any were???? (4 Replies)
Discussion started by: sudhan143
4 Replies
7. Solaris
hi all,
how can we check whether vxvm is installed in our system or not in solaris?
Thanks in advance
dinu (4 Replies)
Discussion started by: dinu
4 Replies
8. Solaris
This is going to mean nothing to most....
I'm working on a E4500 server running Solaris 2.5.1 and VXVM 2.5.5 :eek:
I've replaced the rootmirror and would like to monitor progress of the resync
It's only a 2Gb /partition so it shouldn't take too long.
In later versions
vxtask list
... (5 Replies)
Discussion started by: Martincorneuk
5 Replies
9. Solaris
Hello all,
i try to allocate the same LUN to two server (or more in the future)
i use solaris 10, vxvm (vxfs) for data and solaris zones and EMC DMX-4, i try to migrate solaris zones between servers in case of problem.
and this is what i want to do
- affect LUN to srv00124 and srv10155
-... (5 Replies)
Discussion started by: mat_solaris
5 Replies
10. Solaris
Hello,
I was assigned some Solaris machines and need to patch them to N-1, where N is the latest OS realease, which means, upgrade till one version before the latest one.
I do not now a lot about Solaris. What I only know is that need to make use of live upgrade and be careful with VxVM... (4 Replies)
Discussion started by: feroccimx
4 Replies
LEARN ABOUT SUNOS
path_to_inst
path_to_inst(4) File Formats path_to_inst(4)
NAME
path_to_inst - device instance number file
SYNOPSIS
/etc/path_to_inst
DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers.
The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible
devices that it may drive is referred to by a given special file.
In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by add_drv(1M) and drvconfig(1M).
Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it.
The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However,
any changes made in this file will be lost if add_drv(1M) or drvconfig(1M) is run before the system is rebooted.
Each instance entry is a single line of the form:
"physical name" instance number "driver binding name"
where
physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes.
instance number is a decimal or hexadecimal number.
driver binding name is the name used to determine the driver for the device.
This name may be a driver alias or a driver name. The driver binding name must be enclosed in double quotes.
EXAMPLES
Example 1: Sample path_to_inst Entries
Here are some sample path_to_inst entries:
"/iommu@f,e0000000" 0 "iommu"
"/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma"
"/obio/serial@0,100000" 0 "zs"
"/SUNW,sx@f,80000000" 0 "SUNW,sx"
FILES
/etc/path_to_inst
SEE ALSO
add_drv(1M), boot(1M), drvconfig(1M), mknod(1M)
WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap
device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers
than they did before, and special files created via mknod(1M) may refer to different devices than expected.
For the same reasons, changes should not be made to this file without careful consideration.
NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future
release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API.
SunOS 5.10 2 Nov 1995 path_to_inst(4)