Hi all,
I have a problem where fam is hanging on to a disk partition and
won't let it go so I can unmount it. I'm seeking a way to make
fam "forget" that it needs to monitor this disk.
I'm running the fam that ships with RedHat 7.3 (fam-2.6.7-6); I
have a 7.2 system that has been upgraded to 7.3. I have this
service configured through xinetd.
If I boot the machine, log in, and mount a particular vfat drive,
I cannot unmount it (device busy, and something else about an
illegal seek). Fuser identifies fam as the culprit, and sure
enough a fam process is running. If I restart xinetd (using the
init script in /etc/initd), the fam process is killed and does
not restart and I can mount and unmount the drive at will. But
the next time I boot the machine, I have this bad behavior again,
unless I again restart xinetd.
The problem arose from a complicated series of missteps on my
part. It involved having the automounter autofs set up to mount
the drive on the same mount point as if I issued a regular mount
command. I did issue such a command and it looks like someone
got confused and the disk looked like it was mounted twice in
/etc/mtab. I deleted the extra lines from /etc/mtab and could
unmount the drive, but now I have this problem with fam.
I realize this is very sketchy and you may well need more
specific info to help. I tried to keep the initial message short
rather than fill it with irrelevancies. I'm new at this and
still learning alot. I appreciate any suggestions I can get.
I've tried reinstalling the fam and xinetd packages (as well as
nautilus and kde2-compat that depend on fam). I am at a loss as
to how fam is remembering to monitor the drive at boot and why it
forgets to do so after restarting xinetd.
Thanks,
Rob
|