Date: Wed, 21 Sep 2016 18:26:30 +0000 From: Colin Percival <cperciva@tarsnap.com> To: Michael Sierchio <kudzu@tenebras.com>, Julian Elischer <julian@freebsd.org> Cc: FreeBSD Lists <freebsd-xen@freebsd.org> Subject: Re: number of xen block devices Message-ID: <010001574dffc3a9-b9aa811c-ac09-45b3-9aea-1be72fcaab67-000000@email.amazonses.com> In-Reply-To: <CAHu1Y70uCjZH92iMe4NVaK3q9%2BbSfFb0DpT%2B7OtBCNoXOY-Pag@mail.gmail.com> References: <73fad119-03d8-a9ea-c222-f65b22c6feac@freebsd.org> <010001574a0207f9-d12e326c-e152-49f9-9763-2cf0161f7458-000000@email.amazonses.com> <3132e8d0-68db-940f-5cb1-22fe01b52480@freebsd.org> <CAHu1Y70uCjZH92iMe4NVaK3q9%2BbSfFb0DpT%2B7OtBCNoXOY-Pag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/21/16 09:13, Michael Sierchio wrote: > Also check if there is a resource limit imposed by AWS. If you are bumping > into that, a simple request can get the limit raised for a particular > availability zone. AWS limits can be an issue, but it would be a limit on the number or size of the EBS volumes can *create*. Once volumes are created, AWS limits won't affect whether you can attach them to instances or whether the instances can see the attached volumes, so I doubt that's what Julian was running into. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010001574dffc3a9-b9aa811c-ac09-45b3-9aea-1be72fcaab67-000000>