[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a8748490608300219qb3adege9e400bc5d51a21d@mail.gmail.com>
Date: Wed, 30 Aug 2006 11:19:49 +0200
From: "Jesper Juhl" <jesper.juhl@...il.com>
To: "Kasper Sandberg" <lkml@...anurb.dk>
Cc: "Nathan Scott" <nathans@....com>,
"Linus Torvalds" <torvalds@...l.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Linux v2.6.18-rc5
On 30/08/06, Kasper Sandberg <lkml@...anurb.dk> wrote:
> On Tue, 2006-08-29 at 01:30 +0200, Jesper Juhl wrote:
> > On 29/08/06, Nathan Scott <nathans@....com> wrote:
> > > On Mon, Aug 28, 2006 at 12:35:00PM +0200, Jesper Juhl wrote:
> > > > On 28/08/06, Kasper Sandberg <lkml@...anurb.dk> wrote:
> > > > > On Mon, 2006-08-28 at 12:10 +0200, Jesper Juhl wrote:
> > > > > > Not really a regression, more like a long standing bug, but XFS has
> > > > > > issues in 2.6.18-rc* (and earlier kernels, at least post 2.6.11).
> > > > > and you are saying this issue exists in all post .11 kernels?
> > >
> > > I would be surprised if this is not a day one bug, it probably
> > > even affects the IRIX version of XFS. Our problem is the lack
> > > of a test case to find it - my efforts have come to naught so
> > > far. I'm having to cross my fingers that Jesper can extract a
> > > bit more information when he's next able to hit it.
> > >
> > I'm trying my best, but it's difficult. Often I can only run the -rc
> > kernel for a few hours on the box that currently shows the problem,
> > and that's not enough to hit the fault.
> > I've configured a XFS partition on my home workstation and I'm keeping
> > that one busy doing various rsync's and running benchmarks etc -
> > putting as much different stress on the XFS filesystem as I can. I'm
> > also setting up a test box at work to try and duplicate the problem on
> > a non-production server. I won't be able to duplicate the setup
> > exactly, but it'll be close.
>
> i have nyself tested xfs in -rc5 now, doing rsync over and over, and
> been unable to hit any problem, it indeed seems very hard to reproduce.
>
Just in case I have not mentioned it before; the box I'm seeing the
problem on is a dual 3.2GHz Xeon and the kernel is compiled for SMP.
might be relevant, might not be...
--
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists