Dave Kleikamp wrote:
On Thursday 09 January 2003 02:10, Francesc Guasch wrote:
I'm afraid I don't have a good answer for you. When jfs_fsck reports
that both superblocks are bad, it's usually an indication that the
partition is screwed up somehow. Running xpeek (name changed to
jfs_debugfs just recently) and using the sup command ("sup s" for the
secondary) will show you if the superblocks look sane at all.
I attack the results of xpeek. I also noticed it cores when it
tries to mount. I attach the log.
Did you try booting with an older kernel to see if you could still
access that partition? Also, have you tried formatting a different
partition as jfs to see if it behaved correctly?
I booted with an older kernel and it happened the same.
--
frankie
[1] s_magic: 'JFS1' [15] s_ait2.addr1: 0x00
[2] s_version: 1 [16] s_ait2.addr2: 0x000003a6
[3] s_size: 0x00000000038edb90 s_ait2.address: 934
[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: 0x0071dc89
[9] pad: Not Displayed s_logpxd.address: 7462025
[10] s_agsize: 0x00010000 [22] s_fsckpxd.len: 279
[11] s_flag: 0x10200900 [23] s_fsckpxd.addr1: 0x00
JFS_LINUX [24] s_fsckpxd.addr2: 0x0071db72
s_fsckpxd.address: 7461746
JFS_COMMIT JFS_GROUPCOMMIT [25] s_time.tv_sec: 0x3ddba535
[26] s_time.tv_nsec: 0x40089c2b
JFS_INLINELOG [27] s_fpack: ' '
[28] s_rsrvd1: Not Displayed
[29] s_device: 0x1ffc
[12] s_state: 0x00000000
FM_CLEAN
[13] s_compress: 0
[14] s_ait2.len: 4
display_super: [m]odify or e[x]it:
Jan 13 09:01:53 barraxova kernel: attempt to access beyond end of device
Jan 13 09:01:53 barraxova kernel: 16:01: rw=0, want=29848108, limit=29398918
Jan 13 09:01:53 barraxova kernel: Unable to handle kernel NULL pointer dereferen
ce at virtual address 00000004
Jan 13 09:01:53 barraxova kernel: printing eip:
Jan 13 09:01:53 barraxova kernel: c0147a41
Jan 13 09:01:53 barraxova kernel: *pde = 00000000
Jan 13 09:01:53 barraxova kernel: Oops: 0000
Jan 13 09:01:53 barraxova kernel: CPU: 0
Jan 13 09:01:53 barraxova kernel: EIP: 0010:[<c0147a41>] Not tainted
Jan 13 09:01:53 barraxova kernel: EFLAGS: 00010246
Jan 13 09:01:53 barraxova kernel:
Jan 13 09:01:53 barraxova kernel: EIP is at (2.4.18-19.7.xcustom)
Jan 13 09:01:53 barraxova kernel: eax: 00000000 ebx: cdf02780 ecx: 00000000
edx: cdf02780
Jan 13 09:01:53 barraxova kernel: esi: cdf02780 edi: 00000000 ebp: 00000000
esp: c8481e3c
Jan 13 09:01:53 barraxova kernel: ds: 0018 es: 0018 ss: 0018
Jan 13 09:01:53 barraxova kernel: Process mount (pid: 8289, stackpage=c8481000)
Jan 13 09:01:53 barraxova kernel: Stack: cdf02780 c0148df0 cdf02780 cc713980 ca2
1dc00 cdf02780 c015f906 cdf02780
Jan 13 09:01:53 barraxova kernel: c0226c28 00001601 00001601 fffffff3 c02
21a30 ca21dc00 c0221a30 c013b01d
Jan 13 09:01:53 barraxova kernel: ca21dc00 00000000 00000000 00001601 c19
7e280 c0113726 c01ec2b2 c8480000
Jan 13 09:01:53 barraxova kernel: Call Trace: [<c0148df0>] (0xc8481e40))
Jan 13 09:01:53 barraxova kernel: [<c015f906>] (0xc8481e54))
Jan 13 09:01:53 barraxova kernel: [<c013b01d>] (0xc8481e78))
Jan 13 09:01:53 barraxova kernel: [<c0113726>] (0xc8481e90))
Jan 13 09:01:53 barraxova kernel: [<c01ec2b2>] (0xc8481e94))
Jan 13 09:01:53 barraxova kernel: [<c013406a>] (0xc8481e9c))
Jan 13 09:01:53 barraxova kernel: [<c013b1fc>] (0xc8481ee0))
Jan 13 09:01:53 barraxova kernel: [<c014add6>] (0xc8481f14))
Jan 13 09:01:53 barraxova kernel: [<c014b08b>] (0xc8481f44))
Jan 13 09:01:53 barraxova kernel: [<c014aeec>] (0xc8481f80))
Jan 13 09:01:53 barraxova kernel: [<c014b40c>] (0xc8481f94))
Jan 13 09:01:53 barraxova kernel: [<c010880b>] (0xc8481fc0))
Jan 13 09:01:53 barraxova kernel:
Jan 13 09:01:53 barraxova kernel:
Jan 13 09:01:53 barraxova kernel: Code: 8b 40 04 85 c0 74 08 53 ff d0 59 eb 11 8
9 f6 53 8b 15 74 a1
