07-03-2012
Just because it's a raw disk device doesn't mean you're actually reading the disk raw. Disk cache and read-ahead gets used for it just like everything else.
Try hdparm for some more direct tests.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Im looking to get the statistics on a machine
memory, cpu speed drive size etc
thanks in advance (3 Replies)
Discussion started by: simplimarvelous
3 Replies
2. Solaris
Hi ......
I have file system problem when i try to mount get the following message :
mount: /dev/rdsk/c1t4d0s7 not a block device ....
I run fsck it's ok ,,,, after run
newfs -N /dev/dsk/c1t4d0s7 and
fsck -o b=535952 /dev/dsk/c1t4d0s7 .............it's ok ........
At the and when i try... (2 Replies)
Discussion started by: tt155
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am triying to make sure that there exists only one file with the pattern abc* in path /path/. This directory is having many huge files. If there is only one file then I have to take its complete name only to use furter in my script.
I am planning to do like this:
if ; then... (2 Replies)
Discussion started by: new_learner
2 Replies
4. Linux
We are intending to protect a set of user specified files using LVM mirroring where the protected space on which the user files are stored is mirrored on an LV on a different disk. Our problem is that for a user with a custom layout has installed linux with 2 partitons for swap and / and there is... (0 Replies)
Discussion started by: kickdgrass
0 Replies
5. Red Hat
Hi friends,
I wanna know how to block USB devices in my RedHat flavor Operating system.
regards,
Prakash (3 Replies)
Discussion started by: prakashkumar41
3 Replies
6. Shell Programming and Scripting
I talked with this guy who seems to think loop mounting a fs ext3 image on a directory, as opposed to just using the underlying filesystem, will work better as far as IO conflicts. I have no idea why this would be better? I haven't been able to contact him.
Basically we have a daemon that... (0 Replies)
Discussion started by: stevenswj
0 Replies
7. Linux
I use CentOS
I talked with this guy who seems to think loop mounting a fs ext3 image on a directory, as opposed to just using the underlying filesystem, will work better as far as IO conflicts. I have no idea why this would be better? I haven't been able to contact him.
Basically we have a... (1 Reply)
Discussion started by: stevenswj
1 Replies
8. Shell Programming and Scripting
Hello everyone
I am finishing a script allowing me to purge logs on multiple servers, i have one last pb with the ssh command.........it is throwing me the following error :
tcgetattr: Inappropriate ioctl for device (full screen in attached file 1, full script in attached file 2)
It... (15 Replies)
Discussion started by: jimmy75_13
15 Replies
9. UNIX for Advanced & Expert Users
Currently I am using this laborious command
lvdisplay | awk '/LV Path/ {p=$3} /LV Name/ {n=$3} /VG Name/ {v=$3} /Block device/ {d=$3; sub(".*:", "/dev/dm-", d); printf "%s\t%s\t%s\n", p, "/dev/mapper/"v"-"n, d}'
Would like to know if there is any shorter method to get this mapping of... (2 Replies)
Discussion started by: royalibrahim
2 Replies
10. OS X (Apple)
Mac Version 10.15.2 (macOS Catalina)
Does anyone know how to change the name of a connected bluetooth device from the command line on macOS?
I am having trouble with various bluetooth devices which I cannot get the "rename" option in the GUI to "save" properly and so I cannot rename a few... (0 Replies)
Discussion started by: Neo
0 Replies
HP(4) Kernel Interfaces Manual HP(4)
NAME
hp - RH-11/RP04, RP05, RP06 moving-head disk
DESCRIPTION
The octal representation of the minor device number is encoded idp, where i is an interleave flag, d is a physical drive number, and p is a
pseudodrive (subsection) within a physical unit. If i is 0, the origins and sizes of the pseudodisks on each drive, counted in cylinders
of 418 512-byte blocks, are:
disk start length
0 0 23
1 23 21
2 0 0
3 0 0
4 44 386
5 430 385
6 44 367
7 44 771
If i is 1, the minor device consists of the specified pseudodisk on drives numbered 0 through the designated drive number. Successively
numbered blocks are distributed across the drives in rotation.
Systems distributed for these devices use disk 0 for the root, disk 1 for swapping, and disk 4 (RP04/5) or disk 7 (RP06) for a mounted user
file system.
The block files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records.
A `raw' interface provides for direct transmission between the disk and the user's read or write buffer. A single read or write call
results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of
the raw files conventionally begin with an extra `r.' In raw I/O the buffer must begin on a word boundary, and raw I/O to an interleaved
device is likely to have disappointing results.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO
rp(4)
BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
Raw device drivers don't work on interleaved devices.
HP(4)