On Fri, 2006-04-21 at 19:50 +0200, Karl Schricker wrote:
> Thanks for the quick reply, Dave!
>
> I installed the 1.1.10 utils and it still faults. Here are the details.
>
>
> Karl
>
> (gdb) run /dev/md0
> Starting program: /sbin/fsck.jfs /dev/md0
> Reading symbols from shared object read from target memory...done.
> Loaded system supplied DSO at 0xffffe000
> /sbin/fsck.jfs version 1.1.10, 19-Oct-2005
> processing started: 4/21/2006 10.47.4
> Using default parameter: -p
> The current device is: /dev/md0
> Block size in bytes: 4096
> Filesystem size in blocks: 183148848
> **Phase 0 - Replay Journal Log
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x080717a3 in markImap (fsimap=
> {fileset = 16, imap_page_count = 93, fsimapctrl = 0x814e000, imap_wsp
> = 0x8151000, iag_pbuf = 0x814f000, imap_pagenum = 7, iag_pbuf2 = 0x8150000,
> imap_pagenum2 = 0, next = 0x0}, inum=48326904, inopxd=
> {len = 16, addr1 = 0, addr2 = 134222860}, val=1, vol=0)
> at log_work.c:2024
> 2024 imp = fsimap.imap_wsp[(iag_num + 1)].imap_data;
I haven't seen this before, but it looks like we're not sanity checking
iag_num. jfs_fsck only allocates space for fsimap.imap_wsp depending on
the size of the inode map. It must be trying to handle an inode number
that goes beyond the inode map.
I don't know if the problem is due to bad data in the journal,
corruption somewhere else, or a bug in the jfs code somewhere. One way
to continue would be to run fsck with the --omit_journal_replay flag.
You may lose some recently written data this way though. It may be
possible to mount the file system read-only and backing up any data that
you can get to before continuing with fsck.
If you can wait, I may be able to do some more investigation, but I'm
afraid I can't get to it right away.
> (gdb) where
> #0 0x080717a3 in markImap (fsimap=
> {fileset = 16, imap_page_count = 93, fsimapctrl = 0x814e000, imap_wsp
> = 0x8151000, iag_pbuf = 0x814f000, imap_pagenum = 7, iag_pbuf2 = 0x8150000,
> imap_pagenum2 = 0, next = 0x0}, inum=48326904, inopxd=
> {len = 16, addr1 = 0, addr2 = 134222860}, val=1, vol=0)
> at log_work.c:2024
> #1 0x0807275b in updatePage (ld=0xbfa9f648, logaddr=7860320)
> at log_work.c:2806
> #2 0x08072d41 in doAfter (ld=0xbfa9f648, logaddr=7860320) at log_work.c:633
> #3 0x0806f766 in jfs_logredo (pathname=0xbfaa1706 "/dev/md0",
> fp=0x814a568, use_2nd_aggSuper=135786848) at logredo.c:690
> #4 0x0806a473 in phase0_processing () at xchkdsk.c:1882
> #5 0x0806be43 in main (argc=2, argv=0xbfa9f764) at xchkdsk.c:334
>
--
David Kleikamp
IBM Linux Technology Center
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
