From: Stefan Priebe - FH <studium@profihost.com>
To: David Chinner <dgc@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS or Kernel Problem / Bug
Date: Mon, 22 Jan 2007 08:51:10 +0100 [thread overview]
Message-ID: <45B46CEE.4090808@profihost.com> (raw)
In-Reply-To: <20070122061852.GT33919298@melbourne.sgi.com>
Hi!
I'm not shure but perhaps it isn't an XFS Bug.
Here is what i find out:
We've about 300 servers at the momentan and 5 of them are "old" Intel
Pentium 4 Machines with a DFI PM-12 Mainboard with VIA chipset. It only
happens on THESE Machines. Other P4 Machines with a Tyan Mainboard or a
Gigabyte Mainboard are not affected. All 300 machines runs the same
Debian 3.0 with self build kernel. Some of these 5 use a 3ware
controller and some of them the mainboardcontroller. All systems are
using IDE.
But i cannot say what happens to these machines at the time of failure.
Sometimes these servers crashed directly after a few minutes. Sometimes
they run about 2-3 days... i've now downgraded all servers to 2.6.16.37.
Cause they are production machines... but i have one machine where we
can test - if you need something.
Here is the output running 2.6.16.37 at the moment:
xfs_growfs -n /
meta-data=/dev/root isize=256 agcount=16, agsize=603855 blks
= sectsz=512 attr=0
data = bsize=4096 blocks=9661680, imaxpct=25
= sunit=0 swidth=0 blks, unwritten=1
naming =version 2 bsize=4096
log =internal bsize=4096 blocks=4717, version=1
= sectsz=512 sunit=0 blks
realtime =none extsz=65536 blocks=0, rtextents=0
Stefan
David Chinner schrieb:
> On Sun, Jan 21, 2007 at 01:30:15PM +0100, Stefan Priebe - FH wrote:
>> Hello!
>>
>> I've 3 Servers which works wonderful with 2.6.16.X (also testet the
>> latest 2.6.16.37)
>>
>> but with 2.6.18.6 i get these errors:
>
> [ EIP is at xfs_bmap_add_extent_hole_delay+0x58d/0x59b ]
> [ EIP is at generic_file_buffered_write+0x390/0x6cf ]
>
> Do you have a reproducable test case for these? if not,
> do you have any idea what is going on in the system at the time
> of the failure?
>
> Can you describe the storage subsystem you are using and post the
> output of xfs_growfs -n <mntpt> on the filesystem that is causing
> problems?
>
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2007-01-22 7:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060801141545.B2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CED76B.20507@profihost.com>
[not found] ` <20060801142755.C2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CED8F4.9080208@profihost.com>
[not found] ` <20060801143212.D2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CEDA1D.5060607@profihost.com>
[not found] ` <20060801143803.E2326184@wobbly.melbourne.sgi.com>
[not found] ` <44CF36FB.6070606@profihost.com>
[not found] ` <20060802090915.C2344877@wobbly.melbourne.sgi.com>
[not found] ` <44D07AB7.3020409@profihost.com>
[not found] ` <20060802201805.A2360409@wobbly.melbourne.sgi.com>
2007-01-21 12:30 ` XFS or Kernel Problem / Bug Stefan Priebe - FH
2007-01-22 6:18 ` David Chinner
2007-01-22 7:51 ` Stefan Priebe - FH [this message]
2007-01-22 8:03 ` David Chinner
2007-01-22 8:07 ` Stefan Priebe - FH
2007-01-23 1:10 ` David Chinner
2007-01-23 8:31 ` Stefan Priebe - FH
2007-01-22 9:42 ` Stefan Priebe - FH
2007-01-23 19:49 ` Chuck Ebbert
2007-01-24 7:40 ` Stefan Priebe - FH
2007-01-24 14:57 ` Chuck Ebbert
2007-01-24 15:03 ` Stefan Priebe - FH
2007-01-24 15:13 ` Chuck Ebbert
2007-01-24 15:34 ` Stefan Priebe - FH
2007-01-24 16:51 ` Chuck Ebbert
2007-01-24 17:16 ` Stefan Priebe - FH
2007-01-24 17:56 ` Chuck Ebbert
2007-01-24 19:27 ` Stefan Priebe - FH
2007-01-25 20:52 ` Chuck Ebbert
2007-01-25 21:29 ` Stefan Priebe - FH
2007-01-30 10:44 ` Stefan Priebe - FH
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=45B46CEE.4090808@profihost.com \
--to=studium@profihost.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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.