Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!worldnet.att.net!news.mathworks.com!mvb.saic.com!news.cerf.net!news1.ni.net!maleficent.ni.net!stevek
From: Steven Kehlet <stevek@maleficent.ni.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 2.2-RELEASE, can't umount MFS fs
Date: Thu, 20 Mar 1997 22:52:28 -0800
Organization: Network Intensive
Lines: 79
Message-ID: <Pine.NEB.3.95.970320221349.251A-100000@maleficent.ni.net>
Reply-To: Steven Kehlet <stevek@maleficent.ni.net>
NNTP-Posting-Host: maleficent.ni.net
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37577
Hello fellow FreeBSD users,
I've used MFS for a while now with FreeBSD, but since my upgrade to 2.2
something is wrong: the kernel panics every time I try to reboot. I have
narrowed it down to the MFS partitions, because if I do not mount any, the
problem goes away. I am hoping someone else (more knowledgable than I) might
be able to interpret the following detailed transcripts:
If I execute "halt", it hangs for a while, then panics (copied by hand):
... system halted by stevek ...
... syslog dies ...
syncing disks... done
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervior read, page not present
instruction pointer = 0x8:0x0
stack pointer = 0x10:0xefbffe58
frame pointer = 0x10:0xefbffe60
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL=0
current process = 383 (halt)
interrupt mask =
panic: page fault
Odd, it says it's syncing the disks, but when I reboot it has to fsck
everything.
If I do a "shutdown now" to go to single user mode, it doesn't panic, but
complains that "some processes would not die; check ps -alx". Now this
is interesting. Here is "ps -alx" after I do a shutdown now:
# ps -alx
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 0 0 0 -18 0 0 0 sched DLs ?? 0:00.01 (swapper)
0 1 0 0 10 0 460 264 wait Is ?? 0:00.02 /sbin/init -
0 2 0 0 -18 0 0 12 psleep DL ?? 0:00.00 (pagedaemon
0 3 0 0 28 0 0 12 psleep DL ?? 0:00.00 (vmdaemon)
0 4 0 0 28 0 0 12 update DL ?? 0:00.10 (update)
0 237 1 0 10 0 82396 3144 mfsidl Is ?? 0:00.11 mfs /dev/wd1
0 329 1 1 10 0 500 368 wait Ss con 0:00.11 -sh (sh)
0 375 329 1 28 0 628 264 - R+ con 0:00.00 ps -alx
If I try to unmount the above MFS fs, or kill the process:
# umount /var/tmp
umount: /var/tmp: Device busy
# kill 237
# kill -9 237
# kill -9 237
#
I don't know what could be making that file system busy.
I know with my 2.1.5 system I can unmount an MFS fs at any time (script not
included), but not so with the 2.2 system (script not included: "Device busy"
error again). For now, I just don't mount my MFS partitions and everything
works just fine (no panic), but I really do like them! ;-)
Thanks for any input you may have. If there is useful information I haven't
collected, please let me know and I'll get it.
Steve Kehlet
--
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
mQCNAzMWcboAAAEEAOmKSE2pwQ8jtlgWyDsx0YHrSuqB6/mNBYsIf6V66P1F/MCL
J73zPfCntL8oHgXwSnIcULlmo7yPSQYAsELTE/7+QPhZ9z70lqKH36dqOE1wEylS
UvxKybr87KC3Fss3cFjud5fEa2GScSoa/kwaVOeqFJTNsbWmHqp9teyaupklAAUR
tChTdGV2ZW4gVC4gS2VobGV0IDxzdGV2ZWtAYW50aWd1YS5uaS5uZXQ+
=sq+m
-----END PGP PUBLIC KEY BLOCK-----