From owner-freebsd-fs  Sun Oct 28  9:39:16 2001
Delivered-To: freebsd-fs@freebsd.org
Received: from bigglesworth.mail.be.easynet.net (bigglesworth.mail.be.easynet.net [212.100.160.67])
	by hub.freebsd.org (Postfix) with ESMTP
	id A330B37B401; Sun, 28 Oct 2001 09:39:12 -0800 (PST)
Received: from 212-100-182-16.adsl.easynet.be ([212.100.182.16] helo=belgacom.net)
	by bigglesworth.mail.be.easynet.net with esmtp (Exim 3.16 #1)
	id 15xttq-0006A2-00; Sun, 28 Oct 2001 18:39:06 +0100
Message-ID: <3BDC427E.710CE831@belgacom.net>
Date: Sun, 28 Oct 2001 18:38:06 +0100
From: Chris Pockele <chrisp@belgacom.net>
X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Kris Kennaway <kris@obsecurity.org>
Cc: freebsd-gnats-submit@FreeBSD.org, fs@FreeBSD.org
Subject: Re: misc/30168: 4-stable, crash when writing to msdos fs
References: <3B8CBCAB.97D88562@belgacom.net> <20010829031921.A69280@xor.obsecurity.org> <3B8CD565.A4A52CC6@belgacom.net> <20010829133603.C75228@xor.obsecurity.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-fs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-fs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-fs>
X-Loop: FreeBSD.org

> Thanks, that was what's needed.  Now to find an msdosfs guru to debug
> this :)
> 
> Kris
> 
Compiling msdosfs support as a module has solved the problem
for a long time (don't know why, but it didn't crash).
But after doing a cvsup + makeworld today,
it occured again (mounting & reading the msdos partition is ok,
panic when writing).
I searched the GNATS database and i found a few pr's that
seem to describe the same problem.
I applied the following patch from pr i386/28536, and it did
give me the error message (Next free cluster in FSInfo (%u)
exceeds maxcluster (%u)) when trying to mount the partition.

The scandisk programs from win98 and w2k don't report any
errors on the partitions, and Linux can write to them, too.

Should I recompile with unpatched sources and submit another
traceback?

Here's the patch:

/*
                * Check and validate (or perhaps invalidate?) the fsinfo
structure?            XXX
                */
       +     if (pmp->pm_fsinfo && pmp->pm_nxtfree > pmp->pm_maxcluster)
{
       +         printf ("
       +                pmp->pm_nxtfree, pmp->pm_maxcluster);
       +         error = EINVAL;
       +         goto error_exit;
       +     }
         
               /*
                * Allocate memory for the bitmap of allocated clusters,
and then


Here are the error messages (with patch applied):

Oct 28 18:33:35 freedaemon /kernel: Next free cluster in FSInfo
(4294967295) exceeds maxcluster (1148401)
Oct 28 18:33:49 freedaemon /kernel: Next free cluster in FSInfo
(4294967295) exceeds maxcluster (1467070)

(there are two msdos partitions which i tried to mount)
Maybe it's because the partitions are bigger than 2 or 8 GB?

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message