Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Nov 1996 23:51:56 +0300 (MSK)
From:      =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) <ache@nagual.ru>
To:        toor@dyson.iquest.net (John S. Dyson)
Cc:        current@freebsd.org, dyson@freebsd.org
Subject:   Re: MSDOS lkm just broken (MAXBSIZE)
Message-ID:  <199611292051.XAA00689@nagual.ru>
In-Reply-To: <199611292005.PAA08993@dyson.iquest.net> from "John S. Dyson" at "Nov 29, 96 03:05:21 pm"

next in thread | previous in thread | raw e-mail | index | archive | help

> > 
> > panic: getblk: size(32768) > MAXBSIZE(16384)
> > 
> Excellent!!! Another disk (filesystem) saved...  This is only
> panicing under a very very evil situation.  It was never
> checked before.

Nothing saved, it simple not work and really work before!
No evil situation occurse, it was just usual boot stage mount as before.

It not work by very simple reason: MSDOS lkm awaits MAXBSIZE
as 32768 and compiled kernel define it as 16384 instead of 32768
because MSDOSFS NOT defined by kernel because I don't want MSDOSFS
inside kernel and want is as lkm instead.

I always have my MSDOS filesystem mounted and it work for me
for years without any data corruption in both filesystems, it not
work now.

Now I forced to define MSDOSFS in my kernel config file to
bypass your checking (and not use MSDOS lkm as result).

-- 
Andrey A. Chernov
<ache@nagual.ru>
http://www.nagual.ru/~ache/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611292051.XAA00689>