Hi,
want to report that crash.
cantaloupe:~ # fdisk -l
Disk /dev/sda: 64 heads, 32 sectors, 8678 cylinders
Units = cylinders of 2048 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 1001 1025008 8e Linux LVM
/dev/sda2 1002 5002 4097024 8e Linux LVM
/dev/sda3 5003 8678 3764224 8e Linux LVM
Disk /dev/sdb: 64 heads, 32 sectors, 8678 cylinders
Units = cylinders of 2048 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 4 4080 41 PPC PReP Boot
/dev/sdb2 5 1028 1048576 82 Linux swap
/dev/sdb3 1029 8678 7833600 83 Linux
cantaloupe:~ # df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb3 reiserfs 7.5G 1.4G 6.1G 19% /
/dev/blah/olaf jfs 2.6G 496k 2.5G 1% /abuild
shmfs shm 969M 0 968M 0% /dev/shm
cantaloupe:~ # rpm -q jfsprogs
jfsprogs-1.0.10-4
cantaloupe:~ # free
total used free shared buffers cached
Mem: 1984188 57968 1926220 0 9108 16620
-/+ buffers/cache: 32240 1951948
Swap: 1048568 0 1048568
it runs jfs 1.0.10 on 2.4.16aa on a 43p 260 2cpus, 2gig.
I had a crash or power off one day ago, it might be related to
a corrupted filesystem.
Gruss Olaf
----- Forwarded message from Olaf Hering <[EMAIL PROTECTED]> -----
Date: Thu, 13 Dec 2001 18:14:21 +0100
From: Olaf Hering <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [kernel] 2.4.16 crash jfs on lvm
On Thu, Dec 13, Andrea Arcangeli wrote:
> On Thu, Dec 13, 2001 at 05:25:05PM +0100, Olaf Hering wrote:
> > On Thu, Dec 13, Olaf Hering wrote:
> >
> > huberts current, ppc power3 smp 2gig, 2gig jfs on lvm partition, root on
> > reiser.
> >
> > > cantaloupe:~/yaboot/yaboot-1.3.6 # cpu 1: vector: 0 at pc = c0043be0, lr =
>c0043be0
> > > msr = 9032, sp = c06a5e70 [c06a5db8]
> > > current = c06a4000, pid = 9, comm = jfsCommit
> > > 1:mon> t
> > > backtrace:
> > > c0043be0 c0043b1c T kunmap_high
> > > c011b6bc c011b550 t __write_metapage
> > > c011b914 c011b730 T release_metapage
> > > c011f1f0 c011f004 t txUnlock
> > > c0121eb8 c0121a98 T txAbort
> > > c01220ec c0121ef8 T jfs_lazycommit
> > > c0007418 c00073ec T kernel_thread
> >
> >
> > kernel BUG at highmem.c:169!
> > kernel BUG at highmem.c:169!
> >
> >
> > Yeah, more a JFYI...
>
> sounds like a genuine jfs bug, suprious kunmap in __write_metapage.
looks corrupted now, rebooted with ppc64....
Welcome to SuSE Linux SLES-7 (PPC) - Kernel 2.4.13-ppc64-SMP (ttyS0).
cantaloupe login: xmon called
cpu 0: Vector: 0 at [c000000004ca3380]
pc: c0000000001aa8a8 (xmon+0x284)
lr: c0000000001aa8a8 (xmon+0x284)
sp: c000000004ca3310
msr: a000000000009032
current = 0xc000000004ca0000
paca = 0xc0000000003ff000
current = c000000004ca0000, pid = 10, comm = jfsCommit
0:mon> t
c000000004ca3310 c0000000001aa740 xmon+0x11c
c000000004ca34f0 c00000000018bea8 dbAdjCtl+0x2e8
c000000004ca35d0 c00000000018b3a4 dbFreeDmap+0x68
c000000004ca3670 c000000000188a50 dbFree+0x178
c000000004ca3720 c0000000001a06f4 txFreeMap+0x168
c000000004ca37d0 c000000000180e1c xtTruncate+0xac0
c000000004ca39d0 c000000000178cdc freeZeroLink+0x244
c000000004ca3a70 c000000000177004 jfs_delete_inode+0x84
c000000004ca3af0 c0000000000ba1a4 iput+0x274
c000000004ca3b80 c0000000001a02bc txUpdateMap+0x358
c000000004ca3c60 c0000000001a10c0 txLazyCommit+0x38
c000000004ca3cf0 c0000000001a1400 jfs_lazycommit+0x1e0
c000000004ca3e30 c00000000001284c <unknown code>
it was created with ppc64, I think it crashed once or the box was
powered off. Maybe it is just a result of a corrupted filesystem.
The mail that I sent this week, corrupted modules.conf on reiserfs, that
box was completly hosed after the crash. "awk '{ print $3 }' <
/dev/null" returned a segfault in gawk..
Gruss Olaf
--
$ man clone
BUGS
Main feature not yet implemented...
----- End forwarded message -----
--
--
$ man clone
BUGS
Main feature not yet implemented...
_______________________________________________
Jfs-discussion mailing list
[EMAIL PROTECTED]
http://www-124.ibm.com/developerworks/oss/mailman/listinfo/jfs-discussion
