All of lore.kernel.org
 help / color / mirror / Atom feed
From: "René Rebe" <rene@rocklinux-consulting.de>
To: Joshua Kwan <joshk@triplehelix.org>
Cc: reiserfs-list@namesys.com
Subject: Re: [2.6.8] Strange FS corruption on sparc64
Date: Sat, 21 Aug 2004 11:05:10 +0200	[thread overview]
Message-ID: <41271046.7020309@rocklinux-consulting.de> (raw)
In-Reply-To: <20040821000112.GM8070@triplehelix.org>

Hi,

Joshua Kwan wrote:

> I've been tasking my UP sparc64 for a few days now to build lots of
> kernels for Debian. However, during the build, it must have stumbled
> across some inconsistency in my reiser3 filesystem:

Interesting - I tried to use ReiserFS on my (UltraSPARC) SPARC, too. But 
at that time the reiserfsprogs did not liked to be compiled on sparc(32) 
due to the usage of kernel headers for bit operations and those are 
implemented in software on sparc32. Are the tools fixed in the meantime? 
Or do you use a 64bit only userspace version of the reiserfstools?

   René

      reply	other threads:[~2004-08-21  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21  0:01 [2.6.8] Strange FS corruption on sparc64 Joshua Kwan
2004-08-21  9:05 ` René Rebe [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=41271046.7020309@rocklinux-consulting.de \
    --to=rene@rocklinux-consulting.de \
    --cc=joshk@triplehelix.org \
    --cc=reiserfs-list@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.