On Tue, 2004-12-07 at 23:59 -0800, Sang Nguyen Van wrote:
> processing terminated: 12/8/2004 8:49:47 with return
> code: 10052 exit code: 8. [xchkdsk.c:472]
Here is a patch that should get you by this specific error, but I'm not
sure how much further you'll get. This is a failure to read an inode
that isn't used. fsck shouldn't give up here. But with both the
journal superblock corrupt, and fsck unable to read this inode, I have a
suspicion that fsck won't get a whole lot farther.
If you can't get fsck to finish, you may try to mount the partition
read-only (mount -oro). If that succeeds, you may be able to recover
> About the syslog, before we installed the new SuSe
> 9.2, my administrator checked the system and said
> there was an error message like the system is trying
> to write to the area out of the hardisk space (?!).
> I have a question: the problem comes from my old SuSe
> 7.3 (old kernel), and so the jfs handler or something
> else? Eventhough there may not be much hope for
> recovering the partition, I just don't want it to
> occur again!
I'm not sure what happened, but jfs is much more stable in SuSe 9.2 than
> Sang Nguyen.
IBM Linux Technology Center