Bug 29121

Summary:	msdos fs causes kernel panic when writing
Product:	Base System	Reporter:	Charlie Root <root>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.3-RELEASE
Hardware:	Any
OS:	Any

Description Charlie Root 2001-07-21 18:20:00 UTC

	
	When trying to write on a msdos partition, I get a kind of
kernel panic forcing a sync/reboot.

Fix: 

No idea...
How-To-Repeat: 	

	I don't know if it's related to a hardware problem, but that
partition was on a Maxtor 40GB ATA-100 HDD. I'm using an Asus A7V
motherboard with Promise ata-100 chipset for this hard drive.

Heh by the way, sometimes I can see my cpu usage and sometimes no...
without touching anything on the kernel...

Comment 1 jyliu 2001-08-02 13:29:21 UTC

Please refer to PR i386/28536. Seems this problem is related to large fat32 partitions. Running chkdsk in Windows would probably help, even if it says your partition is not corrupted.

Jiangyi Liu

Comment 2 Craig Reyenga 2002-01-16 02:10:23 UTC

I noticed that this happens on an msdos fs with any kind of error. The fix
is,
of course, to either run Scandisk or fsck_msdosfs. There should be more
'tolerance' for errors, though.

Comment 3 Jens Schweikhardt freebsd_committer

2002-08-09 20:49:54 UTC

State Changed
From-To: open->feedback

What exactly are the commands you use? Please give an easy to reproduce 
case, preferably with an msdosfs on a floppy. What is "a kind of kernel 
panic"? Please specify the exact panic string. Better yet, read the FAQ 
on how to supply a kernel stack trace. 

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING

Comment 4 Jens Schweikhardt freebsd_committer

2002-08-14 21:35:18 UTC

State Changed
From-To: feedback->closed

Feedback request bounced. If still an issue, let us know.

Comment 5 Christopher Brian Jack 2002-10-08 22:31:12 UTC

HOW TO REPEAT:

on my system with a maxtor 20G drive the following causes the system to freeze 
within 1-5 attempts (seems to act like russian roulette):

$ cp /usr/large.file.several.mbytes /dosd

where /dosd has a fstab entry like:
/dev/ad1s1              /dosd           msdos   rw              0       0

upon reboot inspection of the copied file on /dosd reveals it up to be 
incomplete, and sometime the copied file doesn't even get to be created 
before the system froze

Note: that was release 4.52 - I have moved to 4.6-RELEASE #0 recently and 
don't know if any filesystem code has been updated between 4.52/4.6 I haven't 
repeated the problem lately but that's probably becuase I've stopped writing 
anything to msdos partitions.