All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: Marc Dietrich <Marc.Dietrich@ap.physik.uni-giessen.de>
Cc: Barry Naujok <bnaujok@sgi.com>, xfs@oss.sgi.com
Subject: Re: filesystem corruption in linus tree
Date: Mon, 03 Mar 2008 15:23:46 +1100	[thread overview]
Message-ID: <47CB7D52.2030704@sgi.com> (raw)
In-Reply-To: <200802262100.18631.marc.dietrich@ap.physik.uni-giessen.de>

Marc Dietrich wrote:
> Hi again,
> 
> On Tuesday 26 February 2008 08:38:50 Lachlan McIlroy wrote:
>> Marc Dietrich wrote:
>>> Hi,
>>>
>>> On Monday 25 February 2008 01:36:28 Barry Naujok wrote:
>>>> On Sun, 24 Feb 2008 20:58:26 +1100, Marc Dietrich
>>>>
>>>> <Marc.Dietrich@ap.physik.uni-giessen.de> wrote:
>>>>> Hi,
>>>>>
>>>>> somewhere after the release of 2.6.24 my xfs filesystem got corrupted.
>>>>> Initialy I thought it was only related to the readdir bug.
>>>>> (http://oss.sgi.com/archives/xfs/2008-02/msg00027.html) So I waited for
>>>>> the fix to go into mainline. Yesterday I tried again, but got this
>>>>> error during boot:
> 
> <sniped>
> 
>> We've had a few problems reported with XFS on 32-bit powermacs and the
>> culprit appears to be some changes to bit manipulation routines.  Could you
>> please try reverse applying the attached patches and see if the problem is
>> resolved?
> 
> I saw, that you already pushed it into mainline - for a good reason ;-) Works 
> as expeted.
> 
> Please also don't forget 2.6.24-stable !

The changes that caused this regression went into 2.6.25-rc1 so no need for a
2.6.24 stable fix.

  reply	other threads:[~2008-03-03  4:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24  9:58 filesystem corruption in linus tree Marc Dietrich
2008-02-25  0:36 ` Barry Naujok
2008-02-25 22:47   ` Marc Dietrich
2008-02-26  7:38     ` Lachlan McIlroy
2008-02-26 20:00       ` Marc Dietrich
2008-03-03  4:23         ` Lachlan McIlroy [this message]
2008-03-05  8:33           ` Marc

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=47CB7D52.2030704@sgi.com \
    --to=lachlan@sgi.com \
    --cc=Marc.Dietrich@ap.physik.uni-giessen.de \
    --cc=bnaujok@sgi.com \
    --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.