linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: xfs@oss.sgi.com, Alan Piszcz <ap@solarrain.com>,
	linux-raid@linux-kernel.vger.kernel.org
Subject: Re: XFS on x86_64 Linux Question
Date: Sat, 28 Apr 2007 12:41:42 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704281241100.11586@p34.internal.lan> (raw)
In-Reply-To: <p73lkgc1k2s.fsf@bingen.suse.de>



On Sat, 28 Apr 2007, Andi Kleen wrote:

> Justin Piszcz <jpiszcz@lucidpixels.com> writes:
>
>> Had a quick question, if I re-provision a host with an Intel Core Duo
>> CPU with x86_64 Linux; I create a software raid array and use the XFS
>> filesystem-- all in 64bit space...
>>
>> If I boot a recovery image such as Knoppix, it will not be able to
>> work on the filesystem correct?  I would need a 64bit live CD?
>
> There used to be a XFS bug that 32bit journals couldn't
> be replayed on 64bit and vice versa. This means you couldn't mount
> a dirty file system on the other architecture. But this bug has been
> long fixed and mounting clean file systems always worked.
>
> -Andi
>

Thanks for the prompt reply!  I have more confidence in trying x86_64 now 
:)

Justin.

  reply	other threads:[~2007-04-28 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-28 10:35 XFS on x86_64 Linux Question Justin Piszcz
2007-04-28 10:36 ` Justin Piszcz
2007-04-28 11:57   ` Raz Ben-Jehuda(caro)
2007-04-28 12:09     ` Justin Piszcz
2007-04-28 17:32 ` Andi Kleen
2007-04-28 16:41   ` Justin Piszcz [this message]
     [not found] <H00000680010301f.1177756626.www.korstad.net@MHS>
2007-04-28 14:53 ` Daniel Korstad

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=Pine.LNX.4.64.0704281241100.11586@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=andi@firstfloor.org \
    --cc=ap@solarrain.com \
    --cc=linux-raid@linux-kernel.vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).