Re: Error reported dd'ing close of end of block device with skip

2005-12-14 Thread Corinna Vinschen
On Dec 14 16:04, Eric Blake wrote: > > > > Btw., I just applied a patch which implements O_DIRECT, which will be > > available in the next snapshot. The same restriction as on Linux > > applies, which is, the buffers used in read/write operations must be > > sector-aligned. Note that using O_DIR

Re: Error reported dd'ing close of end of block device with skip

2005-12-14 Thread Eric Blake
> > Btw., I just applied a patch which implements O_DIRECT, which will be > available in the next snapshot. The same restriction as on Linux > applies, which is, the buffers used in read/write operations must be > sector-aligned. Note that using O_DIRECT requires to rebuild the > application, so

Re: Error reported dd'ing close of end of block device with skip

2005-12-14 Thread Corinna Vinschen
On Dec 13 19:05, Loh, Joe wrote: > We downloaded cygwin-inst-20051213.tar.bz2 and implemented the solution > recommended below. So far, our cursory testing indicates that we are > able to do unbuffered read. However, we are not seeing any "bug" that > was referenced here. What is the "bug" that

RE: Error reported dd'ing close of end of block device with skip

2005-12-14 Thread Loh, Joe
(3, 0x10EED60, 1), errno 0 Thanks, Joe -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED] Sent: Thursday, December 08, 2005 4:57 AM To: cygwin@cygwin.com Subject: Re: Error reported dd'ing close of end of block device with skip On Dec 7 19:35, Corinna Vinschen

Re: Error reported dd'ing close of end of block device with skip

2005-12-08 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 12/8/2005 3:30 AM: > > Hey, cool idea! There's no definition of O_DIRECT in Cygwin so far, but > this sounds like a worthwhile extension, at least for disk and tape > devices, but maybe also for files. This won't be

Re: Error reported dd'ing close of end of block device with skip

2005-12-08 Thread Corinna Vinschen
On Dec 7 19:35, Corinna Vinschen wrote: > On Dec 7 11:55, Loh, Joe wrote: > > QUESTION: > > > > Is there a way in Cygwin to do a read of a block device using "C" that > > does not do a read-ahead? We needed to develop an application that will > > issue the exact transfer size to the target de

Re: Error reported dd'ing close of end of block device with skip

2005-12-08 Thread Corinna Vinschen
On Dec 7 16:47, Loh, Joe wrote: > Thank you ... This will work. Any plans on supporting O_DIRECT flag in > open()? We believe this effectively gives unbuffered I/O. Please > correct if we are making the wrong assumption. Hey, cool idea! There's no definition of O_DIRECT in Cygwin so far, but t

RE: Error reported dd'ing close of end of block device with skip

2005-12-07 Thread Loh, Joe
>> On Dec 7 11:55, Loh, Joe wrote: >> QUESTION: >> >> Is there a way in Cygwin to do a read of a block device using "C" that >> does not do a read-ahead? We needed to develop an application that >> will issue the exact transfer size to the target device as requested. >> Looking at the strace

Re: Error reported dd'ing close of end of block device with skip

2005-12-07 Thread Corinna Vinschen
On Dec 7 11:55, Loh, Joe wrote: > QUESTION: > > Is there a way in Cygwin to do a read of a block device using "C" that > does not do a read-ahead? We needed to develop an application that will > issue the exact transfer size to the target device as requested. > Looking at the strace, it appear

RE: Error reported dd'ing close of end of block device with skip

2005-12-07 Thread Loh, Joe
> Searching the archive > > http://cygwin.com/cgi-bin/htsearch?config=htdig&words=dd+eom > > reveals a thread "Bug in dd ?? at EOM" which starts here: > > http://sourceware.org/ml/cygwin/2005-09/msg00878.html > > Btw, have you tried the latest snapshot from http://cygwin.com/snapshots/ ? > > > C

Re: Error reported dd'ing close of end of block device with skip

2005-12-07 Thread Corinna Vinschen
On Dec 6 15:56, Loh, Joe wrote: > Hello Folks, > Here's the second part of the problem. The follow on from a previous > issue observed as reported in "Size difference reported by > /proc/partitions and lseek(SEEK_END) on block device." Searching the archive http://cygwin.com/cgi-bin/htsearch