Re: Move jogamp.org to new machine due to need for reliable healing filesystem (ZFS) [June 3rd - June 7th]

https://jogamp.org/bugzilla/show_bug.cgi?id=742

+++

On current jogamp.org server, we have experienced silent GNU/Linux SW Raid-1
block mismatches.

[root@jogamp sysconfig]# cat /sys/block/md2/md/mismatch_cnt
1024

The semantics of GNU/Linux SW Raid are inconclusive, i.e. it could be nothing,
but also a silent degradation (block failure).

Since the only reliable filesystem w/ proven block failure detection via
sha256 checksums
including healing via redundancies (mirror or raidz) is ZFS,
we need to move to a new box w/ preferably ECC Ram and 2x Enterprise HDD for
mirroring setup.

A work in progress is documented here (doc will move to git later on):
  <http://jogamp.org/files/temp/zfs-linux-server-setup.txt>

The move will probably happen within next week, i.e. June 3rd - 7th.

+++

Cheers, Sven

Updated .. <https://jogamp.org/bugzilla/show_bug.cgi?id=742> ..

We will move jogamp.org today to a new server to enhance it's storage
reliability. The new server should also perform better ..

To All:
  - Please refrain from writing to any service of jogamp.org (not this forum):
     bugzilla, wiki, jogamp.org email, git, ...

  - Service interruption ahead TODAY


I will update you on progress here.

On 06/05/2013 09:39 AM, Sven Gothel [via jogamp] wrote: <https://jogamp.org/bugzilla/show_bug.cgi?id=742#c4>

write access allowed again, files moved and following services reinstated:

logging, move backup files and users, mysql, procmail, bogofilter, sasl2,
dovecot, sendmail,
git, apache and jabot

todo: jenkins

The HungryHarry? powered twitter aggregation looks broken:
https://jogamp.org/stream/
It only display an empty list after the server move.

It's not a big loss as a few people benefited of this feature to disparage JOGL, it should be moderated or disabled.