Fsck on 250Gb filesystem aborts (coredump)

Question

Hello,
I had a SVM raid1 on 2 250Gb hard drives.
Upon trying to restore from them, I may have compromised the integrity of the UFS.
My latest attempt consists in a one-way setup:
$> metadb -i
  flags   first blk block count
a m  pc luo      16    8192    /dev/dsk/c5d1s2
a    pc luo      16    8192    /dev/dsk/c1d1s2
$> metastat -i
gamma: Mirror
    Submirror 0: alpha
      State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 488327805 blocks (232 GB)
alpha: Submirror of gamma
    State: Okay
    Size: 488327805 blocks (232 GB)
    Stripe 0:
  Device   Start Block  Dbase        State Reloc Hot Spare
  c1d1s2      16065     Yes           Okay   Yes
Device Relocation Information:
Device   Reloc  Device ID
c1d1   Yes    id1,cmdk@AST3250410AS=____________9RY0BKEX
$> fstyp /dev/md/dsk/gamma
ufsHowever it would not mount:
$> mount -F ufs /dev/md/dsk/gamma /back
mount: The state of /dev/md/dsk/gamma is not okay
        and it was attempted to be mounted read/write
mount: Please run fsck and try againAt which point I try to run fsck.
In manual mode, it seems it will never end (and never does, I ctrl^c)
In preen mode, it recommends to run in manual mode.
In yes sir mode, it runs for a long time, clears corrects slashes and dices, but terminates on a coredump.
I don't know what is the best course of action at that point?
The data seems to be on the disk (using strings, I recognize all the filenames)
Is it possible to extract a small section of the 232Gb and run fsck manually on that?
Is there some documentation for fsdb?
Thanks for all your suggestions,
Matthieu

Answer 1

There are probably on the order of 5000 files on there.
There is no output in /var/adm/messages, and the console output looks like (after about 2hrs):
I=9633  Symlink longer than supported maximumBAD FILE I=9633  OWNER=41064 MODE=120140
SIZE=512742369966006384 MTIME=Oct 13 18:42 1973
CLEAR?  yes
I=9633  Symlink longer than supported maximumBAD FILE I=9633  OWNER=41064 MODE=120140
SIZE=512742369966006384 MTIME=Oct 13 18:42 1973
CLEAR?  yes
I=9633  Symlink longer than supported maximumBAD FILE I=9633  OWNER=41064 MODE=120140
SIZE=512742369966006384 MTIME=Oct 13 18:42 1973
CLEAR?  yes
fsck: warning: the following command (process 2184) was terminated by signal 11 and dumped core
fsck -F ufs -y -o b=32 /dev/md/dsk/gamma(I've tried with other superblocks and its the same result)
I have actually a pretty good idea of whats on the disk: I backed up music using cddawav, so the directory structure is
/Media/Music/{author_album}/audio_XX.{wav,txt}
I have never used fsdb, so I will heed your advice.
I am thinking of perhaps using a tool like foremost...
Although I am curious to discover what could have gone wrong.
Matt