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!
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!
FS#2959 - kernel -2.6.12.2 - System stuck while unmounting NTFS
Attached to Project:
Arch Linux
Opened by Omri Zohar (greycloack) - Thursday, 14 July 2005, 07:58 GMT
Last edited by Judd Vinet (judd) - Wednesday, 24 August 2005, 22:19 GMT
Opened by Omri Zohar (greycloack) - Thursday, 14 July 2005, 07:58 GMT
Last edited by Judd Vinet (judd) - Wednesday, 24 August 2005, 22:19 GMT
|
DetailsSome users have reported that their computers hang when gerring to the unmounting stage while shutting down or while unmounting NTFS partitions.
It seems the problem accured after upgrading to the latest stock kernel currently in the current repository. Post related to the subject with a patch that should solve it if inserted to the kernel : http://bbs.archlinux.org/viewtopic.php?t=13780&sid=5ef672e6c88e60247a7094c963e5224b |
This task depends upon
Comment by dtw (dibblethewrecker) -
Thursday, 21 July 2005, 15:01 GMT
I am having this problem outside of the stock kernel
Comment by Alexander Baldeck (kth5) -
Sunday, 24 July 2005, 16:00 GMT
may this be a problem with manually mounted nfs shares and manual portmapd start? also unavailable shares tend to umount very slow cause of a high timeout default.
Comment by Johannes Jordan (FoPref) -
Wednesday, 10 August 2005, 19:55 GMT
I have this problem on two different systems with NTFS partitions. They don't unmount, regardless wether they are in /etc/fstab and (u)mounted automatically, or this done manually.
Comment by Paul Seropian (paranoos) -
Wednesday, 28 September 2005, 08:45 GMT
This is a kernel bug that is fixed in 2.6.13, please close this :)