Bug 755140 - Large amounts of disk I/O on a flash drive makes machine unresponsive
Summary: Large amounts of disk I/O on a flash drive makes machine unresponsive
Keywords:
Status: CLOSED DUPLICATE of bug 734516
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-19 00:43 UTC by Scott Baker
Modified: 2011-11-23 13:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-23 13:24:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Scott Baker 2011-11-19 00:43:01 UTC 
Description of problem:
When I tried zeroing out a USB Flash drive after a couple of minutes my machine became completely unresponsive. I could move the mouse, and the windows that were animated still moved, but KDE wouldn't accept any input (mouse/keyboard). After the disk I/O stopped the machine was responsive again.

Version-Release number of selected component (if applicable):
Completely up-to-date F16 install

How reproducible:
Easy

Steps to Reproduce:
1. Insert multi-gig USB Flash drive
2. dd if=/dev/zero of=/dev/sdX
  
Actual results:
Flash drive will begin to zero out, and after a minute or so the box will be completely unresponsive.

Expected results:
Box remains responsive and usable during the zero-out process

Additional info:
Also tried it with pv

pv /dev/zero | dd of=/dev/sdX
Comment 1 Scott Baker 2011-11-19 00:49:25 UTC 
I recently upgraded from F14, and did not have this problem.
Comment 2 Scott Baker 2011-11-19 00:51:37 UTC 
Looks like this might be a dupe of:

https://bugzilla.redhat.com/show_bug.cgi?id=734516
or
https://bugzilla.redhat.com/show_bug.cgi?id=721127
Comment 3 Chuck Ebbert 2011-11-23 13:24:10 UTC 

*** This bug has been marked as a duplicate of bug 734516 ***
Note You need to log in before you can comment on or make changes to this bug.