> From: Dave Kleikamp <snip> > Unfortunately, the damage extends to the root directory, which can't be > ignored. Since fsck says that your primary & secondary allocation > structures don't match, you could try forcing jfs_fsck to use the > secondary instead of the primary. This untested patch should do that. <snip>
That patch doesn't resolve the problem... s5n06.hep(rader): sudo ./jfs_fsck -d -f /dev/sda1 ./jfs_fsck version 1.1.8, 03-May-2005 processing started: 6/21/2005 8.40.29 The current device is: /dev/sda1 [xchkdsk.c:1555] Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 [fsckpfs.c:3227] Primary superblock is valid. [fsckmeta.c:1559] The type of file system for the device is JFS. [xchkdsk.c:1572] Block size in bytes: 4096 [xchkdsk.c:1899] Filesystem size in blocks: 586057467 [xchkdsk.c:1906] **Phase 0 - Replay Journal Log [xchkdsk.c:1913] LOGREDO: Log already redone! [logredo.c:555] logredo returned rc = 0 [xchkdsk.c:1945] **Phase 1 - Check Blocks, Files/Directories, and Directory Entries [xchkdsk.c:2038] Invalid data (7) detected in file system object MA1. [fsckmeta.c:2465] Invalid data (8) detected in file system object MA1. [fsckmeta.c:2473] Invalid data (9) detected in file system object MA1. [fsckmeta.c:2481] Invalid data (10) detected in file system object MA1. [fsckmeta.c:2489] Invalid data (11) detected in file system object MA1. [fsckmeta.c:2500] Invalid data (12) detected in file system object MA1. [fsckmeta.c:2508] Invalid data (13) detected in file system object MA1. [fsckmeta.c:2516] Invalid data (14) detected in file system object MA1. [fsckmeta.c:2524] Secondary metadata inode A1 is corrupt. [fsckmeta.c:2565] Unable to read the Primary File/Directory Allocation Table. [fsckmeta.c:1897] Errors detected in the Secondary File/Directory Allocation Table. [fsckmeta.c:1904] CANNOT CONTINUE. [fsckmeta.c:1911] processing terminated: 6/21/2005 8:40:30 with return code: -10049 exit code: 4. [xchkdsk.c:469] s5n06.hep(rader): grep FSCK_FAILED_BOTHAITBAD *.h xfsck.h:#define FSCK_FAILED_BOTHAITBAD -10049 The file system now appears in the same sorry shape as the file system a colleage of mine experienced with the exactly same hardware and os... http://sourceforge.net/mailarchive/message.php?msg_id=10804175 What'dya make of that? Fwiw (nothing??), I patched around the failure above... *************** *** 1903,1910 **** agg_recptr->ag_dirty = 1; fsck_send_msg(fsck_CANTCONTINUE); } else if (primary_part1_bad && secondary_part1_bad) { ! agg_recptr->ag_dirty = 1; ! fsck_send_msg(fsck_CANTCONTINUE); } else if (primary_part2_bad && secondary_part2_bad) { agg_recptr->ag_dirty = 1; fsck_send_msg(fsck_CANTCONTINUE); --- 1907,1916 ---- agg_recptr->ag_dirty = 1; fsck_send_msg(fsck_CANTCONTINUE); } else if (primary_part1_bad && secondary_part1_bad) { ! //agg_recptr->ag_dirty = 1; ! //fsck_send_msg(fsck_CANTCONTINUE); ! printf("SRDEBUG Ignoring primary_part1_bad && secondary_part1_bad\n"); ! vsait_rc = FSCK_OK; } else if (primary_part2_bad && secondary_part2_bad) { agg_recptr->ag_dirty = 1; fsck_send_msg(fsck_CANTCONTINUE); ....and the result is malloc() in alloc_wsp_extent() is failing... s5n06.hep(rader): sudo ./jfs_fsck -d -f /dev/sda1 ./jfs_fsck version 1.1.8, 03-May-2005 processing started: 6/21/2005 9.0.52 The current device is: /dev/sda1 [xchkdsk.c:1555] Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 [fsckpfs.c:3227] Primary superblock is valid. [fsckmeta.c:1559] The type of file system for the device is JFS. [xchkdsk.c:1572] Block size in bytes: 4096 [xchkdsk.c:1899] Filesystem size in blocks: 586057467 [xchkdsk.c:1906] **Phase 0 - Replay Journal Log [xchkdsk.c:1913] LOGREDO: Log already redone! [logredo.c:555] logredo returned rc = 0 [xchkdsk.c:1945] **Phase 1 - Check Blocks, Files/Directories, and Directory Entries [xchkdsk.c:2038] Invalid data (7) detected in file system object MA1. [fsckmeta.c:2464] Invalid data (8) detected in file system object MA1. [fsckmeta.c:2472] Invalid data (9) detected in file system object MA1. [fsckmeta.c:2480] Invalid data (10) detected in file system object MA1. [fsckmeta.c:2488] Invalid data (11) detected in file system object MA1. [fsckmeta.c:2499] Invalid data (12) detected in file system object MA1. [fsckmeta.c:2507] Invalid data (13) detected in file system object MA1. [fsckmeta.c:2515] Invalid data (14) detected in file system object MA1. [fsckmeta.c:2523] Secondary metadata inode A1 is corrupt. [fsckmeta.c:2564] Unable to read the Primary File/Directory Allocation Table. [fsckmeta.c:1897] Errors detected in the Secondary File/Directory Allocation Table. [fsckmeta.c:1904] SRDEBUG Ignoring primary_part1_bad && secondary_part1_bad Insufficient dynamic storage available for required workspace (1,6). CANNOT CONTINUE [fsckwsp.c:287] processing terminated: 6/21/2005 9:06:30 with return code: -10097 exit code: 8. [xchkdsk.c:469] ugh. steve - - - systems & network manager high energy physics university of wisconsin ------------------------------------------------------- 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
