newsNews: Savannah status

Latest News
Savannah is migrating to updated systems. posted by rwp, Wed Nov 30 23:56:33 2016 - 0 replies
Savannah suffering networking problems posted by rwp, Fri May 13 22:58:25 2016 - 0 replies
Savannah https SSL certificates updated posted by rwp, Fri Mar 25 05:32:10 2016 - 0 replies
Savannah IPv4 address has changed posted by rwp, Sun Aug 9 20:07:57 2015 - 0 replies
IPv4 address change for Savannah posted by rwp, Sat Aug 8 05:14:00 2015 - 0 replies
[179 news in archive]

Savannah status

Item posted by Sylvain Beucler <Beuc> on Thu Jun 11 17:37:06 2009.

All services are running fine now, except for a few things to fix in webcvs replication.

CVS/SVN/Git/Hg: no need to send new recovery requests, all repos are restored, either from your instructions, either from the May 27 backup.

Arch/Bzr: restored from May 29

Downloads: restored from May 29

WebCVS; restored from May 27 at Savannah, refreshed accordingly at and For (group 'www') only, changes between 27 and 29 were manually re-committed. If you need a diff of these changes for your project, please send a support request.

The May 27 backup was found some days after the crash because of ongoing changes in the FSF backup system. The location of the latest backups are now properly documented.

The origin of the crash is still unknown. A first degradation was due to a broken disk. The one that happened the next day and corrupted the whole disk array is unknown. The experts we sent the disks to could not easily recover a whole directory structure, so we will not further attempt to recover data from the crashed disks.

Currently we're planning a move to newer hardware to avoid taking any risk. We'll also put an emphasis on having backups available in the same facility, to reduce the delay we got during the recovery. We'll also setup a DRBD real-time synchro to minimize the amount of data lost between the last backup and a crash.


No messages in Savannah status


Back to the top

Powered by Savane 3.1-cleanup