All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Fischer <Christian.Fischer@easterngraphics.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Lyon <andrew.lyon@gmail.com>,
	Eric Sandeen <sandeen@sandeen.net>,
	xfs@oss.sgi.com
Subject: Re: xfs crash, kernel 2.6.29
Date: Tue, 11 Aug 2009 16:39:28 +0200	[thread overview]
Message-ID: <200908111639.28786.Christian.Fischer@easterngraphics.com> (raw)
In-Reply-To: <20090811142029.GB30913@infradead.org>

On Tuesday 11 August 2009, Christoph Hellwig wrote:
> On Tue, Aug 11, 2009 at 09:21:50AM +0200, Christian Fischer wrote:
> > We had a new crash yesterday, server uptime maybe 20 hours.
> >
> > This is 2.6.29-xen-r4 from
> > http://code.google.com/p/gentoo-xen-kernel/downloads/list
> >
> > @Eric/Andrew: do we have a xfs or a xen patches problem?
>
> It's a known bug that we just fixed in 2.6.31-rc.  Can you check if this
> patch
>
> 	http://bugzilla.kernel.org/attachment.cgi?id=22590
>
> applies to 2.6.29 (I produced it against 2.6.30)

Yes, I've seen this after sending my first mail.

If there are no patches against 2.6.29 then i have no other chance than trying 
this, or i switch to ext4. But what happens then?

What a bullshit, from one bug to the next, my company kills me.

Thanks for all comments and help.
Christian

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-08-11 14:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11  7:21 xfs crash, kernel 2.6.29 Christian Fischer
2009-08-11  8:09 ` Christian Fischer
2009-08-11 14:20 ` Christoph Hellwig
2009-08-11 14:39   ` Christian Fischer [this message]
2009-08-14 12:56   ` [Patch] " Christian Fischer
2009-08-14 14:18     ` Christoph Hellwig
2009-08-19  7:50       ` Andrew Lyon
2009-08-19  8:16         ` Christian Fischer
2009-08-14 13:02   ` Christian Fischer

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=200908111639.28786.Christian.Fischer@easterngraphics.com \
    --to=christian.fischer@easterngraphics.com \
    --cc=andrew.lyon@gmail.com \
    --cc=hch@infradead.org \
    --cc=sandeen@sandeen.net \
    --cc=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.