Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Bug in dd ?? at EOM Date: Mon, 26 Sep 2005 12:08:30 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <3308.130.240.136.220.1127731371.squirrel@pinus> Message-ID: ----Original Message---- >From: Bengt-Arne Fjellner >Sent: 26 September 2005 11:43 > When using dd with flags conv=noerror,sync > It tries reading after the disc ends. > > This line in cygwin tries reading past end of media: > dd if=/dev/sdd of=kkkkkk bs=512 skip=156280250 conv=noerror,sync > dd: reading `/dev/sdd': Input/Output error > 21120+0 records in > 21120+0 records out > 10813440 bytes (11 MB) copied, 1.151 seconds, 9.4 MB/s > dd: reading `/dev/sdd': Input/Output error > 21120+1 records in > 21121+0 records out > repeats "forever" > > Stops at end of disk. Whos wrong? There is very definitely a problem with cygwin vs. dd, which I'm investigating. I've seen the same thing with CF memory cards, and initially thought it was directly related to the memcard driver, but I was becoming convinced it's a generic problem with cygwin's readv, and since you've found it shows up on hard drives as well, that confirms it for me. I'll get round to it late tonight. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/