Since the bug database has been transitioned to the SourceForge bug database (http://www-124.ibm.com/developerworks/bugs/?group_id=35) my bug still lives on.. I'll recreate the info here. If anyone would like I'll create another (new) bug entry for this new database.
[root@peters /root]# fsck.jfs -v /dev/hda2 fsck.jfs version 1.0.10, 28-Nov-2001 The current device is: /dev/hda2 (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: 1050249 Phase 0 - Replay Journal Log (chklog) FSCK:LOGREDO: Journal log is now open. (major = 0x00, minor = 0x00) (chklog) FSCK:LOGREDO: Allocating for ReDoPage: (d) 4096 bytes (chklog) FSCK:LOGREDO: Allocating for NoDoFile: (d) 4096 bytes (chklog) FSCK:LOGREDO: Allocating for BMap: (d) 26704 bytes (chklog) FSCK:LOGREDO: Allocating for IMap: (d) 17552 bytes (chklog) FSCK:LOGREDO: Allocating for IMap: (d) 2048 bytes (chklog) FSCK:LOGREDO: Allocating for IMap: (d) 2048 bytes (chklog) FSCK:LOGREDO: Allocating for IMap: (d) 2048 bytes (chklog) FSCK:LOGREDO: Allocating for IMap: (d) 2048 bytes (chklog) FSCK:LOGREDO: markBmap: Block number(s) out of range (start=0x06f6f732e6c, length=(d)7500910). (chklog) FSCK:LOGREDO: Error in volume (d) 0. (chklog) FSCK:LOGREDO: Invalid volume block number (0x06f6f732e6c). (chklog) FSCK:LOGREDO: Log record for Sync Point at: 0x04fb958 (chklog) FSCK:LOGREDO: Not rebuilding the Inode Alloc Map because fsck will be doing it. (chklog) FSCK:LOGREDO: Write Inode Alloc Map control page failed in UpdateMaps(). (chklog) FSCK:LOGREDO: Unable to update map(s). logredo failed (rc=-265). FSCK continuing. Phase 1 - Check Blocks, Files/Directories, and Directory Entries. (chklog) FSCK Invalid data (45) detected in file system object DF233473. (chklog) FSCK File system object DF233473 has corrupt data (40). (chklog) FSCK processing terminated: 12/17/2001 17.30.34 with return code: -11010. [root@peters /root]# cat /proc/version Linux version 2.4.16-1 (root@peters) (gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-85)) #2 SMP Mon Dec 17 12:02:58 CST 2001 [root@peters /root]# cat /proc/ide/hda/geometry physical 59554/16/63 logical 3736/255/63 [root@peters /root]# All of this happened after a legitimate system failure (crash/power-outage)... So that's why I feel it is still relevant. I've lost the info on the original bug (#141 in the old database) so I don't remember what version of JFS I had that created this image (somewhere around 1.0.3 I believe.) I can provide any sort of trace/dump info necessary. Hope this helps. Peter Smith Peter Smith wrote: > No problem, I always try to follow up--thanks for the response. > > Yes I'm using the 1.0.4 utilities and did run the new fsck.jfs . > > Yes the output is exactly character-for-character the same. > > Let me know if I can be of more help. > > Peter > > > Barry Arndt wrote: > >> Peter, >> >> Thanks for your continued feedback and for providing information >> about the problem. The more we know, the better. >> >> Did you also install the 1.0.4 utilities and run with the new fsck.jfs? >> (The utilities are now separate from the jfs tar ball, so you must >> unzip them and execute make, make install, to copy the new >> versions into /sbin.) We fixed an fsck problem in 1.0.4 that may >> have an effect on the problem you are experiencing. >> >> If you are using the new 1.0.4 fsck.jfs, is the output the same as >> reported in JFS Bug 141? If not, let me know. >> >> Thanks again for your feedback. >> >> Barry Arndt >> IBM Linux Technology Center >> JFS for Linux http://oss.software.ibm.com/developerworks/opensource/jfs >> (512) 838-0723 t/l 678-0723 >> >> >> Peter Smith >> <[EMAIL PROTECTED]>@www-126.southbury.usf.ibm.com >> on 09-05-2001 10:36:08 AM >> >> Sent by: [EMAIL PROTECTED] >> >> >> To: [EMAIL PROTECTED] >> cc: >> Subject: [Jfs-discussion] FYI: JFS Bug 141 / Linux v2.4.9 / Jfs v1.0.4 >> still valid >> >> >> >> http://dwoss.lotus.com/developer/opensource/jfs/bugs/incoming?id=141 >> >> This is still giving the same results under kernel v2.4.9 (smp), jfs >> v1.0.4 on my corrupted hda2. No change as of yet. >> >> I've noticed something interesting with the logdump command: >> >> [root@peters output]# logdump -a /dev/hda2 >> Vol_Label : /dev/hda2 >> FSCK:LOGREDO: The Journal Log has wrapped. >> FSCK:LOGREDO: logRead: Log wrapped over itself (lognumread = (d) >> (351). >> log read failed 0x56af7c >> JFS_LOGDUMP: The current JFS log has been dumped into ./jfslog.dmp >> [root@peters output]# la >> >> Hope I am being helpful. >> >> Peter >> >> _______________________________________________ >> Jfs-discussion mailing list >> [EMAIL PROTECTED] >> http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion >> >> >> > > > _______________________________________________ > Jfs-discussion mailing list > [EMAIL PROTECTED] > http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion _______________________________________________ Jfs-discussion mailing list [EMAIL PROTECTED] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
