Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10385 - After hal upgrade 0.5.9 -> 0.5.11rc2 auto-unmount don't work in XFCE

Attached to Project: Arch Linux
Opened by Artyom (urandom) - Saturday, 10 May 2008, 22:44 GMT
Last edited by Jan de Groot (JGC) - Thursday, 16 April 2009, 20:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

After manual device ejection this device must be unmounted and mount point must be deleted (if this device was auto-mounted by exo), but after upgrading this feature was broken.

Also this messages appear after manual ejection in syslog (with hal-0.5.11rc2):

after ejecting device with fat32:

FAT: Directory bread(block 3841) failed
FAT: Directory bread(block 3842) failed
FAT: Directory bread(block 3843) failed
...

or similar for ext3:

EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
EXT3-fs error (device sdd1): ext3_find_entry: reading directory #2 offset 0
...

This may be upstream bug in exo or hal.
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 16 April 2009, 20:59 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Monday, 12 May 2008, 00:15 GMT
Just pulling USB sticks without unmounting isn't something you should do anyways. These messages in dmesg are from the kernel that is trying to read a filesystem that no longer exists on your system.
Comment by Artyom (urandom) - Saturday, 17 May 2008, 16:39 GMT
This is really bug, try to do this on Ubuntu for examle. Don't close tickets before you totally understand it.
Comment by Artyom (urandom) - Saturday, 17 May 2008, 16:46 GMT
2 JGC. If I want to pull my usb-flash without unmouting, I must to be able it. May be all writings was synchronised (mount -o sync).
Comment by Artyom (urandom) - Saturday, 17 May 2008, 18:54 GMT
I try to do this on just-installed system, and all work perfectly... If nobody confirm this bug, issue can be closed.
Comment by Artyom (urandom) - Thursday, 19 June 2008, 21:55 GMT
Sorry for 4x requesting, this is flyspray failure when page refreshed after form posting. You don't understand me, this problem still exists, I observe it on my work machine and eeepc, also I found this issue in mandriva's and suse's bugtracker. Patch, which repairs lazy unmouting of devices which was physically removed from system, already exists.
Comment by Aaron Griffin (phrakture) - Thursday, 19 June 2008, 21:55 GMT
For the love of god, stop abusing the "reopen this task" button. I've reopened it, but don't let that happen again.
Comment by Aaron Griffin (phrakture) - Thursday, 19 June 2008, 21:57 GMT
Hah dolby, we both did this at the same time! Damned flyspray
Comment by Greg (dolby) - Thursday, 19 June 2008, 21:58 GMT
Damn i just denied reopening. And then while refreshing the page i saw reopened wtf.
Anyway if it is a bug then its an upstream one.
Please make a report upstream.
Edit also you are reffering to a patch. I dont see a link. Nor links to the mandriva and suse bugtracker
Comment by Artyom (urandom) - Thursday, 19 June 2008, 22:05 GMT
Sorry for my importunity, so I'll try talk with hal developers for adding this patch in upstream. Anyway look at this path, here added only 2 lines of code.
   hal-fix-linux_remove_childs.d... (1.1 KiB)
Comment by Gavin Bisesi (Daenyth) - Thursday, 11 December 2008, 18:30 GMT
Status?
Comment by Artyom (urandom) - Thursday, 11 December 2008, 20:38 GMT
Fix not in upstream. HAL still need patching.
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 13 April 2009, 23:29 GMT
status with new HAL 0.5.12git20090406.46dc48-1 ?
Comment by Artyom (urandom) - Thursday, 16 April 2009, 17:48 GMT
All good now. Patch included in upstream.

Loading...