Bug 838237
Summary: | ejecting usb drive can corrupt filesystem even when disk utility says "no media" after sync terminates and Gnome doesn't always notify about the sync process. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | matmenu8 |
Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | dennis, maxamillion, otaylor, samkraju, walters |
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: | 2013-08-01 06:48:31 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: | |
Embargoed: |
Description
matmenu8
2012-07-07 17:29:54 UTC
usb drives have both a DDR Memory buffer. Maybe powering the drive off to quick doesn't let the drive sync internally (data's already in the "on drive DDR buffer" but not in flash memory). I'm not sure of that as a friend had the problem with several usb hard drives with different filesystem (ext3, ntfs). Anyway, that should be 100% reliable. I use Windows sever 2003 too since 2004 until today and i never had such a problem. I'm using USB 2 ports. clicking "safely removal of usb drive xxx" in Windows, doesn't power the usbdrive off (LED always on). So maybe some hardware need to be synced but not completely shut down to ensure all datas are fully written and not only in hardware buffer. Can't the drive return a signal to say that everything is safe ? happened today again, please fix it fast, data corruption/loss id all but not funny. again today, but without data loss or corruption noticeable. But whatever usb drive was inserted after that, it would be opened read-only. I had to restart the computer to get the other usb drives in write mode. The "corrupted" drive kept to be mounted read-only. Only after a checkdisk on windows was it again possible to get read-write mode on it under linux. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |