| To: | James Braid <jamesb@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Default mount options (that suck less). |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 31 Oct 2007 10:21:25 -0500 |
| Cc: | Timothy Shimmin <tes@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <177CA06B-41D3-4E4A-9EA6-5688C952CD63@loreland.org> |
| References: | <20071029075657.GA84369978@melbourne.sgi.com> <4725FBB4.1010400@sandeen.net> <47267EC7.8000906@sgi.com> <177CA06B-41D3-4E4A-9EA6-5688C952CD63@loreland.org> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.6 (Macintosh/20070728) |
James Braid wrote: > On 30 Oct 2007, at 00:45, Timothy Shimmin wrote: >> It might be interesting if people let us know what non-default >> mkfs and mount options that they are using for their various >> configurations/classes. >> Didn't Russell C. have some survey years ago - can't remember if >> that was for h/ware or what now. > > We have a ~100TB filesystem that was made with the default mkfs.xfs > options from memory. The only mount option we use is inode64. Hm, which has been another pet peeve of mine; shouldn't inode64 flag the SB when the first >32bit inode is created? It always bothered me that inode64 was a mount option which appears to be something you could turn back off, even though there may be >32bit inodes on disk already. -Eric |
| Previous by Date: | Re: Default mount options (that suck less)., Justin Piszcz |
|---|---|
| Next by Date: | Re: Default mount options (that suck less)., Chris Wedgwood |
| Previous by Thread: | Re: Default mount options (that suck less)., James Braid |
| Next by Thread: | Re: Default mount options (that suck less)., Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |