> fsck.jfs shouldn't segfault, so you could try running it under gdb to
> determine where the segfault is coming from and I may be able to give
> you a patch that gets you further.
>
> Or, you could try running fsck with the -n flag (read-only)
> just to get
> an idea how corrupted the file system is. With the -n flag,
> fsck won't
> try to replay the journal, so you will avoid whatever problem you're
> currently seeing.
>
> If fsck -n doesn't report too many errors, you could run it with
> --omit_journal_replay, which will skip the journal replay, but still
> attempt to fix any errors.
>
> Third, you can try to mount the file system read-only (mount -oro) and
> recover whatever data you are able to access.
Ah, good suggestions! I tried the read-only check and got many
many screenfulls of "Duplicate reference" blah blah followed by:
Duplicate reference to 1 block(s) beginning at offset 116755104 found in
file system object MA16.
Inode A16 has references to cross linked blocks.
Duplicate reference to 1 block(s) beginning at offset 116757505 found in
file system object MA16.
Inode A16 has references to cross linked blocks.
File system object MA16 has a corrupt forward sibling chain.
Secondary metadata inode A16 is corrupt.
Errors detected in the Primary File/Directory Allocation Table.
Errors detected in the Secondary File/Directory Allocation Table.
CANNOT CONTINUE.
processing terminated: 6/20/2006 11:58:47 with return code: -10049
exit code: 4.
So, I'm guessing that's not good.
-poul
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
