|
|
Sponsored Content
Top Forums
Programming
write() issue during a low level hdd access
Post 302397288 by sponnusa on Sunday 21st of February 2010 06:10:44 PM
02-21-2010
thank you.
So, there is no way around it without writing a device driver to handle the read/write operations? Is that right?
I have a utility written in python which able to identify the bad sectors exactly as the same way as the C program. I am not sure, if python would have implemented anything internally (a device driver) to achieve this. I'm currently downloading the python source code to analyse.
I am sure C is more low level then python (which is btw the dumbest statement, i've said
) and should be able to achieve it. It's little weird that the program fails to identify the bad sectors. I have analysed the following programs so far for such an implementation. And all have the same code.
Testdisk, dd, ddrescue, badblocks etc.,.
So does this conclude that the none of the above available usermode linux opensource programs are really doing what they are claiming for? (data recovery / forensics utilities?) All the above program implements O_DIRECT options too.
Well, I guess I am in need of a fix now!
It also sounds a little weird that there are no user mode programs (not even one?) available in linux that can do a direct I/O with the disk. (Except that I am willing to write one using the libata / scsi libraries which can directly talk to the ATA (PATA / SATA) devices using ATA protocol (i've done this in dos using assembly) and SG / SCSI protocol to the scsi devices).
Anyways, thanks for all your input and guidance. Atleast it got me to do the O_DIRECT implementation. Please update this thread if there are any more information to be shared / assisted.
Thanks again for all the help.
So, there is no way around it without writing a device driver to handle the read/write operations? Is that right?
I have a utility written in python which able to identify the bad sectors exactly as the same way as the C program. I am not sure, if python would have implemented anything internally (a device driver) to achieve this. I'm currently downloading the python source code to analyse.
I am sure C is more low level then python (which is btw the dumbest statement, i've said
) and should be able to achieve it. It's little weird that the program fails to identify the bad sectors. I have analysed the following programs so far for such an implementation. And all have the same code.Testdisk, dd, ddrescue, badblocks etc.,.
So does this conclude that the none of the above available usermode linux opensource programs are really doing what they are claiming for? (data recovery / forensics utilities?) All the above program implements O_DIRECT options too.
Well, I guess I am in need of a fix now!
It also sounds a little weird that there are no user mode programs (not even one?) available in linux that can do a direct I/O with the disk. (Except that I am willing to write one using the libata / scsi libraries which can directly talk to the ATA (PATA / SATA) devices using ATA protocol (i've done this in dos using assembly) and SG / SCSI protocol to the scsi devices).
Anyways, thanks for all your input and guidance. Atleast it got me to do the O_DIRECT implementation. Please update this thread if there are any more information to be shared / assisted.
Thanks again for all the help.
|
|
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
update-python-modules
UPDATE-PYTHON-MODULES(8) System Manager's Manual UPDATE-PYTHON-MODULES(8) NAME
update-python-modules - byte-compile python modules SYNOPSIS
update-python-modules [options] [package.public [...]] DESCRIPTION
The update-python-modules command is part of the python-support bundle. update-python-modules is responsible for the byte-compilation of python modules. When used in byte-compilation mode, it will byte-compile modules references in the files given on the command line. When used in installation mode, it will byte-compile them once for each installed python version, and will make them available for all of them. At each invocation, with or without arguments, update-python-modules will check for installed python versions, and will build or remove modules according to new or removed versions since the last time it was run. ARGUMENTS
Arguments must be files or directories located in the /usr/share/python-support directory. Depending on their extension, they are treated differently. package.public A file listing public modules to install for each version. These modules must lie in /usr/share/pyshared or /usr/lib/pyshared. package.private A file listing private modules to byte-compile for one Python version. package/ A legacy directory hierarchy of public modules. The C extensions and portions that change with the Python version are to be found in /usr/lib/python-support/pythonX.Y/package/. package.dirs A legacy file listing directories where to find private modules. OPTIONS
-h, --help Show summary of options. -v, --verbose Detail all actions while they are performed. -b, --bytecompile Only accept to work on private modules. When given this option, update-python-modules will fail if passed references to public mod- ules. -i, --install Only accept to work on public modules. When given this option, update-python-modules will fail if passed references to public mod- ules. -c, --clean Clean modules instead of installing them. -a, --rebuild-all Rebuild all private modules. This is necessary when the default python version was changed, for example. -f, --force-rebuild-all Clean all modules (public and private), and rebuild them. FILES
/usr/lib/pymodules/pythonX.Y/ These directories contain the byte-compiled modules for version pythonX.Y. SEE ALSO
/usr/share/doc/python-support/README.gz AUTHOR
Josselin Mouette <joss@debian.org>. 18 Feb 2009 UPDATE-PYTHON-MODULES(8)