Bug 810997

Summary:	dd'ing a fedora live iso to USB fails
Product:	[Fedora] Fedora	Reporter:	patrick korsnick <korsnick>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	dennis, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	USB first=3.3
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-30 20:13:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description patrick korsnick 2012-04-09 20:09:58 UTC

Description of problem:
attempting to dd a fedora live iso image to USB stick fails:

dd if=/run/media/ppk/passport/all/iso/64/Fedora-16-x86_64-Live-XFCE.iso of=/dev/sdc bs=2M
312+1 records in
312+1 records out
655360000 bytes (655 MB) copied, 0.275111 s, 2.4 GB/s

this behavior has worked for me up until today when i did a yum update. i have tried 3 different USB sticks and tried from 2 different f17 installs (both yum updated, one f17 KDE and one f17 Gnome). in both installations i get the same very fast return of the command and high data transfer rate. bearing in mind that this is usb 2.0 the transfer rate alone is an indication that something is wrong. the contents of the usb stick are unchanged after running the command.

i have run this command thousands of times and never had any problem until today.

Version-Release number of selected component (if applicable):

17

How reproducible:

every time

Steps to Reproduce:
1. run above dd command
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Josh Boyer 2012-04-10 20:23:11 UTC

What was included in your update?  Can you attach your yum log that shows the updates from working->not working?

Also, please attach the dmesg output when booted into the system where this problem occurs.

Comment 2 Dave Jones 2012-06-28 02:16:22 UTC

Can you still repeat ths with the 3.4 Kernel ?

Comment 3 patrick korsnick 2012-06-30 20:12:37 UTC

I haven't seen this problem for some time. Now working fine just like before. Closing this bug as fixed.