Help - Search - Members - Calendar
Full Version: Root Filesystem Corruption After Reboot
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
sommi
Hi!

I recently installed the pdaXrom kathrin rc9 on my Zaurus
SL-C750. The first reboot after the flashing finished without
any errors.

Today my Zaurus crashed with a garbled screen so I had
to reboot it. As I was still able to log in to the Zaurus via ssh,
I issued the "reboot" command.
The Zaurus seemed to reboot normally, but then I got
strange messages during startup:

CODE
...
Eep. Child "System.profile-K0I8-U" (ino #2832) of dir
ino #2820 doesn't exist
Inode #1771 was a directory with children -removing those too...
Inode #2799 was a directory with children -removing those too...
...


startx then complained about missing libraries and I noticed that
some symlinks disappeared.

Has anyone else gotten these error messages during reboot?
Or is this a sign that my internal flash is going to fail soon (not good)?
Or could this be a bug in the jffs2 driver?

Is there any way to avoid this corruption?

Thanks!
iamasmith
QUOTE(sommi @ Apr 7 2005, 06:52 PM)
...
CODE
...
Eep. Child "System.profile-K0I8-U" (ino #2832) of dir
ino #2820 doesn't exist
Inode #1771 was a directory with children -removing those too...
Inode #2799 was a directory with children -removing those too...
...


startx then complained about missing libraries and I noticed that
some symlinks disappeared.
...
*


OK, firstly I'm not stating absolutely that its not the case that there's a correlation between your missing libraries and the jffs2 errors but I will say that you get those messages in normal operation.

jffs2 will absolutely avoid writing to the flash at all costs if it can help it. This means zeroing data on the file system when it's already marked the file as delete in its journal.

The reason is quite simple. It's trying to extend the life of the flash device.

To recreate the errors if you don't believe this reflash your Z so that its completely clean, create a large directory structure with a lot of files and directories and then delete that structure. You will get a LOT of those messages. They are just messages and some people on the jffs2 news groups really complain that the file system is just too 'chatty' and alarms too many users into rebuilding their systems.

As far as the missing libraries go, I would reinstall them.

Andy
MarcusKracht
I noticed something similar. Xpdf does not work, so I used the trick that someone
pointed out: link the freetype-libraries to freetype.so.6.3.4 instead of freetype.so.6.3.7.
This works, but every now and then Xpdf crashes and I find that the libraries have
been relinked to freetype.so.6.3.7. Occasionally the system would also not find an
executable file after I have edited the path in /etc/system. Seems that this is a similar
type of problem.

-- Marcus
osteron
QUOTE(MarcusKracht @ Apr 7 2005, 08:26 PM)
This works, but every now and then Xpdf crashes and I find that the libraries have
been relinked to freetype.so.6.3.7.


I think this happens because ldconfig automatically links to the highest version when run.
sommi
QUOTE(iamasmith @ Apr 7 2005, 08:44 PM)
To recreate the errors if you don't believe this reflash your Z so that its completely clean, create a large directory structure with a lot of files and directories and then delete that structure. You will get a LOT of those messages. They are just messages and some people on the jffs2 news groups really complain that the file system is just too 'chatty' and alarms too many users into rebuilding their systems.

As far as the missing libraries go, I would reinstall them.


That's good to know. I am not familiar with the jffs2 filesystem, so I thought these
messages would indicate an inconsistent state or something like that...

So there must be another cause for my problems. I noticed that the libraries themselves
aren't missing, but that symlinks pointing to them were removed (most of my applications
are installed on an sd-card).

In any case, thanks for your answer!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.