Sponsored Content
Top Forums Programming write() issue during a low level hdd access Post 302397295 by sponnusa on Sunday 21st of February 2010 06:22:37 PM
Old 02-21-2010
Quote:
Originally Posted by Corona688
The crux is that the kernel doesn't do reads when or how you tell it to. It might bundle it with other reads, feed you data from cache, or make you wait until other reads are done. It may have to do a little or a lot of translation between the device and you. This is true for most multitasking operating systems.

Have you tried doing reads?

it may also be using linux's ancient, soon-to-be-removed obsolete and unportable raw system.
Yes. I have tried the read call. It does not return a failure for the read operation on bad sectors.

It returns success. It says it had read the amount of data I request for.

The only way I can identify the error is when I try to compare / analyse the read data with the known pattern.

Thank you.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Low level format?

I want to do a low level format like in windows (C:\format c:) but I don't know how it works in unix or linux.. Can somebody help me ? thnx :) (3 Replies)
Discussion started by: day
3 Replies

2. HP-UX

Access to a second HDD

Hello How to access to a second hard disk on a HP-UX system? Thanks (3 Replies)
Discussion started by: ouniss
3 Replies

3. IP Networking

Best reference for understanding low level info on nic cards drivers and functionality

Hi, What is the best reference that gives in detail on nic cards configuration , assigning multiple ip addresses to a single interface, netlink library etc and all basic stuff at this level..? Thanks (2 Replies)
Discussion started by: Gopi Krishna P
2 Replies

4. AIX

High Runqueue (R) LOW CPU LOW I/O Low Network Low memory usage

Hello All I have a system running AIX 61 shared uncapped partition (with 11 physical processors, 24 Virtual 72GB of Memory) . The output from NMON, vmstat show a high run queue (60+) for continous periods of time intervals, but NO paging, relatively low I/o (6000) , CPU % is 40, Low network.... (9 Replies)
Discussion started by: IL-Malti
9 Replies

5. Programming

System calls and C language low-level qualities???

Hi friends, I hope everyone is fine and doing well. I queried in my previous thread about the low-level qualities of C/C++ languages.I really thank you people for explaining, it was really helpful. One more ambiquity that I have in my mind is regarding the unix system calls like open, creat,... (1 Reply)
Discussion started by: gabam
1 Replies

6. Programming

Why is C/C++ considered low-level languages???

Hi friends, I hope everyone is doing well and fine. I have always been hearing that C/C++ are relatively low-level as compared to Java/C# etc. Could you please tell me some low-level qualities of C/C++? And I think disk deframenters are written in C/C++, please correct me if I am wrong. And please... (5 Replies)
Discussion started by: gabam
5 Replies

7. Programming

Low level X11 programming

How to use X11 without Xlib not XCB? How draw window directly on low level? I must use anyway window manager like Motif? I have ridden that X11 has server-client architecture, client send via TCP/IP to port 6000 request for primitives and get replies. Where is detailed description of it? In X11... (0 Replies)
Discussion started by: AndrzejB
0 Replies
SRAW(8) 						      System Manager's Manual							   SRAW(8)

NAME
sraw - benchmark raw scsi I/O performance under linux SYNOPSIS
sraw [ -fiv6 ] scsi-device [ bstart [ bstep ] ] DESCRIPTION
This program basically reads the specified scsi device and measures the throughput. Note that the filesystem *AND* the buffer cache are bypassed by this code, this program was designed to benchmark the naked scsi drivers by themselves without the need to account for the overhead of any other portion of the kernel. It also could be used to benchmark disk read throughput. This program does a series of reads of the disk, of consecutive areas on the disk. The device is first queried to determine the sector size for the device, and then the series of reads is begun. About 5.0 Mb is read from the device, and then the performance numbers are reported. Note that since the buffer cache is completely bypassed, there is no need to be concerned about cache hits or anything. Output of sraw is a set of lines, 4 numbers per line: blocksize, elapsed time, nblocks and throughput (in bytes per second). scsi-device is either a block device (e.g. /dev/sda, /dev/scd0) or a generic SCSI device (e.g. /dev/sg0). OPTIONS
-f set FUA (Force Unit Access) bit during read. Data is then read from media instead of internal drive cache. -i use legacy ioctl instead of new SG I/O layer (will not work on 2.6 kernel and block devices). -v more verbose output. -6 use 6-bytes instead of 10-bytes read command. In this case, only the first GB of data could be read from media. bstart starting block to check different zones on ZBR discs bstep factor for sequential stepping, default 1. Use 0 for reading always the same blocks (from cache) ERRORS
sraw could issue input/output errors when reading too many blocks at the same time from a block device like /dev/sda. To get rid of them, use /dev/sgN instead. AUTHOR
sraw was first written by Eric Youngdale. Extensions (-v, -f, -6, SG IO, man page) were written by Eric Delaunay. SEE ALSO
sg_dd(8) from sg3-utils package. AVAILABILITY
sraw is available at ftp://tsx-11.mit.edu/pub/linux/ALPHA/scsi/ Nov 1993 SRAW(8)
All times are GMT -4. The time now is 08:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy