About the mirror.accum.se file archive
Some statistics,
bandwidth graphs and Load graphs for all file archive machines.
Overview
This server is a cluster of three kinds of machines:
- Backends
- Reliable large storage that is NFS-mounted to all the frontends
and offloaders, NAS-style.
- Frontends
- The machines behind the DNS names. Handles all incoming requests, but passes http and https requests for large files on to offloaders.
- Offloaders
- Serves http and https requests for large files, distribution
cd/dvd-images, movies etc.
Disk Backends
The current disk backend is an IBM x3650 M4 server called greifswald.
Total usable space is about 700TiB.
Frontends
We are using caching frontends to be able to deliver high bandwidth
without having to have a disk backend that can handle the aggregated
output. The cache used is mod_cache_disk_largefile, our modified version of the
mod_cache_disk (previously mod_disk_cache) available in Apache HTTP Server. An
XFS filesystem over striped SAS 10k/15kRPM disks is used as local storage.
For larger files (like .iso images) we use http redirects to send these off
to one of the offloaders. The choice of which offloader to redirect to is
done by a perl program and is cached in apache as a dbm-cached rewrite rule.
To keep cache size reasonably low a certain URL is always redirected to the
same offloader.
The visible frontends are:
Offloaders
The offloaders work just as the frontends caching data locally, but they only
handle a few large files. The majority of data is usually sent by the
offloaders and cache re-use is high.
As a precaution against nosey users, the offloaders redirect directory indexes
back to the main frontends. And as a precaution against stupid download agents
we limit the max connections per IP to 10, and we always deliver data from
cache if the data is cached, even if the user agent sends "Cache-control: no
cache" or similar.
The current offloaders are:
Network
All machines are reachable via both IPv4 and IPv6 and connected with 10 or 25
gigabit ethernet, external bandwidth available is 200 gigabit/s.
Current and historical bandwidth graphs for the frontends.
Protocols
All mirrored content are available via HTTP, HTTPS, Rsync and FTP. We strongly recommend avoiding FTP whenever possible.
Names
The server is known by many names. Among them:
- mirror.accum.se
- ftp.accum.se
- ftp.ac2.se
- ftp.acc.umu.se
- ftp.sunet.se
- ftp.se.debian.org
- ftp.gnome.org
- se.releases.ubuntu.com
- se.archive.ubuntu.com
- cdimage.debian.org
Mirrored projects
All projects we actively mirror can be found in the /mirror directory.
Contact
If you have any questions please contact ftp-adm, and we will do our best to help you.
Mirror requests
We are happy to add download mirrors of open source projects to the mirror.accum.se file archive. All mirrored projects are available via HTTP, HTTPS and Rsync.
Send us a mirror request containing:
- Project information (short description, home page URL, license etc as appropriate).
- An email address where we can reach the project in case of mirror issues.
- Estimates of size and number of files, current and future growth.
- Rsync URL that we can mirror from.
- Expected update interval.
- Mirror list URL.
- Any mirror status or download director (eg. Mirrorbits, MirrorBrain) status URL(s), if applicable.
- Any other information that you think we might need.
We strongly recommend projects to leverage a download redirector to make best use of mirrors, forcing users to manually select mirrors is frowned upon. Mirrorbits comes highly recommended by many projects that we mirrror.
More information
Previous setups
