On Sat, 24 May 2003 06:50:55 +0200 Clayton Cornell wrote:

Ooops, wasn't clear on that one... yes, I close/exit Konq. completely. While I was trying to pin down what is going on, I've exited everything, and

checked running processes (top and ps) to see if something was left laying around. Also made sure I didn't have a terminal window open that was pointing to that drive etc. I cannot find anything obvious that is hanging onto the mountpoint and keeping it busy... umount -f should be able to force the unmounting. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

On Sat, 24 May 2003 15:22:39 +0200 Clayton Cornell wrote:

Yes, and so does umount -l (as I pointed out that I used, in the original email). Problem is, using the "force" or "lazy" options are a solution of sorts, but it does not solve the problem... only provides a messy workaround. I agree. Somewhere you have an active process that had CD'd to that filesystem. I had a similar issue with the DVD on SuSE 8.2 last night. I mounted it, but could not umount it without forcing. -- Jerry Feldman Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9

On Saturday 24 May 2003 10:11 am, Clayton Cornell wrote:

On Saturday 24 May 2003 15:50, Jerry Feldman wrote:

...

On Sat, 24 May 2003 15:22:39 +0200

...

Yes, and so does umount -l (as I pointed out that I used, in the original email). Problem is, using the "force" or "lazy" options are a solution of sorts, but it does not solve the problem... only provides a messy workaround.

I agree. Somewhere you have an active process that had CD'd to that filesystem. I had a similar issue with the DVD on SuSE 8.2 last night. I mounted it, but could not umount it without forcing.

So this is where it gets a bit interesting. No active processes (that I know of) are trying to read the FAT32 drive. I click the desktop icon, and this mounts the drive (a seperate physical drive from my Linux drive) and opens Konq showing the drive contents. If I immediately exit Konq, I cannot umount the drive. I haven't used any other application to access the drive, and I cannot find anything that is still running that is attached to that mount point.

If I open a terminal/konsole and mount the drive from the command line, and can copy files or whatever, and then umount the drive without any errors or problems. It all seems linked to whatever Konq is doing or leaving behind.

What's in your fstab? Sounds to me like the difference is coming from how the partition gets mounted. (and maybe who mounts it) Clicking on the icon would cause a user mount, and the mount would be based on the information in the fstab. Doing a manual mount: mount /dev/xxx /<mountpoint> would not use information in the fstab. But you haven't given enough information as to how you mounted the partition.

I have done some more digging and have come across an option in Konq that is the culprit. In the Konq settings, there is a performance option to always have at least one instance of Konq preloaded - makes it faster. If it is set to have at least one instance of Konq always open (default setting is 1) it will maintain that link to the drive I want to unmount.

So.. if anyone else is having this problem, set the preload to zero (0). It means Konq takes a half second longer to start up (well on my system anyway), but you are not annoyed with a drive that won't umount.

C.

-- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 05/24/03 11:03 + +----------------------------------------------------------------------------+ "Live a clean, healthy life and you will soon die of boredom."