* stripe unit/width, inode64, misc mkfs.xfs params
@ 2010-04-30 16:49 Peter Merelis
2010-04-30 17:33 ` Eric Sandeen
0 siblings, 1 reply; 2+ messages in thread
From: Peter Merelis @ 2010-04-30 16:49 UTC (permalink / raw)
To: xfs@oss.sgi.com
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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: stripe unit/width, inode64, misc mkfs.xfs params
2010-04-30 16:49 stripe unit/width, inode64, misc mkfs.xfs params Peter Merelis
@ 2010-04-30 17:33 ` Eric Sandeen
0 siblings, 0 replies; 2+ messages in thread
From: Eric Sandeen @ 2010-04-30 17:33 UTC (permalink / raw)
To: Peter Merelis; +Cc: xfs@oss.sgi.com
Peter Merelis wrote:
> 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
sounds right
> …which I believe is equivalent to:
>
> sunit=512
> swidth=5120
>
> Is that correct?
probably, but FWIW su/sw might be easier since it deals in byte / multiplier units.
> Also, does the inode64 option make sense for a filesystem with only a few files, each around ~100G?
for a large filesystem, yes, if your userspace can cope.
> And finally, are 'allocsize=1GB,nobarrier,noatime,nodiratime' recommended mount options?
no mount options are recommended without more information about the load ;)
nobarrier is only recommended if the storage has a battery-backed cache (or no cache)
allocsize=1GB is probably ok if you really are only writing large files and have
fragmentation problems
noatime,nodiratime probably don't matter much at all.
-Eric
> Thanks,
> Peter
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-30 17:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-30 16:49 stripe unit/width, inode64, misc mkfs.xfs params Peter Merelis
2010-04-30 17:33 ` Eric Sandeen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox