public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
* Filesystem Driver Panic
@ 2002-05-08  1:56 Matt Cochran
  2002-05-08  8:15 ` David Woodhouse
  0 siblings, 1 reply; 3+ messages in thread
From: Matt Cochran @ 2002-05-08  1:56 UTC (permalink / raw)
  To: linux-mtd; +Cc: David Woodhouse

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.

During the course of this, I've run nftl_format, tried
several filesystems, and repeated this on two systems
with identical hardware. Has anyone reported or
experienced the same kind of issues?


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Filesystem Driver Panic
  2002-05-08  1:56 Filesystem Driver Panic Matt Cochran
@ 2002-05-08  8:15 ` David Woodhouse
  2002-05-13  0:48   ` Matt Cochran
  0 siblings, 1 reply; 3+ messages in thread
From: David Woodhouse @ 2002-05-08  8:15 UTC (permalink / raw)
  To: Matt Cochran; +Cc: linux-mtd

matthewcochran@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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Filesystem Driver Panic
  2002-05-08  8:15 ` David Woodhouse
@ 2002-05-13  0:48   ` Matt Cochran
  0 siblings, 0 replies; 3+ messages in thread
From: Matt Cochran @ 2002-05-13  0:48 UTC (permalink / raw)
  To: David Woodhouse; +Cc: linux-mtd

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@infradead.org> wrote:
> 
> matthewcochran@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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-05-13  0:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-08  1:56 Filesystem Driver Panic Matt Cochran
2002-05-08  8:15 ` David Woodhouse
2002-05-13  0:48   ` Matt Cochran

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox