On Wed, 2005-01-26 at 14:28 -0600, Sean Murphy wrote:I read one place that possible copying a superblock from a fresh mkfs.jfs of an identical disk could fix this.
This may get you a little further, but it looks as though more than just
the superblocks are corrupted. The primary superblock rarely gets
touched during normal operations (and only at mount & unmount time) and
the secondary superblock isn't touched at all. I don't know what could
cause random data to be written over both superblocks, but my guess is
that the damage is more widespread.
Were there any syslog errors that appear to come from the lower-level drivers (dm, scsi)?
Not that I could see. The hardware seems fine.
Ok, I put the output of sup s below. It does look pretty random. But ifjfs_debug outputsu[1] s_magic: 'Pm??' [15] s_ait2.addr1: 0x47 [2] s_version: 2042101673 [16] s_ait2.addr2: 0xdad0bf23
s2p
This doesn't display the secondary superblock. It is a slightly different format as the 'sup' command. "sup s" will show you the secondary superblock.
I do jfs_debug a d 8 I can recognize directory names in the blocks. So
the data isn't completely trashed.
I'd be happy to give you a login on this machine if you want to try to debug it.
[1] s_magic: 'Pm??' [16] s_aim2.len: 15262231
[2] s_version: 2042101673 [17] s_aim2.addr1:
0xfb
[EMAIL PROTECTED] log]# jfs_debugfs /dev/VolGroup00/lvol0 jfs_debugfs version 1.1.7, 22-Jul-2004
Aggregate Block Size: -551086469
> sup s
[1] s_magic: '?;p' [15] s_ait2.addr1: 0xee
[2] s_version: -239149243 [16] s_ait2.addr2: 0x7cc1acce
[3] s_size: 0x51fd07c3f3a6da75 s_ait2.address: 1024295283918
[4] s_bsize: -239352807 [17] s_logdev: 0x2e76fe54
[5] s_l2bsize: -30923 [18] s_logserial: 0x08f4366f
[6] s_l2bfactor: -26675 [19] s_logpxd.len: 11615295
[7] s_pbsize: 1435256719 [20] s_logpxd.addr1: 0x96
[8] s_l2pbsize: -16611 [21] s_logpxd.addr2: 0x32a9ceaa
[9] pad: Not Displayed s_logpxd.address: 645095083690
[10] s_agsize: 0xe1f8bf91 [22] s_fsckpxd.len: 10200766
[11] s_flag: 0xce019b0d [23] s_fsckpxd.addr1: 0xbd
JFS_OS2 [24] s_fsckpxd.addr2: 0xe514c382
JFS_COMMIT JFS_GROUPCOMMIT s_fsckpxd.address: 815592162178
JFS_LAZYCOMMIT JFS_INLINELOG [25] s_time.tv_sec: 0xce8de14e
JFS_BAD_SAIT [26] s_time.tv_nsec: 0xd5efc40d
[27] s_fpack: 'Ä????9???'
[12] s_state: 0xbe4748f2
Unknown State
[13] s_compress: 2115698254
[14] s_ait2.len: 4244216
display_super: [m]odify or e[x]it: sup
> sup
[1] s_magic: 'Pm??' [15] s_ait2.addr1: 0x47
[2] s_version: 2042101673 [16] s_ait2.addr2: 0xdad0bf23
[3] s_size: 0x754f77d2ff733ab6 s_ait2.address: 308613791523
[4] s_bsize: -551086469 [17] s_logdev: 0xfc60bfc6
[5] s_l2bsize: -28929 [18] s_logserial: 0x87fec159
[6] s_l2bfactor: 14907 [19] s_logpxd.len: 10252845
[7] s_pbsize: 2041535975 [20] s_logpxd.addr1: 0xeb
[8] s_l2pbsize: 20148 [21] s_logpxd.addr2: 0xdad36af3
[9] pad: Not Displayed s_logpxd.address: 1012988603123
[10] s_agsize: 0x0eacfdf4 [22] s_fsckpxd.len: 15211755
[11] s_flag: 0x81763500 [23] s_fsckpxd.addr1: 0x87
[24] s_fsckpxd.addr2: 0x86413b36
JFS_COMMIT JFS_GROUPCOMMIT s_fsckpxd.address: 582073006902
[25] s_time.tv_sec: 0xaf1831dd
JFS_SPARSE [26] s_time.tv_nsec: 0x0f1820be
DASD_ENABLED [27] s_fpack: 'i?>z??u0?'
[12] s_state: 0x00000002
FM_DIRTY
[13] s_compress: -1951450971
[14] s_ait2.len: 10252845
display_super: [m]odify or e[x]it: x >
Sean Murphy [EMAIL PROTECTED]
_______________________________________________ Jfs-discussion mailing list [email protected] http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
