All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Paavo Hartikainen <pahartik@sci.fi>,
	reiserfs-list@namesys.com, Vladimir Saveliev <vs@namesys.com>
Subject: Re: Still unable to use ReiserFS on PowerPC [Oops]
Date: Tue, 14 Sep 2004 09:20:38 +0200	[thread overview]
Message-ID: <41469BC6.1010104@fh-landshut.de> (raw)
In-Reply-To: <4146201F.5080808@suse.com>

Hello,

I guess my problem is similar, though I cannot quite verify that.

I'm having a problem exporting Reiser4 over NFS, and Vladimir thought it 
possible that the problem has been rooted in endianness. He sent me a patch that 
tries to expose the problem, and one of the cases got fired.

Maybe you could both talk - I mean Paavo and Vladimir - coordinate about the 
problem, since I'm not in a position to help you beyond having a workstation and 
embedded PowerPC targets, where I can test things.

With kind regards,
Oliver Korpilla

Jeff Mahoney wrote:
> Paavo Hartikainen wrote:
> | On PowerPC, I have never got ReiserFS working.  It breaks apart when
> | trying to copy contents to ReiserFS from existing Ext3 filesystem.  I
> | tried this about one year ago (PowerPC 603e, latest Linux 2.4 kernel
> | back then), and now again (PowerPC 604e, Linux 2.4.27 kernel) with
> | same results.
> 
> As the original author of the endian safeness patches, this report
> concerns me. This code has been in the kernel for a few years now, and
> is considered quite stable. I've tried reproducing on my iBook, and
> could not. Though, 2.4.27 won't even boot on my dual g4 powermac.
> 
> Do you always get an Oops in the same path?
> - -Jeff

      reply	other threads:[~2004-09-14  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 22:45 Still unable to use ReiserFS on PowerPC [Oops] Paavo Hartikainen
2004-09-13 22:33 ` Jeff Mahoney
2004-09-14  7:20   ` Oliver Korpilla [this message]

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=41469BC6.1010104@fh-landshut.de \
    --to=okorpil@fh-landshut.de \
    --cc=jeffm@suse.com \
    --cc=pahartik@sci.fi \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@namesys.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.