unmount failed
 

hi all,
I have fc3 2.6.9-1.667 with two disk drives in a master slave configuration. I have mounted partisions of drive follwed by the following entries in the /etc/fstab file.
/dev/hdb1 /mnt/driveF auto defaults 0 0
/dev/hdb3 /mnt/driveG ext3 defaults 1 2


Disk /dev/hda: 40.0 GB, 40020664320 bytes
255 heads, 63 sectors/track, 4865 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

"The following is the output of fdisk -l"

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2550 20482843+ 7 HPFS/NTFS
/dev/hda2 2551 4865 18595237+ f W95 Ext'd (LBA)
/dev/hda5 2551 4080 12289693+ b W95 FAT32
/dev/hda6 4081 4093 104391 83 Linux
/dev/hda7 4094 4158 522081 82 Linux swap
/dev/hda8 4159 4865 5678946 83 Linux

Disk /dev/hdb: 40.0 GB, 40060403712 bytes
16 heads, 63 sectors/track, 77622 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hdb1 1 20318 10240240+ c W95 FAT32 (LBA)
/dev/hdb2 20319 36984 8399664 7 HPFS/NTFS
/dev/hdb3 36985 57301 10239768 c W95 FAT32 (LBA)
/dev/hdb4 57302 77618 10239768 c W95 FAT32 (LBA)


The problem is that when I turn off PC following messege pops on

"umount failed device busy "
Even though I have closed all the files that I had openend from that drive.
However when I first do

"umount -l " for the drive and then shutdown I do not get the "FAIL" message.

Can any one help me figure out the glitch in it.

TIA

regards
tan...

Try installing lsof and running it on mountpoint of the drive.
It will show you.

hi,
As you told about "lsof", the package was already installed. I used this command and I was able to see the list of opened files.
Then probably closing the file may remove the error.

Actually I wanted to know "why is it happeneing that even after closing an openned file (say a pdf doc), I get device busy error!", because earlier I was using rh9 2.4 kernel, and I never faced this problem.
So is it because of any missing configuration or setting ?

TIA
regards
tan...

Say a pdf doc... Can you actually tell: I open the file in format 'xyz' with application buggyFataMorgana version 2.71828 and upon apprently closing application file stays open according to lsof? Also mention if "ps auxwww | grep 'buggyFataMorgana' " thinks process is still in memory.

And did you manage to close file and cleanly unmount disk? If yes, how?

See as I have mentioned in the first post itself
umount -l
does not give such error
So can u tell what exactly does this "-l" option doing

TIA

regards
tan...

-l means 'lazy umount' : file system is inaccessible for new open's, but all old opened file are still valid and if they are all closed at some moment, filesystem is finally unmounted.

And by cleanly unmounting I meant without '-l'. What are open files?

Are you shutting down the system gracefully, or just hitting the power button to kill it?

From a GUI (Gnome, KDE, etc.) there should be a menu choice of "Log Off" and one it's subitems should be "Shutdown Computer" (or something similar).

From a terminal window, login as root and run "shutdown" or "telinit 0" to shut down cleanly.

Ctrl-Alt-Del and/or the power button can sometimes be configured for clean shutdown as well, but the point is, they have to be configured (AFAIK). Maybe yours is not, or not correctly. I do not shutdown this way myself so I cannot tell you specifically how to configure things. Probably something in the BIOS and also in the OS needs to be set.

Looks like correct shutdown - auto-umount occurs.

yes I am using that only for shutdown, and if I am not wrong the "auto umount" should run automatically and kill the process using the mounted drive. Because I have been doing so with my earlier linux version rh9
But since having FC3 I am having this problem so I was thinking that there is some configuration missing that is needed to be done.

TIA
regards
Tan...

I'm wondering if you might have something started up in your multiuser init scripts (e.g., /etc/rc2.d/S20Program, /etc/rc5.d/S20Progam) but don't have a matching kill script (e.g., /etc/rc0.d/K20Program, /etc/rc6.d/K20Program). Thus "Program" is left running when you try to shutdown or reboot, holding a filesystem open when your shutdown/reboot attempts to unmount it.

Just a guess.

a) Why are you still using FC3 when FC5 is available?

b) I notice that all of us who have answered do not list RH, RHEL, or FC amongst our distros, perhaps you should have posted this in an RH/FC forum.

c) Are there any FC/RH folks there that can say if this is a known bug/feature of FC3?