From: Stefan Priebe <s.priebe@profihost.ag>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs@oss.sgi.com
Subject: Re: xfs_growfs / planned resize / performance impact
Date: Sun, 05 Aug 2012 17:54:28 +0200 [thread overview]
Message-ID: <501E9734.8020905@profihost.ag> (raw)
In-Reply-To: <201208051303.09337.Martin@lichtvoll.de>
Am 05.08.2012 13:03, schrieb Martin Steigerwald:
> Am Freitag, 3. August 2012 schrieb Stefan Priebe - Profihost AG:
> But then you didn´t describe where those VM disks are located. If that
> location has many spindles it might not matter at all or even improve
> performance.
30 disks raid 50 via LIO iSCSI and LVM.
> Anyway, I do not see much sense to make them 30 GiB when they can grow to
> 500 GiB – at least provided that you use thin provisioning. Cause
> xfs_growfs and resizing the image will likely be a manual step while thin
> provisioning goes automatically and only needs to be monitored.
I do not use thin provisioning as dm thin is not production ready isn't it?
> That manual step makes sense tough if you want to guarentee all the space
> thats visibly in df output is really physically available, without
> providing for x times 500 GiB initially.
Oh i can easily automate the whole resizing stuff.
Stefan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-05 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 13:56 xfs_growfs / planned resize / performance impact Stefan Priebe - Profihost AG
2012-07-31 17:27 ` Stan Hoeppner
2012-08-03 4:03 ` Eric Sandeen
2012-08-03 6:09 ` Stefan Priebe - Profihost AG
2012-08-03 13:46 ` Eric Sandeen
2012-08-05 11:03 ` Martin Steigerwald
2012-08-05 12:34 ` Stan Hoeppner
2012-08-05 13:49 ` Martin Steigerwald
2012-08-05 20:26 ` Stan Hoeppner
2012-08-05 15:54 ` Stefan Priebe [this message]
2012-08-06 11:42 ` Michael Monnerie
2012-08-04 22:43 ` Dave Chinner
2012-08-05 5:46 ` Stefan Priebe
2012-08-05 11:06 ` Martin Steigerwald
2012-08-05 11:35 ` Andy Bennett
2012-08-05 20:57 ` Dave Chinner
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=501E9734.8020905@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=Martin@lichtvoll.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.