[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.
CANNOT CONTINUE. [EMAIL PROTECTED] ~]# jfs_debugfs /dev/VolGroup00/lvol0 jfs_debugfs version 1.1.7, 22-Jul-2004
Aggregate Block Size: 4096
> su
[1] s_magic: 'JFS1' [15] s_ait2.addr1: 0x00
[2] s_version: 1 [16] s_ait2.addr2: 0x00022f85
[3] s_size: 0x000000022ee2a098 s_ait2.address: 143237
[4] s_bsize: 4096 [17] s_logdev: 0x00000000
[5] s_l2bsize: 12 [18] s_logserial: 0x00000000
[6] s_l2bfactor: 3 [19] s_logpxd.len: 8192
[7] s_pbsize: 512 [20] s_logpxd.addr1: 0x00
[8] s_l2pbsize: 9 [21] s_logpxd.addr2: 0x45dce000
[9] pad: Not Displayed s_logpxd.address: 1172103168
[10] s_agsize: 0x01000000 [22] s_fsckpxd.len: 35821
[11] s_flag: 0x10200900 [23] s_fsckpxd.addr1: 0x00
JFS_LINUX [24] s_fsckpxd.addr2: 0x45dc5413
JFS_COMMIT JFS_GROUPCOMMIT s_fsckpxd.address: 1172067347
JFS_INLINELOG [25] s_time.tv_sec: 0x41f94590
[26] s_time.tv_nsec: 0x00000000
[27] s_fpack: ''
[12] s_state: 0x00000000
FM_CLEAN
[13] s_compress: 0
[14] s_ait2.len: 4
On Jan 27, 2005, at 2:10 PM, Dave Kleikamp wrote:
I expected that to at least get by the superblock check. Can you run fsck.jfs again with the -v flag? You can also use jfs_debug to see if the superblock looks somewhat sane.
On Thu, 2005-01-27 at 13:51 -0600, Sean Murphy wrote:I tried copying in the fresh superblock and ended up with this. Anything else? It about 10 days worth of computing on there, so I'm only spending another few hours on it before we just regenerate it all.
[EMAIL PROTECTED] ~]# fsck.jfs -f /dev/VolGroup00/lvol0 fsck.jfs version 1.1.7, 22-Jul-2004 processing started: 1/27/2005 13.49.9 The current device is: /dev/VolGroup00/lvol0 Superblock is corrupt and cannot be repaired since both primary and secondary copies are corrupt.
CANNOT CONTINUE.-- David Kleikamp IBM Linux Technology Center
Sean Murphy [EMAIL PROTECTED]
_______________________________________________ Jfs-discussion mailing list [email protected] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
