Time to cull the usage on mirrors again, but leave the files on ftp.m.o. $ du -scm seamonkey/releases/* 2878 seamonkey/releases/2.0.14 ** 3600 seamonkey/releases/2.1 1192 seamonkey/releases/2.1b1 ** 2471 seamonkey/releases/2.1b2 ** 3346 seamonkey/releases/2.1rc1 ** 3608 seamonkey/releases/2.1rc2 ** 2660 seamonkey/releases/2.2b1 ** maybe ? 2792 seamonkey/releases/2.2b2 1 seamonkey/releases/README 22544 total $ du -scm thunderbird/releases/* 331 thunderbird/releases/22.214.171.124 4582 thunderbird/releases/3.0.11 ** leaving update/win32 4752 thunderbird/releases/3.1.10 ** 4693 thunderbird/releases/3.1.11 628 thunderbird/releases/3.3a3 ** 7552 thunderbird/releases/5.0 4516 thunderbird/releases/5.0b1 ** 9007 thunderbird/releases/5.0b2 ** 0 thunderbird/releases/latest 0 thunderbird/releases/latest-3.0 ** 0 thunderbird/releases/latest-3.1 0 thunderbird/releases/latest-5.0 1 thunderbird/releases/README 36059 total I'm proposing we remove all the ** lines from the mirrors. Sound OK ?
(In reply to comment #0) > 1192 seamonkey/releases/2.1b1 ** > 2471 seamonkey/releases/2.1b2 ** > 3346 seamonkey/releases/2.1rc1 ** > 3608 seamonkey/releases/2.1rc2 ** I went ahead and removed these ones. The two betas have already been switched to ftp://ftp.m.o on http://www.seamonkey-project.org, and the latter two will still work from download.m.o using MoCo mirrors (if anyone should hit them). Still interested in cleaning up the other releases, but acting now because we're at 108G and will need space for SeaMonkey 2.2 final this week.
I'm not sure about 5.0b2, but the other Thunderbird ones look ok to remove from the mirrors. I'm wondering why we are leaving 126.96.36.199 on the mirrors...?
Added these to the exclude list: 4582 thunderbird/releases/3.0.11 ** leaving update/win32 4752 thunderbird/releases/3.1.10 ** 628 thunderbird/releases/3.3a3 ** 4516 thunderbird/releases/5.0b1 ** 0 thunderbird/releases/latest-3.0 ** (In reply to comment #2) > I'm wondering why we are leaving 188.8.131.52 on the mirrors...? There are still about 100k requests for 184.108.40.206 complete mars every weekday, almost all for windows. Slightly larger number for 3.0.11.
Removed Check Now for the releases in comment #3, and turned it back on for the update products for 3.0.11.
Added SeaMonkey 2.0.14, 2.1, 2.2b1, 2.2b2, 2.2b3 to the exclude list; will wait a couple of days for most of the mirrors to action that before fixing Check Now in bouncer. Callek says (on IRC), for SeaMonkey, until you hear differently, you can feel safe doing "leave one major release, and latest beta on mirrors, all else can be dropped" We have dm-download02 to keep download.m.o links working, so there's no need to wait for the SeaMonkey website to be updated to use ftp.m.o.
As it turns out, we DO need Thunderbird 3.1.10 on the mirrors, since we never shipped 220.127.116.11->3.1.11 major updates.
I've set Check Now back to true on the Thunderbird-3.1.10-Complete product, which means we check the mirrors every 5 minutes. We now have several mirrors providing coverage now. I think the daily job that checks all products must have failed, leaving us without mirror coverage.
(In reply to Nick Thomas [:nthomas] from comment #5) > Added SeaMonkey 2.0.14, 2.1, 2.2b1, 2.2b2, 2.2b3 to the exclude list; will > wait a couple of days for most of the mirrors to action that before fixing > Check Now in bouncer. Check Now has been cleaned up, along with 2.3b1. (In the meantime bug 674517 has permanently removed any betas from the mirrors for Thunderbird, SeaMonkey, Firefox, and Fennec.) The mozilla-releases module is at 80G right now.
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.