All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jake Maciejewski <maciejej@msoe.edu>
To: Alex Zarochentsev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 on PPC
Date: Mon, 02 May 2005 10:59:04 -0500	[thread overview]
Message-ID: <1115049544.6385.20.camel@gentoo> (raw)
In-Reply-To: <20050502141026.GA6067@backtop.namesys.com>

On Mon, 2005-05-02 at 18:10 +0400, Alex Zarochentsev wrote:
> Hi,
> 
> On Sun, May 01, 2005 at 12:03:13PM -0500, Jake Maciejewski wrote:
> > Now that reiser4 seems to be working on AMD64, I'm trying to test it on
> > PPC. Unfortunately, I haven't even been able to mount a reiser4 FS.
> 
> Unfortunately we could not test reiser4 on PPC because of lack of test machine.
> Currently no idea where it might fail.
> 
> > I get the following error: "mount: No such file or directory". I've
> > tried a loopback filesystem and a native partition. The same native
> > patition works when formatted with reiserFS. I've tried the code as a
> > module and builtin. I was using reiser4progs 1.0.4 and the latest -mm
> > patch on vanilla, which while not officially supported works on AMD64
> > and x86 and shouldn't cause a problem like this. fsck.reiser4 says the
> > unmountable filesystem is consistent. Is there anything else I should
> > try?
> 
> can you look at your machine /var/log/messages or dmesg(8) output for reiser4
> messages?

Well, now that I've actually checked it, there is a warning. I get the
same message regardless of the architecture the FS is created on.

reiser4[mount(22352)]: key_warning
(fs/reiser4/plugin/object.c:96)[nikita-717]:
WARNING: Error for inode 720575940379279360 (-2)

This is a clean, consistent filesystem we're talking about, so I guess
it's a kernel problem. Is it worth trying a different kernel version?
I'm trying to avoid -mm because it sometimes breaks alternative
architectures, but I wanted the lastest version of the code. As I
mentioned before, I used a cutsom patch that works on x86. I'm willing
to try other versions if necessary.

> 
> If you have possibility to check the fs by an fsck.reiser4 compiled on i386,
> please do it.  If you don't have i386 around or have no time to compile the
> progs there, make a small file with reiser4 fs image , compress it and make it
> downloadable.
> 
> > 
> > -- 
> > Jake Maciejewski <maciejej@msoe.edu>
> > 
> 
> Thanks in advance,
> Alex.
> 
-- 
Jake Maciejewski <maciejej@msoe.edu>


  parent reply	other threads:[~2005-05-02 15:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-01 17:03 reiser4 on PPC Jake Maciejewski
2005-05-02 14:10 ` Alex Zarochentsev
2005-05-02 15:34   ` Jake Maciejewski
2005-05-02 15:59   ` Jake Maciejewski [this message]
2005-05-02 16:11     ` Boyd Waters
2005-05-02 19:14   ` Boyd Waters
2005-05-03 13:31     ` mjt
2005-05-03 16:31       ` Adrian Ulrich
2005-05-03 17:21         ` mjt
2005-05-03 18:25         ` Hans Reiser
2005-05-03 21:25           ` Jake Maciejewski

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=1115049544.6385.20.camel@gentoo \
    --to=maciejej@msoe.edu \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@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.