public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com, aurfalien <aurfalien@gmail.com>
Subject: Re: specify agsize?
Date: Sun, 14 Jul 2013 17:08:04 -0500	[thread overview]
Message-ID: <51E32144.3020109@hardwarefreak.com> (raw)
In-Reply-To: <51E2CE83.9080003@sandeen.net>

On 7/14/2013 11:14 AM, Eric Sandeen wrote:

> http://wikihelp.autodesk.com/Creative_Finishing/enu/2012/Help/05_Installation_Guides/Installation_and_Configuration_Guide_for_Linux_Workstations/0118-Advanced118/0194-Manually194/0199-Creating199
> 
> I guess?
> 
> That's quite a procedure!  And I have to say, a slightly strange one at first glance.

Agreed.

> It'd be nice if they said what they were trying to accomplish rather than just giving you a long recipe.

Again.

> In the end, I think they are trying to create 128AGs and maybe work around some mkfs corner case or other.

Or it's just as likely they are laying out these image frames in a
specific manner across 128 directories, assuming 128 AGs exist, to
achieve some specific "on disk" organization of the files.  It's simply
not possible to know without more information.

Interestingly, on a 14+2 RAID6 array of 7.2K drives, normally 128 AGs
will decrease parallel performance due to a huge increase in head seek
latency.  Thus I'd assume this isn't a parallel workload.  Either that
or Autodesk doesn't know XFS as well as they believe.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-07-14 22:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-14  0:11 specify agsize? aurfalien
2013-07-14  2:13 ` Eric Sandeen
2013-07-14  4:20   ` aurfalien
2013-07-14  7:06     ` Stan Hoeppner
2013-07-14 16:56       ` aurfalien
2013-07-15  1:07       ` Dave Chinner
2013-07-14 16:14     ` Eric Sandeen
2013-07-14 16:46       ` aurfalien
2013-07-14 17:14       ` aurfalien
2013-07-15  1:22         ` Dave Chinner
2013-07-14 22:08       ` Stan Hoeppner [this message]
2013-07-14 22:42         ` aurfalien
2013-07-14 23:43           ` Stan Hoeppner
  -- strict thread matches above, loose matches on Subject: below --
2013-07-14 19:45 Richard Scobie
2013-07-14 22:18 ` aurfalien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51E32144.3020109@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=aurfalien@gmail.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox