From: Johannes Berg <johannes@sipsolutions.net>
To: Gaudenz Steinlin <gaudenz@soziologie.ch>
Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: filesystem corruption on xfs after 2.6.25-rc1 (bisected, powerpc related?)
Date: Mon, 25 Feb 2008 12:34:27 +0100 [thread overview]
Message-ID: <1203939267.13162.93.camel@johannes.berg> (raw)
In-Reply-To: <20080225112310.GA5516@soziologie.ch>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
Hi,
> Git reset is just the easiest way to reproduce it.
Interesting :)
> I was able to track this corruption down to commit
> a69b176df246d59626e6a9c640b44c0921fa4566 ([XFS] Use the generic bitops
> rather than implementing them ourselves.) using git bisect.
>
> Reverting edd319dc527733e61eec5bdc9ce20c94634b6482 ([XFS] Fix
> xfs_lowbit64) to avoid merge conflicts and the faulty commit on top of
> 2.6.25-rc3 fixes the problem.
Odd. The replaced code doesn't look like it has any sort of endianness
assumptions.
> My filesystem is on an LVM2 logical volume and my computer is a
> PowerBook G4 (model 5,8). I'm using GCC 4.2.3.
>
> My problem is similar to the problem Johannes Berg reported in:
> http://oss.sgi.com/archives/xfs/2008-02/msg00244.html
>
> AFAIK Johannes also uses a PowerBook.
Indeed, I do, forgot to mention that, thanks for copying me.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-02-25 11:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 11:23 Gaudenz Steinlin
2008-02-25 11:34 ` Johannes Berg [this message]
2008-02-25 18:15 ` [xfs-masters] " Eric Sandeen
2008-02-25 23:42 ` Rafael J. Wysocki
2008-02-25 23:48 ` Eric Sandeen
2008-02-25 23:52 ` Rafael J. Wysocki
2008-02-25 23:57 ` [xfs-masters] " Christoph Hellwig
2008-02-26 0:13 ` Rafael J. Wysocki
2008-02-26 7:34 ` Gaudenz Steinlin
2008-02-26 11:44 ` Gaudenz Steinlin
2008-02-26 18:11 ` Johannes Berg
2008-02-28 14:40 ` Eric Sandeen
2008-02-26 20:05 ` Eric Sandeen
2008-02-26 20:59 ` Mark Goodwin
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=1203939267.13162.93.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=gaudenz@soziologie.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®