Re: Avalon maintainance update
Avalon is now back in a colo and online after its upgrade and appears to be happy as a clam! With meta-data cached on the SSD and the bulk build disk separated from the packages/repo archive it is having an easier time handling the various tasks assigned to it. We're keeping a watch on its stability. -Matt Matthew Dillon dil...@backplane.com
Re: Avalon maintainance update
Avalon has been shipped back and should be online again by Monday. It's been upgraded with a 80G SSD and a 1TB and 2TB HD, in addition to the 750G Seacrate. The other 750G HD (with the read error) has been removed. The SSD is set up for meta-data caching and the bulk build storage has been split off from the root drive, which should make Avalon a lot more responsive once it comes up again. The remaining space will be used for off-site backups. At the moment I'm leaving Avalon as i386 but I've reserved partition space for a future ugprade to 64-bits and set it up to boot from the SSD. We will want to do that at some point to make use of the RAM in the box (which is 8G but i386 can only use ~3G of that), but it's a bit complex because we'd have to switch around our bulk building machines. -Matt
Re: Avalon maintainance update
On Tue, January 11, 2011 6:01 pm, Matthew Dillon wrote: Avalon will be down all of this week for maintainance. It is getting a new storage subsystem. We expect to be able to get it back into a rack mid-next-week or so. In the mean the time the mirrors have a snapshot of the recent bulk builds and the src and pkgsrc repos can be accessed from the master site, crater.dragonflybsd.org. Our other mirrors will likely be a bit out of date on src and pkgsrc as they typically mirrored from avalon. Is it worth changing the DNS for git.dragonflybsd.org, temporarily? That way nothing confuses the mirrors, but 'make src-update' and friends work.
Re: Avalon maintainance update
On Tue, Jan 11, 2011 at 4:12 PM, Justin C. Sherrill jus...@shiningsilence.com wrote: On Tue, January 11, 2011 6:01 pm, Matthew Dillon wrote: Avalon will be down all of this week for maintainance. It is getting a new storage subsystem. We expect to be able to get it back into a rack mid-next-week or so. In the mean the time the mirrors have a snapshot of the recent bulk builds and the src and pkgsrc repos can be accessed from the master site, crater.dragonflybsd.org. Our other mirrors will likely be a bit out of date on src and pkgsrc as they typically mirrored from avalon. Is it worth changing the DNS for git.dragonflybsd.org, temporarily? That way nothing confuses the mirrors, but 'make src-update' and friends work. Expiry of the CNAME is only 3600, I would say yes, it should be changed. Sam
Re: Avalon maintainance update
I'd rather not change the DNS, it could create confusion for the mirrors. And it will probably confuse the hell out of crater and pkgbox64 too. -Matt
Re: Avalon maintainance update
On Tue, January 11, 2011 7:54 pm, Matthew Dillon wrote: I'd rather not change the DNS, it could create confusion for the mirrors. And it will probably confuse the hell out of crater and pkgbox64 too. We shouldn't have any mirrors pulling from crater. Does crater/pkgbox64 pull from git.dragonflybsd.org? This would just be the git target. I may be oversimplifying this in my mind I worry that if something bad happens to mirror-master/avalon right at a release, it would cause a headache. To eliminate that future headache, we'd need either a bunch more hosts or more DNS flexibility.
