From: Steve Lord <lord@xfs.org>
To: Mihai RUSU <dizzy@roedu.net>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at fs/xfs/support/debug.c:106!
Date: Wed, 10 Dec 2003 07:42:20 -0600 [thread overview]
Message-ID: <3FD722BC.1000205@xfs.org> (raw)
In-Reply-To: <Pine.LNX.4.56L0.0312100953310.8346@ahriman.bucharest.roedu.net>
Mihai RUSU wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi
>
>Another problem now, on another system. This one is a 2xP3 1.1 Ghz, 3 GB
>RAM, MB Intel SCB2, Adaptec 7899 Controller onboard having one 18 GB SCSI
>disk connected to it (for XFS external journal, swap and / partition which
>is on ext3), Mylex 170 RAID connected to external storage enclosure with 3
>x 70 GB SCSI RAID5. The kernel error message is:
>
>
>
Mihai,
You missed one thing out of your report, the console message xfs output
before
this.
I suspect it would have been this: xfs_iget_core: ambiguous vns: vp/0x .....
but it would be good to confirm it. This was supposed to be a dead code
path which there was no longer a route to, it is possible something in the
NFS interface in 2.6 has changed to cause this though. Basically a race
between two threads looking up the same inode, xfs has it cached already
and two threads raced to setup the mapping from the linux inode.
The use of iget_locked when looking up new inodes is supposed to protect
against just this condition.
Steve
next prev parent reply other threads:[~2003-12-10 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 8:18 kernel BUG at fs/xfs/support/debug.c:106! Mihai RUSU
2003-12-10 13:42 ` Steve Lord [this message]
2003-12-10 13:56 ` Mihai RUSU
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=3FD722BC.1000205@xfs.org \
--to=lord@xfs.org \
--cc=dizzy@roedu.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox