2002-08-12 06:31:31

by James Lee

[permalink] [raw]
Subject: Re: kernel BUG at filemap.c:843!

Hi,

I'm also having the exactly same problem.
Tested with 2.4.19-xfs(checked out from SGI's CVS on Aug 10) on Redhat 7.2.
Kernel and userland tools are compiled with gcc 2.91.66
The following is the result of some tests:

scsidisks -> xfs: OK
scsidisks -> raid5 -> xfs: OK
scsidisks -> lvm -> xfs: OK
scsidisks -> raid0 -> lvm -> xfs: OK
scsidisks -> raid1 -> lvm -> xfs: OK
scsidisks -> raid5 -> lvm -> xfs: kernel BUG at filemap.c:843!

This problem is always reproducible with the following shell script:

#!/bin/sh
mkraid /dev/md0
vgcreate VolumeGroup /dev/md0
lvcreate -L1G -nTestVolume VolumeGroup
mkfs.xfs -f -d size=32m /dev/VolumeGroup/TestVolume
mount -t xfs /dev/VolumeGroup/TestVolume
/mnt -onoatime,nodiratime,usrquota,grpquota

Whenever I run the above script, mount command always generates kernel oops.
But, if I insert some delay as of the following, then mount goes well:


#!/bin/sh
mkraid /dev/md0
vgcreate VolumeGroup /dev/md0
lvcreate -L1G -nTestVolume VolumeGroup
mkfs.xfs -f -d size=32m /dev/VolumeGroup/TestVolume
sleep 1
mount -t xfs /dev/VolumeGroup/TestVolume
/mnt -onoatime,nodiratime,usrquota,grpquota

JLee

----- Original Message -----
From: "Dagfinn Ilmari Manns?er" <[email protected]>
To: <[email protected]>; <[email protected]>
Sent: Sunday, August 11, 2002 8:27 PM
Subject: kernel BUG at filemap.c:843!


> Hi,
>
> I have been bitten a few times by the BUG() in unlock_page(), both
> with 2.4.19-rc3-xfs and 2.4.19-xfs (the latter checked out from SGI's
> CVS on Aug 10). The system is SCSI-only, with a raid5 array as an LVM
> physical volume and XFS on all the volumes.
>
> Software-wise it's Debian Woody, but the kernel is compiled on a Sid
> box with gcc 2.95.4-16.
>
> Attached are the decoded oops, the module list and the config.
>
> --
> ilmari
>
>