From owner-freebsd-fs Thu Apr 18 9:49:20 2002 Delivered-To: freebsd-fs@freebsd.org Received: from thallium.ikuu.org (b77002.upc-b.chello.nl [212.83.77.2]) by hub.freebsd.org (Postfix) with SMTP id BB83A37B405 for ; Thu, 18 Apr 2002 09:49:10 -0700 (PDT) Received: (qmail 54013 invoked from network); 18 Apr 2002 16:59:45 -0000 Received: from unknown (HELO aurum) (10.0.0.4) by thallium.ikuu.org with SMTP; 18 Apr 2002 16:59:45 -0000 Message-ID: <001501c1e6f9$3e79f630$0400000a@aurum> From: "Rink Springer" To: , Subject: [FOLLOWUP] Bugs in FAT code Date: Thu, 18 Apr 2002 18:51:11 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi once again, I just did some messing around myself, and gdb reveiled that pmp->pm_inusemap is in fact NULL... this would explain the panic. This is a bug all right, but it seems the FAT32 volume itself isn't that fine either. fsck_msdosfs chokes on it: -- ** /dev/ad6s1 backup doesn't compare to primary bootblock -- It does this for my other drives too, though... --Rink To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message