Filesystem Driver Panic

[Matt Cochran]

Here's an example:
I created a FAT partition on the system, and formatted
it to the same. I copied one set of files to it, and
restarted the machine.

I needed to change one of the files, but when I
removed the file I got:

Filesystem Panic (dev 5d:01)
fat_free: deleting beyond EOF
Filesystem has been set read-only

And then rm fails.

I have also noticed that the files copied to the
filesystem are often corrupted.

You're right, I was unable to reproduce this using
only /dev/nftla. Unfortunately, I can't get syslinux
to work without using partitions. Is there a way out
along this path, or do I need to take another
approach?

Matt




--- David Woodhouse <dwmw2 at infradead.org> wrote:
> 
> matthewcochran at yahoo.com said:
> > I've been developing a system using kernel 2.4.18
> and the MTD drivers
> > packaged with it on a system with a Millenium DOC.
> I've enabled
> > read-write support and can successfully read the
> test VFAT filesystem
> > on the DOC. However, after multiple writes,
> approximately 6, I get a
> > "filesystem panic" from the kernel, and the device
> is remounted
> > read-only.
> 
> Can you give more details? Can you reproduce by just
> reading from and 
> writing to the raw /dev/nftla device?
> 
> It's better to format with their DFORMAT program
> than nftl_format.
> 
> --
> dwmw2
> 
> 



__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com