So I am having trouble fixing a corrupted <16 TB file system on a 32bit Linux The problem is that xfs_repair dies due to xfs_repair: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory:
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
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
Yes the log died and was zeroed already with xfs_repair already. So I plan to put a 64bit head on the volumes and leave it that way. I asuume I need to still keep it under 16 tb since the fs datastu
All XFS data structures (which matter for this) are 64bit. But the pagecache size in 32bit x86 systems is indeeed limited, so a larger filesystem won't work there.
Actually there used to be some bugs in old versions where 32bit couldn't replay 64bit logs or vice versa. Probably all fixed in uptodate kernels. -Andi
On Tue, 10 Jun 2008 22:07:18 +1000, Lance Reed <lreed@xxxxxxxxxxxxxx> 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
So I am having trouble fixing a corrupted <16 TB file system on a 32bit Linux The problem is that xfs_repair dies due to xfs_repair: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate memory:
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
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
Yes the log died and was zeroed already with xfs_repair already. So I plan to put a 64bit head on the volumes and leave it that way. I asuume I need to still keep it under 16 tb since the fs datastu
All XFS data structures (which matter for this) are 64bit. But the pagecache size in 32bit x86 systems is indeeed limited, so a larger filesystem won't work there.
Actually there used to be some bugs in old versions where 32bit couldn't replay 64bit logs or vice versa. Probably all fixed in uptodate kernels. -Andi
On Tue, 10 Jun 2008 22:07:18 +1000, Lance Reed <lreed@xxxxxxxxxxxxxx> 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
So I am having trouble fixing a corrupted <16 TB file system on a 32bit Linux system: The problem is that xfs_repair dies due to xfs_repair: libxfs_initbuf can't memalign 4096 bytes: Cannot allocate
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
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
Thanks! Yes the log died and was zeroed already with xfs_repair already. So I plan to put a 64bit head on the volumes and leave it that way. I asuume I need to still keep it under 16 tb since the fs
All XFS data structures (which matter for this) are 64bit. But the pagecache size in 32bit x86 systems is indeeed limited, so a larger filesystem won't work there.
Actually there used to be some bugs in old versions where 32bit couldn't replay 64bit logs or vice versa. Probably all fixed in uptodate kernels. -Andi