From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.22-rc3 safe to migrate to?
Date: Sat, 02 Jun 2007 15:54:09 -0700 [thread overview]
Message-ID: <4661F511.4070207@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0706021723480.22318@p34.internal.lan>
Justin Piszcz wrote:
> Wondering as their were a lot of XFS related issues early on in
> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch
> by ruik which I want be running as long as 2.6.22-rc3 does not have
> any severe XFS issues?
XFS currently has a data-corrupting bug, where files which were appended
by small amounts may lose their updates on umount - I see this
corrupting hg repos. There's a patch which works for me, and is in
2.6.22-rc3-mm1, but it hasn't been merged upstream yet.
J
next prev parent reply other threads:[~2007-06-02 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-02 21:24 Kernel 2.6.22-rc3 safe to migrate to? Justin Piszcz
2007-06-02 21:59 ` Christian Kujau
2007-06-02 22:09 ` Justin Piszcz
2007-06-02 22:27 ` Justin Piszcz
2007-06-02 22:54 ` Jeremy Fitzhardinge [this message]
2007-06-02 22:55 ` Justin Piszcz
2007-06-03 0:25 ` Christian Kujau
2007-06-03 0:27 ` Justin Piszcz
2007-06-03 6:30 ` Jeremy Fitzhardinge
2007-06-03 7:59 ` Michal Piotrowski
2007-06-03 8:02 ` Jeremy Fitzhardinge
2007-06-03 8:41 ` Justin Piszcz
[not found] <fa.eE9c0s9eXX/aO2N8hiu3e2Yehz8@ifi.uio.no>
[not found] ` <fa.hq4JzIoUe01l8ywIZPkqjocRBmc@ifi.uio.no>
[not found] ` <fa.3aN+T/xQVA3sf9DdMPLOfUVmYA0@ifi.uio.no>
[not found] ` <fa.mJ71j4nyi6ALIkQjLcpIJtTbVVI@ifi.uio.no>
[not found] ` <fa.vxJKq726YMWJY2i/waKQsNec3aU@ifi.uio.no>
2007-06-03 6:23 ` Robert Hancock
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=4661F511.4070207@goop.org \
--to=jeremy@goop.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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.