08-01-2007
You onlt chose the path containing the device, you need to use the full path to the actual device.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have been tasked with archiving Oracle tables. The data is on raw devices, and possibly will span multiple logical volumes.
Has anyone ever had to do this? How did you accomplish it?
Any references to accomplish this would be greatly appreciated.
Thanks, (2 Replies)
Discussion started by: isenhart
2 Replies
2. UNIX for Dummies Questions & Answers
What do u mean by raw and cooked disk? What are the advantages of having raw disk?
Thanks n regards, (1 Reply)
Discussion started by: kingsto88
1 Replies
3. Solaris
Hi all,
I would like to know how to make new partitions....
I currently have allocated 60G for various slices (I have totally used 4 out of 7 available slices...
I am running only solaris on my box.
My plan is to have entire disk dedicated to solaris and run other OS from within... (19 Replies)
Discussion started by: wrapster
19 Replies
4. Solaris
I am using Solaris 10. I have a raw device attached to my system which is
/dev/md/rdsk/d91
I want to mount this as a disk with file system on a mount point /u05.
Actually this raw device was earlier part of Oracle ASM. Now I have removed this disk from ASM, and want to use it as normal... (3 Replies)
Discussion started by: fahdmirza
3 Replies
5. Solaris
Hi,
Can any one please provide the command to format an Oracle Raw Disk in Solaris 10.
I have been used the following commands:
dd if=/dev/zero of=<raw disk path>
Thanks
---------- Post updated at 12:20 PM ---------- Previous update was at 10:11 AM ----------
Well this didn't give... (0 Replies)
Discussion started by: Mack1982
0 Replies
6. Solaris
I noticed we have a small splice on end of disk that is not mounted. What could that be and how do we move it few sectors?
Thanks. (7 Replies)
Discussion started by: orange47
7 Replies
7. Solaris
I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below:
root@moneta # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 513M 9.3G 6% /
... (0 Replies)
Discussion started by: fretagi
0 Replies
8. Solaris
I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below:
root@moneta # df -h
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies
9. Solaris
Hi,
I'm in process of creating oracle RAC using Solaris 10 in VirtualBox. I want to know how can I change the ownership of device e.g /dev/rdsk/c0t3d0s0 and keep it persistent during rebbots.
When I enter
chown grid:install /dev/rdsk/c0t3d0s0
ls -l still shows root:root.
Thanks
... (2 Replies)
Discussion started by: jia786
2 Replies
10. Red Hat
Hi All,
Hope someone can help me with this.
I have noticed that on some of the servers i am currently administering there is a difference in the setup of some of the LVM disks.
Some of the disks have been created by SN disk allocated, disk partitioned using type 8e over the entire disk,... (2 Replies)
Discussion started by: Tommyk
2 Replies
LEARN ABOUT OPENSOLARIS
di_path_devfs_path
di_devfs_path(3DEVINFO) Device Information Library Functions di_devfs_path(3DEVINFO)
NAME
di_devfs_path, di_devfs_minor_path, di_path_devfs_path, di_path_client_devfs_path, di_devfs_path_free - generate and free path names
SYNOPSIS
cc [ flag... ] file... -ldevinfo [ library... ]
#include <libdevinfo.h>
char *di_devfs_path(di_node_t node);
char *di_devfs_minor_path(di_minor_t minor);
char *di_path_devfs_path(di_path_t path);
char *di_path_client_devfs_path(di_path_t path);
void di_devfs_path_free(char *path_buf);
PARAMETERS
node The handle to a device node in a di_init(3DEVINFO) snapshot.
minor The handle to a device minor node in a snapshot.
path The handle to a device path node in a snapshot.
path_buf A pointer returned by di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), or di_path_client_devfs_path().
DESCRIPTION
The di_devfs_path() function generates the physical path of the device node specified by node.
The di_devfs_minor_path() function generates the physical path of the device minor node specified by minor.
The di_path_devfs_path() function generates the pHCI physical path to the device associated with the specified path node. The returned
string is identical to the di_devfs_path() for the device had the device not been supported by multipath.
The di_path_client_devfs_path() function generates the vHCI physical path of the multipath client device node associated with the device
identity of the specified path node. The returned string is identical to the di_devfs_path() of the multipath client device node.
The di_devfs_path_free() function frees memory that was allocated to store the path returned by di_devfs_path(), di_devfs_minor_path(),
di_path_devfs_path(), and di_path_client_devfs_path(). The caller is responsible for freeing this memory by calling di_devfs_path_free().
RETURN VALUES
Upon successful completion, the di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), and di_path_client_devfs_path() functions
return a pointer to the string containing the path to a device node, a device minor node, or a device path node, respectively. Otherwise,
they return NULL and errno is set to indicate the error. For a non-NULL return, the path will not have a "/devices" prefix.
ERRORS
The di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), and di_path_client_devfs_path() functions will fail if:
EINVAL The node, minor, or path argument is not a valid handle.
The di_devfs_path(), di_devfs_minor_path(), di_path_devfs_path(), and di_path_client_devfs_path() functions can also return any error value
returned by malloc(3C).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Committed |
+-----------------------------+-----------------------------+
|MT-Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO
di_init(3DEVINFO), libdevinfo(3LIB), malloc(3C), attributes(5)
Writing Device Drivers
SunOS 5.11 15 May 2008 di_devfs_path(3DEVINFO)