Bug 806909
Summary: | F16: kernel 3.3.0-4.fc16.i686.PAE: Fails to umount SDCARD USB disk properly | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Terry Barnaby <terry1> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | awilliam, gansalmon, germano.massullo, itamar, jonathan, kernel-maint, kk_konrad, knight, madhu.chinakonda, twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-29 12:49:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Terry Barnaby
2012-03-26 13:29:52 UTC
I have similar problems with arbitrary USB memory sticks: (F16 x86_64, KDE desktop, kernel 3.2.10-3 and 3.3.0-4) In my setup I am using a luks (cryptsetup) partition formatted with ext4. after copying a big (~40MB) file and then unmount the umount command returns almost immediately and a sync command causes led activity of several seconds on the memory stick. After that I cannot luksClose the device any more (busy msg) and dmsetup table shows that it is still active. Pulling the USB stick genereates log activity like: usb 1-3: USB disconnect, device number 4 Aborting journal on device sdd1-8 JBD2: I/O error detected when updating journal superblock for sdd1-8 journal commit I/O error EXT4-fs error (device sdd1): ext4_journal_start_sb:327: Detected aborted journal EXT4-fs (sdd1): Remounting filesystem read-only Note that the fs has already been unmounted... However: trying the same in emergency.target or multi-user target does not trigger the same behavior - all seems normal: the umount command waits until the buffers are written to the mem stick and luksClose closes as expected. (tried several times with both kernels) So this might be caused by some recent user space changes. Kernel 3.3.0-4 has some problems with SATA hotplug (Intel ICH8 - the symptoms are similar). Hope the mess can be cleaned up soon. maybe related/duplicate? https://bugzilla.redhat.com/show_bug.cgi?id=747114 pls look at my comment about cups, BZ 747114 (disabling cups made the system behaving well again) back to cups-1.5.2-1 on F16 x86_64. (all later koji versions cause this bug) umount is OK again. see BZ 747114 for details Terry, can you let us know if cups is the problem for you too? If so, we can close this as a dupe. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Yes, just tried it. It the system is booted without starting the cups service then un-mounting USB disks is fine ! How on earth can this be ? Disk data storage is sacrosanct and the Linux kernel should ensure data safety ... I think something else (systemd ?) mounted the device too (I am unable to see it in findmnt output though), so your umount is not the last one which will sync the disk buffers. BZ 807672 seems also to be related. see my comment from today: if you stop cups then mount your USB disk then restart cups - stop cups again before umount then it should work OK (at least here it does with cups-1.5.2-8 from koji) wwoods was having lots of trouble with loop devices yesterday, that went away when he disabled cups. it seems clear that cups has screwed some kind of pooch seriously badly, here. let's dupe 'em all off. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 747114 *** *** This bug has been marked as a duplicate of bug 808109 *** |