From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-kernel@vger.kernel.org, "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14)
Date: Thu, 19 Feb 2009 14:12:13 +0100 [thread overview]
Message-ID: <499D5AAD.8060708@aei.mpg.de> (raw)
In-Reply-To: <20090219120158.GA1747@wotan.suse.de>
Hi Nick,
Nick Piggin schrieb:
> I wonder how long you've been running with 2.6.27 based kernels
> without corruption?
Let me see, we upgraded from 2.6.25.9 to 2.6.27.10 in mid January, i.e.
our data base time line is about 6 weeks.
The upgrade to .14 happened about 16 days ago.
HTH
Carsten
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: Nick Piggin <npiggin@suse.de>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14)
Date: Thu, 19 Feb 2009 14:12:13 +0100 [thread overview]
Message-ID: <499D5AAD.8060708@aei.mpg.de> (raw)
In-Reply-To: <20090219120158.GA1747@wotan.suse.de>
Hi Nick,
Nick Piggin schrieb:
> I wonder how long you've been running with 2.6.27 based kernels
> without corruption?
Let me see, we upgraded from 2.6.25.9 to 2.6.27.10 in mid January, i.e.
our data base time line is about 6 weeks.
The upgrade to .14 happened about 16 days ago.
HTH
Carsten
next prev parent reply other threads:[~2009-02-19 13:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 14:49 xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14) Carsten Aulbert
2009-02-17 14:49 ` Carsten Aulbert
2009-02-17 15:19 ` Michael Monnerie
2009-02-17 15:56 ` Carsten Aulbert
2009-02-17 17:24 ` Eric Sandeen
2009-02-17 17:24 ` Eric Sandeen
2009-02-18 9:19 ` Dave Chinner
2009-02-18 9:19 ` Dave Chinner
2009-02-18 9:36 ` Carsten Aulbert
2009-02-18 9:36 ` Carsten Aulbert
2009-02-19 6:19 ` Dave Chinner
2009-02-19 6:19 ` Dave Chinner
2009-02-19 10:13 ` Carsten Aulbert
2009-02-19 10:13 ` Carsten Aulbert
2009-02-19 12:01 ` Nick Piggin
2009-02-19 12:01 ` Nick Piggin
2009-02-19 13:12 ` Carsten Aulbert [this message]
2009-02-19 13:12 ` Carsten Aulbert
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=499D5AAD.8060708@aei.mpg.de \
--to=carsten.aulbert@aei.mpg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--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.