All of lore.kernel.org
 help / color / mirror / Atom feed
From: "James Lee" <jlee@canada.com>
To: <linux-kernel@vger.kernel.org>, <linux-xfs@oss.sgi.com>
Subject: Re: kernel BUG at filemap.c:843!
Date: Mon, 12 Aug 2002 02:40:03 -0400	[thread overview]
Message-ID: <012301c241cb$16ea8530$fe232fd1@corona> (raw)
In-Reply-To: d8jsn1k9b03.fsf@wirth.ping.uio.no

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" <ilmari@ping.uio.no>
To: <linux-kernel@vger.kernel.org>; <linux-xfs@oss.sgi.com>
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
>
>



      reply	other threads:[~2002-08-12  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12  0:27 kernel BUG at filemap.c:843! Dagfinn Ilmari Mannsåker
2002-08-12  6:40 ` James Lee [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='012301c241cb$16ea8530$fe232fd1@corona' \
    --to=jlee@canada.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.