Re: Cannot remove child "XXX", ino #13, because it doesn't exist

[Estelle HAMMACHE <estelle.hammache@st.com>]

Martin Egholm Nielsen wrote:
> 
> Hi again,
> 
> > After removing a directory containing a lot of files, I get lots of the
> > following messages on reboot (one for each of the files I removed):
> 
> > Cannot remove child "file10.txt", ino #13, because it doesn't exist

This might happen when the deletion dirent for the directory
is found, but the deletion dirent for the files are not found
(which should not happen during ordinary operation).
Exactly what command (or code) did you use to remove the file and
directory ? Did you umount correctly after that ?
Do you really get this message for each and every deleted file
or only part of them ?

> The problem arose after creating a directory in my JFFS2 NAND fs, and
> creating some 1000 (small) files in it. After rebooting I removed the
> entire directory, and at the next reboot I got the error.

This message is a notice. It should not prevent JFFS2 from running.
The directory and the files are considered as deleted.

Just out of curiosity, do you get these messages
"Eep. Child "fileXXXX" (ino #XXX) of dir ino #XX doesn't exist!"
previously to the "Cannot remove..." messages ?
If you don't, it might be interesting to get a trace with
debug enabled since the child inode cache should not disappear
between the build_inode_pass1 and remove_unlinked_inode.

Bye
Estelle