Hi
I have a Sunfire X4100 box with a 4 disk Chassis (although I only have 2 disks in it). I have been asked to add two more disks into the chassis so that I can mirror the original two using SVM .....Ive read through a couple of SVM docs but am finding it a little confusing, and if any of you... (1 Reply)
hi ;i had setup a lan connection under sco open server release 5.0.5 between 2 pc with tcp/ip , but i want to mirror one of both for other but i can not do this please tell me about how to configure 2 pc for mirroring ? thank you::( (3 Replies)
Hello,
i'm pretty new in using solaris (5.10) and i'm kind of stuck with one problem. I'm trying to create a disk mirror cause of data redundancy. I've installed second disk in my system, prepared everything for creating a mirror (by following the instructions) and don't get any responce for... (7 Replies)
LFTP Mirroring
We are planning to use lftp to mirror some of the files and
directories on to the remote server.
What we exactly want to do is mirror some of the directories and
exclude some of the the directories from "/" i.e. main root. . What
lftp is doing is... (0 Replies)
Really sorry for the long posting. But i would really want to clear all the doubts.
I have 2 disk c0t0d0 & c0t1d0, i wanted to mirror c0t1d0 (mirror) to c0t0d0 (main).
Creating state database replica:
metadb -a -c3 -f c0t0d0s7
... (3 Replies)
Hi Folks,
I am a newbie in AIX.
Can someone please tell me how to do root mirroring in AIX LPAR which is created from mksysb image via HMC/NIM. ?
AIX 5.3/6.1
Let me know.
Thanks in advance (2 Replies)
Discussion started by: snchaudhari2
2 Replies
LEARN ABOUT MOJAVE
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)