fsck.jfs version 1.1.7, 22-Jul-2004
processing started: 1/27/2005 15.40.30
The current device is: /dev/VolGroup00/lvol0
Open(...READ/WRITE EXCLUSIVE...) returned rc = 0
Primary superblock is valid.
The type of file system for the device is JFS.
Block size in bytes: 4096
Filesystem size in blocks: 1172111360
**Phase 0 - Replay Journal Log
LOGREDO: Log already redone!
logredo returned rc = 0
**Phase 1 - Check Blocks, Files/Directories, and Directory Entries
Invalid stamp detected in file system object MA3.
Invalid data (35) detected in file system object MA3.
Invalid data (36) detected in file system object MA3.
Invalid data (37) detected in file system object MA3.
Invalid data (38) detected in file system object MA3.
Invalid data (39) detected in file system object MA3.
Invalid data (40) detected in file system object MA3.
Primary metadata inode A3 is corrupt.
Invalid data (7) detected in file system object MA1.
Invalid data (8) detected in file system object MA1.
Invalid data (9) detected in file system object MA1.
Invalid data (10) detected in file system object MA1.
Invalid data (11) detected in file system object MA1.
Invalid data (13) detected in file system object MA1.
Invalid data (14) detected in file system object MA1.
Secondary metadata inode A1 is corrupt.
Errors detected in the Primary File/Directory Allocation Table.
Errors detected in the Secondary File/Directory Allocation Table.
CANNOT CONTINUE.
processing terminated: 1/27/2005 15:40:30 with return code: -10049 exit code: 4.
On Jan 27, 2005, at 3:31 PM, Dave Kleikamp wrote:
This first superblock is good, but it's unhappy with another data structure, so fsck is wanting to compare an address in the primary superblock with that of the secondary (which I didn't have you copy). I'm not sure if this is going to get you much further, but we can try.
If you still have the sparse file that you ran mkfs against, run this to
copy the secondary superblock:
dd if=/somefile of=/dev/VolGroup00/lvol0 bs=4096 skip=15 seek=15 count=1
On Thu, 2005-01-27 at 15:12 -0600, Sean Murphy wrote:[EMAIL PROTECTED] ~]# fsck.jfs -v /dev/VolGroup00/lvol0 fsck.jfs version 1.1.7, 22-Jul-2004 processing started: 1/27/2005 15.11.50 Using default parameter: -p The current device is: /dev/VolGroup00/lvol0 Open(...READ/WRITE EXCLUSIVE...) returned rc = 0 Invalid data (13) detected in the superblock (P). Invalid magic number in the superblock (S). Superblock is corrupt and cannot be repaired since both primary and secondary copies are corrupt.
-- David Kleikamp
IBM Linux Technology Center
_______________________________________________
Jfs-discussion mailing list
[email protected]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs- discussion
Sean Murphy [EMAIL PROTECTED]
_______________________________________________ Jfs-discussion mailing list [email protected] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
