Re: [Jfs-discussion] File system object DF12704 has invalid descriptor (C)

[Dave K. <sh...@li...>]

On Wed, 2007-05-09 at 23:22 +0200, Marcel Lanz wrote:
> Hi
> 
> This afternoon my box lost power and a volume group with two USB
> drives chained together went down with it. On the VG one big JFS
> Partition (around 500GB) was installed.
> 
> After a fsck.jfs I was not able to mount the partition again. I get
> the following messages using the verbose switch.
> 
> Can anyone help me a bit to interpret the following lines ? I don't
> see any device (sd<x>) related errors in the kernel log, so I hope to
> fix those errors somehow ?

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?

> Thanks and regards, Marcel
> 
> defiant:~# jfs_fsck /dev/external_vg/data_01  -v
> jfs_fsck version 1.1.11, 05-Jun-2006
> processing started: 5/9/2007 23.9.26
> Using default parameter: -p
> The current device is:  /dev/external_vg/data_01
> Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
> Primary superblock is valid.
> The type of file system for the device is JFS.
> Block size in bytes:  4096
> Filesystem size in blocks:  127927296
> **Phase 0 - Replay Journal Log
> LOGREDO:  Log already redone!
> logredo returned rc = 0
> **Phase 1 - Check Blocks, Files/Directories, and  Directory Entries
> File system object DF12704 has invalid descriptor (C).
> File system object DF12768 has invalid descriptor (C).
> File system object DF12800 has invalid descriptor (C).
> File system object DF16448 has corrupt data (18).
> File system object DF16465 has invalid descriptor (C).
> File system object DF16476 has invalid descriptor (C).
> File system object DF16480 has invalid descriptor (C).
> File system object DF16490 has corrupt data (9).
> File system object DF16530 has invalid descriptor (C).
> File system object DF16538 has invalid descriptor (C).
> File system object DF16544 has corrupt data (16).
> File system object DF16563 has invalid descriptor (C).
> Extended attributes for file set object FF16568 have an invalid format.
> File system object DF16572 has invalid descriptor (C).
> Invalid data (45) detected in file system object DF16608.
> File system object DF16608 has corrupt data (18).
> File system object DF16625 has invalid descriptor (C).
> File system object DF16626 has invalid descriptor (C).
> File system object DF16636 has invalid descriptor (C).
> File system object DF16800 has invalid descriptor (C).
> File system object DF20640 has invalid descriptor (C).
> File system object DF40992 has invalid descriptor (C).
> Invalid data (45) detected in file system object DF41024.
> File system object DF41024 has corrupt data (40).
> Invalid data (45) detected in file system object DF41088.
> File system object DF41088 has corrupt data (19).
> File system object DF41184 has invalid descriptor (C).
> File system object DF41216 has invalid descriptor (C).
> Invalid data (45) detected in file system object DF41280.
> File system object DF41280 has corrupt data (16).
> Invalid data (45) detected in file system object DF45344.
> Directory inode F45344 has a node with an invalid freelist.
> processing terminated:  5/9/2007 23:09:31  with return code: 16711680
> exit code: 8.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center