Re: 2.1.63 oops on umount

firewind (
Sun, 16 Nov 1997 12:08:01 -0800 (PST)

On Sun, 16 Nov 1997, Bill Hawes wrote:

> OK, I'm especially interested in msdos fs problems. I fixed a number of
> errors that would cause the "busy inodes" problem, but there may be
> other errors as well.

Like I said, I've had no 'busy inodes' problems in 2.1.6x... great work! :)

> Could you attempt to recreate the problem, and if possible umount the
> msdos partitions first (while syslog is still running) to try to capture
> any messages? The most helpful report would be a specific operation that
> causes an oops at umount time, e.g. "If I mount msdos, do xxx, and then
> umount, I get this oops ...".

Okay, I've reordered my halt scripts; killing syslogd is now the -last-
thing done. I'll keep my eyes peeled. I recall I 'rm -rf'd some large
directory trees on one of the msdos filesystems last night, so I'll try to
recreate it that way.

On a related (and somewhat off-topic) note, is there a fsck for msdos
filesystems available? I'd like to check if these driver problems are
causing any true corruption without having to reboot into (ick) msdos.