From: strawks <strawks@yahoo.fr>
To: linux-kernel@vger.kernel.org
Subject: USB: lost page write but no error reported on closing raw device
Date: Fri, 23 Jan 2009 17:01:49 +0100 [thread overview]
Message-ID: <4979E9ED.2090402@yahoo.fr> (raw)
Hi all,
I was trying to copy my entire internal HDD to an USB HDD :
> dd if=/dev/hda of=/dev/sdb
dd finished without reporting errors but some blocks (around 102GB of
160) were not copied and I got in the syslog :
Jan 21 19:04:43 kernel: usb 4-2: reset high speed USB device using
ehci_hcd and address 4
Jan 21 19:04:43 kernel: sd 6:0:0:0: [sda] Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK,SUGGEST_OK
Jan 21 19:04:43 kernel: end_request: I/O error, dev sda, sector 272136241
Jan 21 19:04:43 kernel: Buffer I/O error on device sda4, logical block
104765468
I don't really know what caused the problem (btw I didn't disconnect the
USB drive) but the fact is that there were an error copying data to the
usb drive but this error were not reported to dd.
Is this the expected behaviour? Shouldn't the close() call repports the
write error to dd?
Note : I tried on debian 2.6.26 stock kernel and 2.6.29-rc2, same behavior.
I have already copied HDD this way (IDE and SCSI but not USB), and each
time IO errors occured dd would print some error message. I think
--
regards
strawks
reply other threads:[~2009-01-23 16:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4979E9ED.2090402@yahoo.fr \
--to=strawks@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox