public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Maier <m1278468@allmail.net>
To: stan@hardwarefreak.com
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: Failure growing xfs with linux 3.10.5
Date: Thu, 15 Aug 2013 19:05:41 +0200	[thread overview]
Message-ID: <520D0A65.9060505@allmail.net> (raw)
In-Reply-To: <520C02BE.6060506@hardwarefreak.com>

Stan Hoeppner wrote:
> On 8/14/2013 1:13 PM, Michael Maier wrote:
>> Stan Hoeppner wrote:
>>> If you keep growing until you consume the disk, you'll have ~100
>>> allocation groups.  Typically you'd want to have no more than 4 AGs per
>>> spindle.  You already have 42 (or 45) which will tend to seek the disk
>>> to death with many workloads, driving latency through the roof and
>>> decreasing throughput substantially.  Do you notice any performance
>>> problems yet?
>>
>> What are expected rates for copying e.g. a 10GB file? It's a Seagate
>> Barracuda 3000GB Model ST3000DM001 SATA connected to SATA 6 Gb/s chip.
>> The source and the destination FS is LUKS crypted. About 3 GB usable RAM
>> (cache), AMD FX-8350 processor @ max. 3800MHz.
> 
> Too many variables really to hazard a guess.  If you put a gun to my
> head, I'd say strictly looking at the ingest rate of the Seagate, at a
> little less than half capacity, writing about 1/3rd of the way down the
> platters, optimum throughput should be 80-100 MB/s or so in the last 3
> AGs, if free space isn't too heavily fragmented.

96MB/s / 40GB-file ~ 130GB free space. -> good guess!

[...]

> With so many smallish AGs, so many grow ops, and this backup workload,
> I'm curious as to what your free space map looks like.  Would you mind
> posting the output of the following command, if you can?
> 
> $ xfs_db -r -c freesp <dev>

after copying:
   from      to extents  blocks    pct
      1       1     193     193   0.00
      2       3      31      72   0.00
      4       7      10      60   0.00
      8      15       8      94   0.00
     16      31       9     210   0.00
     32      63      14     631   0.00
     64     127      20    1974   0.01
    128     255      16    2838   0.01
    256     511      12    4923   0.02
    512    1023      13   10065   0.04
   1024    2047      14   23417   0.10
   2048    4095      22   58439   0.25
   4096    8191       8   44159   0.19
   8192   16383       1    8192   0.04
  16384   32767       7  165001   0.71
  32768   65535       6  228278   0.99
 262144  524287       1  398328   1.72
1048576 2097151       2 3560198  15.39
2097152 4194303       1 3709535  16.04
4194304 7700480       2 14909432  64.47


Regards,
Michael.

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

  reply	other threads:[~2013-08-15 17:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11  7:11 Failure growing xfs with linux 3.10.5 Michael Maier
2013-08-11 18:36 ` Eric Sandeen
2013-08-12 16:50   ` Michael Maier
2013-08-13  0:54     ` Dave Chinner
2013-08-13 14:55       ` Michael Maier
2013-08-14  5:43         ` Dave Chinner
2013-08-14 15:16           ` Michael Maier
2013-08-15  0:58             ` Dave Chinner
2013-08-15 18:14               ` Michael Maier
     [not found]   ` <52090C6C.6060604@allmail.net>
2013-08-13  0:04     ` Dave Chinner
2013-08-13 15:30       ` Michael Maier
2013-08-14  5:53         ` Stan Hoeppner
2013-08-14 15:05           ` Michael Maier
2013-08-14 17:31             ` Stan Hoeppner
2013-08-14 18:13               ` Michael Maier
2013-08-14 22:20                 ` Stan Hoeppner
2013-08-15 17:05                   ` Michael Maier [this message]
2013-08-14  6:20         ` Dave Chinner
2013-08-14 16:20           ` Michael Maier
2013-08-14 16:37             ` Eric Sandeen
2013-08-15 17:18             ` Eric Sandeen
2013-08-15 17:55               ` Michael Maier
2013-08-15 18:14                 ` Eric Sandeen
2013-08-15 18:35                   ` Michael Maier
2013-08-15 18:42                     ` Eric Sandeen
2013-08-14 16:51           ` Eric Sandeen

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=520D0A65.9060505@allmail.net \
    --to=m1278468@allmail.net \
    --cc=sandeen@sandeen.net \
    --cc=stan@hardwarefreak.com \
    --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