On Tue, 24 Feb 2009, Daniel Jarboe wrote:
> On Tue, Feb 24, 2009 at 12:56 AM, Eben King <eben01@verizon.net> wrote:
>
>> 'Splain this, please.
>>
>> eben@pc:~$ sudo umount /misc/scratch/
>> umount: /misc/scratch: device is busy
>> umount: /misc/scratch: device is busy
>>
>> eben@pc:~$ lsof -n | grep scratch
>> eben@pc:~$
>>
>> Why's it busy, then? This might explain why automount never lets it
>> umount. In particular:
>>
>> eben@pc:~$ sudo /etc/init.d/autofs stop
>> Stopping automounter:
>> Couldn't stop automount for /misc done.
>
> Does sudo lsof -n find it?
Well, I rebooted since yesterday and that seems to have taken care of the
"can't umount" problem, but I'm back to the original problem:
eben@pc:~$ sudo umount /misc/scratch ; sleep 2 ; mount | grep scratch
/dev/sda9 on /misc/scratch type ext3 (rw)
eben@pc:~$
This doesn't occur in single-user mode (runlevel 1) -- things that are
umounted there stay that way. This only happens with /misc/* (which
coincidentally is where automount runs); I don't know if it's some
interaction with autofs/automount (as those run just fine in s-u.m.), or
something else. I uninstalled the NFS kernel server, as I didn't need it
anymore, and fewer things installed -> fewer things to cause problems. (It
wasn't the culprit, BTW.)
I have a mind to start in runlevel 1 and run /etc/{rc1.d/K*,rc3.c/S*} one at
a time until it screws up. Any reason why I shouldn't?
-- -eben QebWenE01R@vTerYizUonI.nOetP royalty.mine.nu:81Unix is user-friendly; it's just picky about who it makes friends with. ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:59:10 EDT