JFFS proc file system hierarchy

JFFS proc file system hierarchy

[Finn Håkansson]

Hi David,

I have added some code that lets us monitor a mounted JFFS file system
via the proc file system. As I wrote in the log message when I added
the two new files jffs_proc.h and jffs_proc.c to the MTD sources an hour
or so ago, the directory structure looks like this:

        jffs/
          3c:12/
            info
            layout

"jffs"   is the main directory for all JFFS partitions and is added to the
         proc file system when the JFFS initialization code is run.

"3c:12"  is the name of the mounted device. The name is simply generated by
         kdevname. This directory is added dynamically as well as its
         contents.

"info"   is a file with general information about the JFFS partition and
         could look like this:

         partition size:     00200000
         sector size:        00010000
         used size:          0000696C
         dirty size:         00000000
         free size:          001F9694
         garbage collecting: no

"layout" is a file that contains the current physical layout of the file
         system on-flash.


It should be rather easy to add new files as we need them.

Simon have written some programs that makes images of the information
gathered from the proc files. Programs like that are easy to make when
we have this new functionality.

I haven't compiled the MTD sources with these new changes but I am sure
there are some things one have to tweak in order to be able to compile
it.

Okay. Did I forgot anything?

/Finn



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

Re: JFFS proc file system hierarchy

[David Woodhouse]

finn@axis.com said:
> I have added some code that lets us monitor a mounted JFFS file system
> via the proc file system.

Excellent - I was wishing for something like this only yesterday ;)


finn@axis.com said:
>  I haven't compiled the MTD sources with these new changes but I am
> sure there are some things one have to tweak in order to be able to
> compile it.

Yeah - but it doesn't look like a lot is needed. I'll poke at it tomorrow.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org