ext2_lookup() and i_count

[Alexander Larsson]

On Fri, 12 May 2000, Sébastien Côté wrote:

> Alexander Larsson a écrit :
> > 
> > On Thu, 11 May 2000, David Woodhouse wrote:
> > 
> > >
> > First create your to be filesystem in a directory (call it e.g. img_dir),
> > then run "mkfs.jffs img_dir > fs.jffs", this creates an image fs.jffs that
> > you can copy to your flash (in the case of an mtdram flash, just do "cat
> > fs.jffs > /dev/mtd0". Then mount the flash "mount -t jffs /dev/mtdblock0
> > /mnt/jffs".
> > 
> > Then just go to /mnt/jffs and play around with the filesystem. Not
> > everything works well right now, rename isn't implemented, and unlink
> > seems to have some problems.
> 
> I tried this out today and encoutered some problems.  Most file
> operations work well (cp, rm ln -s) but I have two problems.  

I have huge problems with rm (unlink). If i unlink a file i've recently
read i get a BUG() in clear_inode() in fs/inode.c. See my posting to
linux-kernel for more info.
Otherwise i haven't done much testing, I've mainly done separate testing
of each function as I've implemented them.
 
> First, big file don't get mounted on the filesystem (by big I mean a few
> hundred Ks).  I tried to track the problem without luck.  Second, the
> command df always reports dans the device is full.  Since
> jffs_scan_flash()'s reports are ok, I'm wondering where df takes the
> informations from?
> 
> Did you run into similar problems?

I haven't tried any big filesystems yet.
df probably uses jffs_statfs() (the statfs system call) to get its info.
I haven't tested this yet.

/ Alex




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