<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>The 1.3 TB of space is for the *current* archives - i386, amd64,
Sources as is on archive.ubuntu.com. To my knowledge, this
doesn't include old-releases which needs a separate sync (either
ftpsync or rsync) down to disk, and probably in its own directory
root unless you use some arcane black magic with your syncing.</p>
<p>I made an inquiry with the Mirrors Team (and therefore the
Canonical sysadmins as a result), I was provided with the
information that the approximate disk size on-disk for the
old-releases.ubuntu.com data is about 4.2 TB.<br>
</p>
<p>Which means you will need 1.3TB (currently supported releases) +
4.2 TB (old-releases) for a total of 5.5TB space on disk to hold
all that data. And remember that the ubuntu archives and the
old-releases archives sit on separate sync points, so you might
have an *extra* long download time period, and extra bandwidth
usage beyond what you initially anticipated.<br>
</p>
<p><br>
</p>
<p>Thomas</p>
<div class="moz-cite-prefix">On 4/8/19 9:45 AM, Charles Chambers
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:07edb9a6-5d3e-50f1-a9e0-370966f2ff9c@gmail.com">
<pre class="moz-quote-pre" wrap="">The space is not a problem. I'm dedicating an 8TB drive to the
mirroring, and I'm bringing it down slowly enough (3mb per second) that
my provider won't get too hot about it. If 1.3T is enough for
everything from both old-releases and from archive, then it's all good.
Charlie
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Message: 1
Date: Mon, 8 Apr 2019 07:36:35 +0200
From: Brent Clark <a class="moz-txt-link-rfc2396E" href="mailto:brentgclarklist@gmail.com"><brentgclarklist@gmail.com></a>
To: <a class="moz-txt-link-abbreviated" href="mailto:ubuntu-mirrors@lists.ubuntu.com">ubuntu-mirrors@lists.ubuntu.com</a>
Subject: Re: Repository space
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:042bb016-f01d-dc95-0fc3-fed49636ed5c@gmail.com"><042bb016-f01d-dc95-0fc3-fed49636ed5c@gmail.com></a>
Content-Type: text/plain; charset=utf-8; format=flowed
You can bring it down by specifying only the architectures that is of
interest to you and you are willing to mirror.
I.e amd64 and i386.
If you are using ftpsync
ARCH_INCLUDE="amd64 i386 source"
HTH
Brent
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
</blockquote>
</blockquote>
</body>
</html>