On Fri, 2005-07-29 at 17:02 -0400, Arshavir Grigorian wrote: > GDB: > > (gdb) run /dev/vg00/lvol0 > Starting program: /sbin/fsck.jfs /dev/vg00/lvol0 > (no debugging symbols found) > (no debugging symbols found) > (no debugging symbols found) > /sbin/fsck.jfs version 1.1.7, 22-Jul-2004 > processing started: 7/29/2005 16.59.27 > Using default parameter: -p > The current device is: /dev/vg00/lvol0 > Block size in bytes: 4096 > Filesystem size in blocks: 1855565824 > **Phase 0 - Replay Journal Log > **Phase 1 - Check Blocks, Files/Directories, and Directory Entries > > Program received signal SIGBUS, Bus error. > 0x0002f198 in ?? () > (gdb) bt > #0 0x0002f198 in ?? () > #1 0x0002f178 in ?? () > Previous frame identical to this frame (corrupt stack?) > (gdb)
Without the debugging symbols, this isn't very helpful. I believe if you build jfsutils from the source (http://jfs.sourceforge.net/project/pub/jfsutils-1.1.8.tar.gz), fsck/jfs_fsck will be unstripped, and you may get something useful from gdb run against it. The binaries are stripped when copied to /sbin. I suspect that jfs_fsck is doing some sort of unaligned memory access, but I'm not sure where. Other architectures are not so strict. I'm still not sure about the in-kernel problem. Maybe sparc defines some data type differently than the other architectures. Are there any compile warnings when compiling fs/jfs/ in the sparc64 kernel? Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
