| To: | "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | stripe unit/width, inode64, misc mkfs.xfs params |
| From: | Peter Merelis <merelis@xxxxxxxxxxxx> |
| Date: | Fri, 30 Apr 2010 09:49:05 -0700 |
| Accept-language: | en-US |
| Acceptlanguage: | en-US |
| Thread-index: | AcrohOx3sEBRKE+wSDiI10yHYj7RkQ== |
| Thread-topic: | stripe unit/width, inode64, misc mkfs.xfs params |
Hi, Apologies in advance as I imagine this issue is raised frequently, but can someone familiar with these sorts of things sanity check my stripe unit/width settings since the underlying storage controller is not exposing the data to mkfs.xfs apparently: 12 disk raid6 256k stripe su=256k sw=10 …which I believe is equivalent to: sunit=512 swidth=5120 Is that correct? Also, does the inode64 option make sense for a filesystem with only a few files, each around ~100G? And finally, are 'allocsize=1GB,nobarrier,noatime,nodiratime' recommended mount options? Thanks, Peter |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH V2] xfs: be more explicit if RT mount fails due to config, Christoph Hellwig |
|---|---|
| Next by Date: | Re: Building XFSDump but missing uuid development package, Eric Sandeen |
| Previous by Thread: | Building XFSDump but missing uuid development package, Peter Shuere |
| Next by Thread: | Re: stripe unit/width, inode64, misc mkfs.xfs params, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |