Bug 718910

Summary:	usb memory stick does not "safely remove" in one go
Product:	[Fedora] Fedora	Reporter:	Paul <pnewell0705>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	16	CC:	gansalmon, itamar, jmoskovc, jonathan, kernel-maint, madhu.chinakonda, pnewell0705
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-28 00:00:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Paul 2011-07-05 05:36:57 UTC

Description of problem:
I don't know where to put this regarding component, please change my feeble guess with the correct one

When I ask F14 to "safely remove" a memory stick that I have added / removed data on, it flashes a whole lot to apparently flush the write and then pops up a window of the contents. I then have to close that window and ask it again before it safely removes it ... indicated by the icon on the desktop disappearing.

If I ask it to "safely remove", I expect it to do its cleanup and unmount without my having to issue the request a second time

Thanks,
Paul

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


How reproducible:
Always

Steps to Reproduce:
1. Put a memory stick in
2. Add or remove to it (I can't tell if "a little" vs. "a lot" matters) and close all windows / terminals accessing it
3. Right click "safely remove" .. it cleans up and then pops up a window to it ... right click to "safely remove" again and the sticks flasher does a few blips and then the icon should disappear and the stick is really ready to safely remove
  
Actual results:
See "Steps"

Expected results:
Should be one "safely remove" to do the whole thing

Additional info:

Comment 1 Paul 2011-08-08 06:46:12 UTC

I've discovered that I am only seeing this on my x86-64 machine, not my older 32bit i{386,686} systems.

If I had some help, I might be able to figure out if it was a opSys or hardware issue.

The older machines are HP x4000, the 64bit is an Hp Pavilion DV6500

Thanks,
Paul

Comment 2 Fedora Admin XMLRPC Client 2011-09-12 13:40:33 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Paul 2011-10-18 06:44:13 UTC

I am seeing that this problem may be isolated to Patriot Memory Sticks. I used a Verbatim stick in the same x86_64 machine and didn't see this problem.

I haven't had the time to do a detailed analysis, but I did want to let you know that it may be an issue of a particular memory stick rather than a generic memory stick issue (or a generic F14 issue ...)

Paul

Comment 4 Lukáš Nykrýn 2011-10-18 07:29:41 UTC

I am quite sure that this has nothing to do with usbutils, maybe this can be a kernel issue.

Comment 5 Paul 2011-10-18 07:32:00 UTC

If there is anything I can do to help sort this out, please let me know

Thanks,
Paul

Comment 6 Dave Jones 2011-10-19 17:47:54 UTC

can you test the f15 / f16beta live-cd, and see if it still affects newer kernels?

due to f14 staying on 2.6.35 for its lifecycle, it's unlikely we'll find the relevant commit to backport if it's already fixed. But if it's still a problem on newer releases, we can look deeper at this.

Comment 7 Paul 2011-10-19 21:24:46 UTC

Dave:

I burned a live-cd of f15 and had all sorts of problems. When I was finally able to log in a live-user, I couldn't get the computer to acknowledge the memory stick (nothing on the display and no light flashing on the stick). I couldn't even get a terminal to open.

I'm not prepared to spend the time sorting out why I am having problems with the live-cd (I also had troubles with a live-usb for one of my 32bit systems), but am prepared to get you the info that you need for this bug.

I've avoided f15 and been crossing my fingers that f16 is something that I like (or at least, if gnome3 proves not to my liking, f16 is a release that I can move to with xfce, lxde, and/or other spin).

I will be bringing one of my machine up on f16 once it goes gold and hopefully something after that I will be able to bring the x86_64 box onto f16. I will assume the responsibility to run the tests at that time so I can update this bug.

One of the things I noted is that I do not see the problem on the 32bit systems so I can only test of 64bit and I don't want to do that until I've test-driven f16 with various spins.

Thanks for bearing with,
Paul

Comment 8 Dave Jones 2011-10-21 16:25:35 UTC

oh well, thanks for trying.  Let us know how 16 works out for you.
(I'll move this bug there, as it's realistically not going to get fixed in 14 before it reaches EOL).

Comment 9 Josh Boyer 2012-02-28 00:00:39 UTC

There have been a number of issues resolved around USB drive removal resolved with newer kernels.  If you can recreate your problem on 3.2.7 or newer, please open a new bug with relevant details.