07-31-2007
I haven't tried it, but the point is that it is a raw disk - i.e. FS unknown... so things such as 'blocksize' does not exist or unknown...
I just need to open the device... in a C program... like in Linux the HDD devices are /dev/sda, /dev/hda, etc...
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
RAW(8) System Administration RAW(8)
NAME
raw - bind a Linux raw character device
SYNOPSIS
raw /dev/raw/raw<N> <major> <minor>
raw /dev/raw/raw<N> /dev/<blockdev>
raw -q /dev/raw/raw<N>
raw -qa
DESCRIPTION
raw is used to bind a Linux raw character device to a block device. Any block device may be used: at the time of binding, the device
driver does not even have to be accessible (it may be loaded on demand as a kernel module later).
raw is used in two modes: it either sets raw device bindings, or it queries existing bindings. When setting a raw device, /dev/raw/raw<N>
is the device name of an existing raw device node in the filesystem. The block device to which it is to be bound can be specified either
in terms of its major and minor device numbers, or as a path name /dev/<blockdev> to an existing block device file.
The bindings already in existence can be queried with the -q option, which is used either with a raw device filename to query that one
device, or with the -a option to query all bound raw devices.
Unbinding can be done by specifying major and minor 0.
Once bound to a block device, a raw device can be opened, read and written, just like the block device it is bound to. However, the raw
device does not behave exactly like the block device. In particular, access to the raw device bypasses the kernel's block buffer cache
entirely: all I/O is done directly to and from the address space of the process performing the I/O. If the underlying block device driver
can support DMA, then no data copying at all is required to complete the I/O.
Because raw I/O involves direct hardware access to a process's memory, a few extra restrictions must be observed. All I/Os must be cor-
rectly aligned in memory and on disk: they must start at a sector offset on disk, they must be an exact number of sectors long, and the
data buffer in virtual memory must also be aligned to a multiple of the sector size. The sector size is 512 bytes for most devices.
OPTIONS
-q, --query
Set query mode. raw will query an existing binding instead of setting a new one.
-a, --all
With -q , specify that all bound raw devices should be queried.
-h, --help
Display help text and exit.
-V, --version
Display version information and exit.
BUGS
The Linux dd(1) command should be used without the bs= option, or the blocksize needs to be a multiple of the sector size of the device
(512 bytes usually), otherwise it will fail with "Invalid Argument" messages (EINVAL).
Raw I/O devices do not maintain cache coherency with the Linux block device buffer cache. If you use raw I/O to overwrite data already in
the buffer cache, the buffer cache will no longer correspond to the contents of the actual storage device underneath. This is deliberate,
but is regarded either a bug or a feature depending on who you ask!
NOTES
Rather than using raw devices applications should prefer open(2) devices, such as /dev/sda1, with the O_DIRECT flag.
AUTHOR
Stephen Tweedie (sct@redhat.com)
AVAILABILITY
The raw command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/.
util-linux August 1999 RAW(8)