Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Opteron\s+Systems\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Opteron\s+Systems\s*$/: 12 ]

Total 12 documents matching your query.

1. Opteron Systems (score: 1): Author: Joshua Schmidlkofer <kernel@xxxxxxxxxxxxxx>; Date: Thu, 23 Jun 2005 21:29:56 -0700; Should I be using the inode64 option on my Opteron and EMT64 systems? I am using Gentoo amd64 stuff, so everything is build 64bit, I just wondered if I should be using the inode64 option. Thanks, Jos; /archives/xfs/2005-06/msg00136.html (7,009 bytes)
2. Re: Opteron Systems (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Fri, 24 Jun 2005 06:59:29 -0500; Joshua Schmidlkofer wrote: Should I be using the inode64 option on my Opteron and EMT64 systems? I am using Gentoo amd64 stuff, so everything is build 64bit, I just wondered if I should be using the; /archives/xfs/2005-06/msg00138.html (8,043 bytes)
3. Re: Opteron Systems (score: 1): Author: Tim Shimmin <tes@xxxxxxx>; Date: Mon, 27 Jun 2005 13:37:50 +1000; On IRIX we do have xfs_reno(1M) which can renumber inodes by swaping extents, copying dirents, copying EAs etc...(relies on XFS to allocate new inode). However, it is not ported to Linux. --Tim; /archives/xfs/2005-06/msg00139.html (8,437 bytes)
4. Re: Opteron Systems (score: 1): Author: Björn JACKE <bj@xxxxxxxxx; Date: Tue, 28 Jun 2005 11:28:06 +0200; On 2005-06-27 at 13:37 +1000 Tim Shimmin sent off: is the sourcecode available so that doing a linux port is possible or would this have to be done from scratch? Bjoern -- Björn Jacke, SerNet Servi; /archives/xfs/2005-06/msg00145.html (8,415 bytes)
5. Re: Opteron Systems (score: 1): Author: Tim Shimmin <tes@xxxxxxx>; Date: Thu, 30 Jun 2005 11:32:03 +1000; Hi Bjoern, The source code would need to be reviewed first. What need has arisen for you such that you want xfs_reno? Cheers, --Tim; /archives/xfs/2005-06/msg00158.html (8,511 bytes)
6. RE: Opteron Systems (score: 1): Author: "Mike Gigante" <mg@xxxxxxx>; Date: Thu, 30 Jun 2005 11:51:36 +1000; There are no plans to provide xfs_reno on Linux. The principal reason for xfs_reno was to deal with legacy Irix XFS filesystems that were created before inode32 was available. Mike; /archives/xfs/2005-06/msg00159.html (8,009 bytes)
7. Opteron Systems (score: 1): Author: Joshua Schmidlkofer <kernel@xxxxxxxxxxxxxx>; Date: Thu, 23 Jun 2005 21:29:56 -0700; Should I be using the inode64 option on my Opteron and EMT64 systems? I am using Gentoo amd64 stuff, so everything is build 64bit, I just wondered if I should be using the inode64 option. Thanks, Jos; /archives/xfs/2005-06/msg00308.html (7,009 bytes)
8. Re: Opteron Systems (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Fri, 24 Jun 2005 06:59:29 -0500; Joshua Schmidlkofer wrote: Should I be using the inode64 option on my Opteron and EMT64 systems? I am using Gentoo amd64 stuff, so everything is build 64bit, I just wondered if I should be using the; /archives/xfs/2005-06/msg00310.html (8,043 bytes)
9. Re: Opteron Systems (score: 1): Author: Tim Shimmin <tes@xxxxxxx>; Date: Mon, 27 Jun 2005 13:37:50 +1000; On IRIX we do have xfs_reno(1M) which can renumber inodes by swaping extents, copying dirents, copying EAs etc...(relies on XFS to allocate new inode). However, it is not ported to Linux. --Tim; /archives/xfs/2005-06/msg00311.html (8,437 bytes)
10. Re: Opteron Systems (score: 1): Author: Björn JACKE <bj@xxxxxxxxx; Date: Tue, 28 Jun 2005 11:28:06 +0200; On 2005-06-27 at 13:37 +1000 Tim Shimmin sent off: is the sourcecode available so that doing a linux port is possible or would this have to be done from scratch? Bjoern -- Björn Jacke, SerNet Servi; /archives/xfs/2005-06/msg00317.html (8,415 bytes)
11. Re: Opteron Systems (score: 1): Author: Tim Shimmin <tes@xxxxxxx>; Date: Thu, 30 Jun 2005 11:32:03 +1000; Hi Bjoern, The source code would need to be reviewed first. What need has arisen for you such that you want xfs_reno? Cheers, --Tim; /archives/xfs/2005-06/msg00330.html (8,511 bytes)
12. RE: Opteron Systems (score: 1): Author: "Mike Gigante" <mg@xxxxxxx>; Date: Thu, 30 Jun 2005 11:51:36 +1000; There are no plans to provide xfs_reno on Linux. The principal reason for xfs_reno was to deal with legacy Irix XFS filesystems that were created before inode32 was available. Mike; /archives/xfs/2005-06/msg00331.html (8,009 bytes)

Current List: 1 - 12
Page: [1]