public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Lance Reed <lreed@brightcove.com>
Cc: Tru Huynh <tru@pasteur.fr>, "'xfs@oss.sgi.com'" <xfs@oss.sgi.com>
Subject: Re: Probems with xfs_repair on large filesystem and 32bit OS.
Date: Tue, 10 Jun 2008 08:28:11 -0400	[thread overview]
Message-ID: <20080610122811.GB15871@infradead.org> (raw)
In-Reply-To: <6A32BC807C106440B7E23208F280DDAF01D3F6C8B4@bcmail1.VIDMARK.LOCAL>

On Tue, Jun 10, 2008 at 08:07:18AM -0400, Lance Reed wrote:
> SO, I take it from what you say that that I can running any newer version of xfs progs and a 64bit host (fiber attached, easy to do this), and run xfs_repair on the 32bit XFS volumes without fear of data corruption?
> Is this because XFS is not version specific, and xfs_repair will honor the 32bit file data structures?

Yes, this is fine.  All the actual filesystem structures are endian and
32/64bit clean.  The log needs to be in the same endianess and had 32bit
vs 64bit problems on x86 for a while, but it needs to be recovered
before you run xfs_repair anyway.

  reply	other threads:[~2008-06-10 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 11:28 Probems with xfs_repair on large filesystem and 32bit OS Lance Reed
     [not found] ` <20080610115038.GD3005@sillage.bis.pasteur.fr>
2008-06-10 12:07   ` Lance Reed
2008-06-10 12:28     ` Christoph Hellwig [this message]
2008-06-10 17:07       ` Andi Kleen
2008-06-11  0:01     ` Barry Naujok
  -- strict thread matches above, loose matches on Subject: below --
2008-06-10 12:50 Lance Reed
2008-06-10 13:01 ` 'hch@infradead.org'

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=20080610122811.GB15871@infradead.org \
    --to=hch@infradead.org \
    --cc=lreed@brightcove.com \
    --cc=tru@pasteur.fr \
    --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