>Most of those errors should be recoverable. Some of them are more
>severe and should result in a directory being lost and its contents put
>in lost+found. The worst problem is the termination message:
>> processing terminated: 5/9/2007 23:09:31 with return code: 16711680
>> exit code: 8.
>return code 16711680 isn't valid. In hex, it's 0xff0000. I suspect
>that a return code is being overwritten in memory. Probably some data
>structure containing an array on the stack is going outside its bounds.
>I'm looking at the code now, but I haven't found anything yet.
>Until I figure out how to fix jfs_fsck, you may be able to access the
>volume by mounting it read-only (if that is of any use to you). I'm not
>sure why you're seeing so much file system damage. Could the journal
>replay have failed on an earlier invocation of jfs_fsck?
yes, I can mount it read-only, this helps a lot since I tought to
loose all the data. A read-write mount didn't work so until your
suggestion I never tried to mount it RO. For a RW mount I get the
following:
defiant:/# mount /dev/external_vg/data_01 /mnt/
mount: wrong fs type, bad option, bad superblock on /dev/external_vg/data_01,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
