From: Paul Slootman <paul+nospam@wurtel.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux v2.6.18-rc5
Date: Wed, 6 Sep 2006 12:21:14 +0000 (UTC) [thread overview]
Message-ID: <edmefq$96n$1@news.cistron.nl> (raw)
In-Reply-To: 1156925667.28597.1.camel@localhost
Kasper Sandberg <lkml@metanurb.dk> wrote:
>
>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.
I have a box (dual opteron) that "reliably" has XFS failing every night
with kernels >= 2.6.16. It stays up without any problems with 2.6.15.7.
I've started doing a git bisect, and it failed with some 2.6.16-rc2
version, albeit in a different way to the usual XFS failure: all disk IO
related tasks were locked up in state 'D', no kernel messages on the
console. Probably not related to the previous XFS problem, I guess.
I now need to run at least one night with the "known good" 2.6.15.7,
but I'll report any further findings.
Paul Slootman
next prev parent reply other threads:[~2006-09-06 12:21 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 4:30 Linux v2.6.18-rc5 Linus Torvalds
2006-08-28 5:17 ` Marc Perkel
2006-08-28 5:52 ` Linus Torvalds
2006-08-28 6:13 ` Andi Kleen
2006-08-28 7:24 ` Prakash Punnoor
2006-08-28 12:05 ` Andi Kleen
2006-08-28 12:15 ` Prakash Punnoor
2006-08-28 16:02 ` Andi Kleen
2006-08-28 6:14 ` Andrew Morton
2006-08-28 6:19 ` Olaf Hering
2006-08-28 6:24 ` Andrew Morton
2006-08-28 14:41 ` Shailabh Nagar
2006-08-28 22:01 ` Shailabh Nagar
2006-08-28 6:29 ` Jeff Garzik
2006-08-28 7:25 ` Andi Kleen
2006-08-28 8:08 ` Thomas Gleixner
2006-08-28 17:20 ` Andrew Morton
2006-08-28 17:45 ` Thomas Gleixner
2006-08-28 8:05 ` Catalin Marinas
2006-08-28 8:25 ` Catalin Marinas
2006-08-28 8:34 ` Keith Owens
2006-08-28 8:42 ` Tejun Heo
2006-08-28 15:24 ` Keith Owens
2006-09-03 6:10 ` Tejun Heo
2006-09-06 6:42 ` Keith Owens
2006-09-13 14:41 ` Tejun Heo
2006-09-15 7:40 ` Keith Owens
2006-08-28 8:53 ` Beschorner Daniel
2006-08-28 15:26 ` Dmitry Torokhov
2006-08-29 2:01 ` Greg KH
2006-08-29 2:01 ` Greg KH
2006-08-29 14:50 ` Andreas Barth
2006-08-29 15:57 ` Brice Goglin
2006-08-30 15:54 ` Andrew Benton
2006-08-30 16:15 ` Takashi Iwai
2006-08-31 8:22 ` Takashi Iwai
2006-08-31 5:14 ` Len Brown
2006-09-02 1:40 ` Elias Holman
2006-09-02 1:50 ` Jeff Garzik
2006-08-28 10:10 ` Jesper Juhl
2006-08-28 10:27 ` Kasper Sandberg
2006-08-28 10:35 ` Jesper Juhl
2006-08-28 22:36 ` Nathan Scott
2006-08-28 23:30 ` Jesper Juhl
2006-08-30 8:14 ` Kasper Sandberg
2006-08-30 9:19 ` Jesper Juhl
2006-08-30 13:43 ` Jesper Juhl
2006-09-06 12:21 ` Paul Slootman [this message]
2006-08-28 13:04 ` Roger Luethi
2006-08-29 11:55 ` Olaf Hering
2006-08-29 13:06 ` Nathan Lynch
2006-08-29 13:06 ` Nathan Lynch
2006-08-29 15:26 ` Yves-Alexis Perez
2006-08-29 15:52 ` Olaf Hering
2006-08-29 15:52 ` Olaf Hering
2006-08-30 6:13 ` Paul Mackerras
2006-08-30 6:13 ` Paul Mackerras
2006-08-30 8:05 ` Olaf Hering
2006-08-30 8:05 ` Olaf Hering
2006-08-30 9:00 ` Mikael Pettersson
2006-08-30 9:00 ` Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2006-08-28 9:50 Chuck Ebbert
2006-08-28 18:40 ` Andrew Morton
2006-08-28 18:43 ` Arjan van de Ven
2006-08-29 5:36 Chuck Ebbert
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='edmefq$96n$1@news.cistron.nl' \
--to=paul+nospam@wurtel.net \
--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.