[Buildroot] EXT2-fs error

[Johnny Beardsmore]

> I don't want to be/seem rude, but it seems you lack some really basic
> embedded Linux knowledge. May I suggest to order and read a book such
> as Building Embedded Linux Systems [1] ?
> 
> That would really help you understanding what is going on.
> 
> Also you are not explaining what you are trying to achieve *in the
> end*. It might be that generating an ext2 filesystem image is totally
> useless for what you're trying to do.

No offence taken.  Reading such a book several months ago would have been a very prudent move.  This is perhaps a bit late now, since in the next couple of weeks I hope to have finished this project.  Most of my previous embedded experience didn't involve an operating system (mostly c onto AVRs via AVRstudio).  I would like to thank everyone now for all the assistance I've recieved with this and the other problems I've encountered.

What I'm doing is using Buildroot to create an embedded OS for a small computing device (a pc-104).  I have some code which then runs on the device and acts as a data collection/analysis system.  Un-taring the rootfs.i486.tar.bz onto the flashdrive of the device using grub has worked for me (with the exception of the problem I'm experiencing), and the whole procedure has been built around this (most of this has been achieved by trial-and-error, and assistance from forums).  I'd really like to avoid changing things to use the ext2 image file if possible and continue using the .tar.bz file.  The problem is I keep loosing frequently accessed files, which is (I bilieve) due to me mounting a file system which hasn't been checked.  I get a warning about the fs on boot, and inode errors when I try to acces a file which has been struck.

I believe this is quite a simple problem to fix - I just can't figure this one out.  I believe I need (some how) to check the file system on either the build machine, and/or the target.  If it is done on the target I may need to do this periodically/on-boot (due to the high number of unclean shut-down the device is likely to experience).  Hopefully this is enough detail, but I'm pulling my hair out with this, so will willingly forward anything further which may assist.  Thanks again.
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100916/e800bb05/attachment-0002.html>