| To: | Lance Reed <lreed@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Probems with xfs_repair on large filesystem and 32bit OS. |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 10 Jun 2008 08:28:11 -0400 |
| Cc: | Tru Huynh <tru@xxxxxxxxxx>, "'xfs@xxxxxxxxxxx'" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <6A32BC807C106440B7E23208F280DDAF01D3F6C8B4@bcmail1.VIDMARK.LOCAL> |
| References: | <6A32BC807C106440B7E23208F280DDAF01D3F6C8A8@bcmail1.VIDMARK.LOCAL> <20080610115038.GD3005@sillage.bis.pasteur.fr> <6A32BC807C106440B7E23208F280DDAF01D3F6C8B4@bcmail1.VIDMARK.LOCAL> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [XFS] oss.sgi, Christoph Hellwig |
|---|---|
| Next by Date: | Re: Probems with xfs_repair on large filesystem and 32bit OS., Lance Reed |
| Previous by Thread: | RE: Probems with xfs_repair on large filesystem and 32bit OS., Lance Reed |
| Next by Thread: | Re: Probems with xfs_repair on large filesystem and 32bit OS., Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |