Disappearing directory/mount and Crash on umount since 5.3

[Vince Hoffman]

On Wed, 24 Nov 2004, Kris Kennaway wrote:

> On Wed, Nov 24, 2004 at 11:29:26AM +0000, Vince Hoffman wrote:
>> I'm having a reoccuring problem with one of my mounts,
>> I have a disk i mount at /usr/scratch which is also exported via samba.
>> since upgrading to 5.3 after a little while (sorry no exact timings
>> yet,) an "ls /usr/scratch" gives "ls: /usr/scratch: Bad file descriptor"
>>
>> root at lobster
>> (11:19:06 </usr>) 0 # mount
>> /dev/ad0s1a on / (ufs, local)
>> devfs on /dev (devfs, local)
>> /dev/ad0s1e on /tmp (ufs, local, soft-updates)
>> /dev/ad0s1f on /usr (ufs, local, soft-updates)
>> /dev/ad0s1d on /var (ufs, local, soft-updates)
>> /dev/ad2s1c on /usr/scratch (ufs, local, soft-updates)
>> /dev/ad3s1a on /big (ufs, local, soft-updates)
>> devfs on /var/named/dev (devfs, local)
>> root at lobster
>> (11:19:10 </usr>) 0 # ls
>> ls: scratch: Bad file descriptor
>> .snap/     bin/       home/      libdata/   obj/       share/
>> @LongLink  compat/    include/   libexec/   ports/     src/
>> X11R6/     games/     lib/       local/     sbin/      sup/
>> root at lobster
>>
>> trying to umount /usr/scratch will crash the machine, (will do it once
>> more this evening and write down the error that pops up.)
>
> Drop to single-user mode and run fsck -f /usr/scratch.  If it finds
> errors, repeat until it stops finding them.
>
> Kris
Seems to have fixed that problem, thanks Kris.
Looks like I may have to do a clean reinstall anyway though as I have had 
2 more hard crashes since then for no reason I can yet pin down,
the only semi useful log entry i have is:
Nov 25 18:15:01 lobster kernel: pid 60702 (hostname), uid 0: exited on 
signal 11
  (core dumped)
Nov 25 18:15:01 lobster kernel: pid 60718 (mailwrapper), uid 0: exited on 
signal
  11 (core dumped)
Think i'll try a clean install and see if thats more stable.
I guess the upgrade to 5.3 from 5.2.1 didnt go as well as I thought, which 
is a shame since my laptop upgraded from 5.2.1 to 5.3-current to 
5.3-stable with no issues.

Vince

>