> > i tried to fix a jfs-partition after a kernel crash (caused by alsa,
> > not jfs ;) ), but jfs_fsck had some problems...
>
> It may help pinpoint the problem if you run jfs_fsck with the -v flag.
> Another thing might be to run it under gdb and send me the stack trace
> when it hits the segmentation fault.
running it from gdb with -v:
-------------------------------------------------------------------
/home/nevyn/jfsutils-1.1.1/fsck/jfs_fsck version 1.1.1, 17-Dec-2002
The current device is: /dev/yhaunn/scratch
(chklog) FSCK Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
(chklog) FSCK Primary superblock is valid.
(chklog) FSCK The type of file system for the device is JFS.
Block size in bytes: 4096
File system size in blocks: 1049600
Phase 0 - Replay Journal Log
(chklog) FSCK:LOGREDO: Allocating for ReDoPage: (d) 4096 bytes
(chklog) FSCK:LOGREDO: Allocating for NoDoFile: (d) 4096 bytes
(chklog) FSCK:LOGREDO: Log record for Volume Mount at: 0x02e0a00
(chklog) FSCK:LOGREDO: Log record for Sync Point at: 0x02e09dc
(chklog) FSCK:LOGREDO: Attempt to read file system primary superblock
failed.
(chklog) FSCK:LOGREDO: Attempt to read file system superblock failed.
(chklog) FSCK:LOGREDO: Unable to update file system superblock.
logredo failed (rc=-230). FSCK continuing.
Phase 1 - Check Blocks, Files/Directories, and Directory Entries.
Phase 2 - Count Links.
Phase 3 - Rescan for Duplicate Blocks and Verify Directory Tree.
Phase 4 - Report Problems.
Phase 5 - Check Connectivity.
Phase 6 - Perform Approved Corrections.
Phase 7 - Rebuild File/Directory Allocation Maps.
Program received signal SIGSEGV, Segmentation fault.
0x080564b4 in iags_rebuild (is_aggregate=0, which_it=16, which_ait=396,
iagiptr=0xbffff930,
msg_info_ptr=0xbffff950) at fsckimap.c:3209
3209 iagiptr->agtbl[this_ag].backed_inodes +=
---------------------------------------------------------------------
backtrace gives:
----------------------------------------------------------------------
#0 0x080564b4 in iags_rebuild (is_aggregate=0, which_it=16,
#which_ait=396, iagiptr=0xbffff930,
msg_info_ptr=0xbffff950) at fsckimap.c:3209
#1 0x080569d6 in iamap_rebuild (is_aggregate=0, which_it=16,
#which_ait=396, iagiptr=0xbffff930,
msg_info_ptr=0xbffff950) at fsckimap.c:3459
#2 0x08057097 in rebuild_fs_iamaps () at fsckimap.c:3807
#3 0x0806f903 in phase7_processing () at xchkdsk.c:2942
#4 0x0806d0fb in main (argc=3, argv=0xbffffa04) at xchkdsk.c:382
----------------------------------------------------------------------
some other infos that might interesst:
running is a 2.4.20 copiled from the debian/sid source.
the system is (surprise...) a debian/sid, which normally installs jfs
tools 1.0.23. I compiled 1.1.1 to see if this problem has been solved
since 1.0.23 (all dumps above are from 1.1.1 as written in the dump).
the partition sits in an lvm-volume (as you can see from the device-name).
i'm completely green concerning to kernel/linux-system programming and
gdb, but if i can help in some way please tell me (i'm not so green
concerning programming ;) )
thanks a lot
emanuel
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
