| To: | Steve Lord <lord@xxxxxxx> |
|---|---|
| Subject: | Re: Opteron Systems |
| From: | Tim Shimmin <tes@xxxxxxx> |
| Date: | Mon, 27 Jun 2005 13:37:50 +1000 |
| Cc: | Joshua Schmidlkofer <kernel@xxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <42BBF5A1.3000502@xxxxxxx>; from lord@xxxxxxx on Fri, Jun 24, 2005 at 06:59:29AM -0500 |
| References: | <42BB8C44.2010303@xxxxxxxxxxxxxx> <42BBF5A1.3000502@xxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
On Fri, Jun 24, 2005 at 06:59:29AM -0500, Steve Lord wrote: > 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 inode64 option. > > Thanks, Joshua > > If your filesystems are 1 Tbyte or larger then yes, otherwise it > does not really make any difference. You can enable this at any point, > > once you have done it though, the inodes will be out there and > you cannot get rid of them. > 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Opteron Systems, Steve Lord |
|---|---|
| Next by Date: | Re: Questions regarding stack size with RHEL AS 4.0, Eric Sandeen |
| Previous by Thread: | Re: Opteron Systems, Steve Lord |
| Next by Thread: | Re: Opteron Systems, Björn JACKE |
| Indexes: | [Date] [Thread] [Top] [All Lists] |