This I feel needed a separate thread because it is a different issue than the thread I started called Cannot create hard drive icons. I got a 19G partition that I am trying to access. The file system is reiser. I can mount it and umount it from the command line just fine but it is when I try and do it through either KDE or GNOME that I run into issues. I created the desktop icon for the drive and click on it. It mounts successfully and I am able to carry out read/write operations to the disk. But I close the konqueror window and try to umount it by right clicking on the icon and choosing unmount, I get the error that the drive cannot umount because it is still busy. Well looking at the processes, I see that konqueror did not completely die. I kill it and then I am able to umount successfully. Now in Gnome, I right click on the desktop and choose in the disk menu the drive that I want to mount, it mounts and I see the icon on the desktop. But if I immediately try to umount it or even after working with the drive try and umount it, Gnome freezes up completely! Hard! I needed to do a reboot in order to gain access to my machine. Can anyone give me any clues on why this is? I would appreciate it! Ok here is the 2 variations I tried in the fstab file and both have the same outcomes. Original one I put in: /dev/hdb2 /mydata reiserfs user,noauto,acl,user_xattr 0 0 One that I have now: /dev/hdb2 /mydata reiserfs user,noauto 0 0 Thanks! Marshall
On Tue, 2004-05-11 at 06:39, Marshall Heartley wrote:
This I feel needed a separate thread because it is a different issue than the thread I started called Cannot create hard drive icons.
I got a 19G partition that I am trying to access. The file system is reiser. I can mount it and umount it from the command line just fine but it is when I try and do it through either KDE or GNOME that I run into issues.
I created the desktop icon for the drive and click on it. It mounts successfully and I am able to carry out read/write operations to the disk. But I close the konqueror window and try to umount it by right clicking on the icon and choosing unmount, I get the error that the drive cannot umount because it is still busy. Well looking at the processes, I see that konqueror did not completely die. I kill it and then I am able to umount successfully.
Another thing I have been doing lately is going to a different dir outside of the mount point before closing konquerer and don't seem to have problems anymore. -- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)
<snip>
Another thing I have been doing lately is going to a different dir outside of the mount point before closing konquerer and don't seem to have problems anymore.
OK I will try that. I think that my issue has something to do with the filemanagers that KDE and Gnome uses. I think that Anders stated that Nautilus draws the Gnome desktop. So if that is the case, it might be the file managers that are having the issues. Anyone else seen this? I guess that I can try and tell nautilus not to draw the desktop and see if I can get Gnome to behave, Thanks for the suggestion! Marshall
<snip>
Another thing I have been doing lately is going to a different dir outside of the mount point before closing konquerer and don't seem to have problems anymore.
Just tried it with KDE and unfortunately, it doesn't seem to help :( Thanks anyway for the suggestion. For some reason, konqueror in this instance does not want to die and therefore makes it not possible to umount the drive. This may also be the case with Nautilus. I am not sure. Marshall
Well I think that I solved the KDE side of the mount weirdness. I had to tell KDE not to preload a instance of konqueror. If this preloaded instance was still running, it would not allow me to umount the volume until it was killed. Now does Nautilus have anything like that? Gnome still wants to lock up each time I umount a disk in it. I think that Nautilus is at fault here. Any pointers would be great. Thanks, Marshall
participants (2)
-
Kenneth Schneider
-
Marshall Heartley