Bidirectional rsync flaws

 

Conclusion:

rsync does a fantastic job to sync and keep in sync content from one to another system. Backups are perfect with it, use rsnapshot to get even more out of it.
But rsync is not good in bi-directional syncing in the case of deletion of content. Despite, that you can delete all file on all content directories on all hosts, which is not an option for a the very-day user.
Keep in mind, that you need same timezones and synced clocks, when using the –update option

Look out to keep things in sync, with deletion too, take “unison” for example.
Unison

Continue reading

pear fails… Update

I’m hunting a bug on a CentOS 5.3 installation. If I run pear, it just exists direclty. Even pear help quits cowardly. The only hint is in the logfile:

php: PHP Fatal error:  Call to a member function getMessage() on a non-object in /usr/share/pear/pearcmd.php on line 321

Installed version of php is:
PHP 5.1.6 (cli) (built: Jan 13 2010 17:09:42)
Copyright (c) 1997-2006 The PHP Group
Zend Engine v2.1.0, Copyright (c) 1998-2006 Zend Technologies with eAccelerator v0.9.5.2, Copyright (c) 2004-2006 eAccelerator, by eAccelerator

pear is: php-pear-1.4.9-6.el5

Somebody have an idea?

[UPDATE]: As always, restart from the beginning helps. I did uninstall the rpm package by yum remove php-pear and downloaded the go-pear via wget http://pear.php.net/go-pear. The installation was triggered with php ./go-pear and I got a working environment again.

Drobo kaputt (schon wieder) [Update2]Drobo failed (again) [Update2]

Heute morgen wurde ich mal wieder von einer “leeren” Drobo überrascht. Alle Daten in einem kaputten ext3 und keiner der Backup-Blöcke funktional. Gparted fand zwar die Partition, aber fsck.ext3 verweigerte die Arbeit. Nun macht testdisk seine Scans wieder.

[Update 2009/04/01] So wie es akutell aussieht ist das journal vom ext3 zerstört. Der fsck wurde mit einem komplett leeren Dateisystem beendet. Ich hatte zuvor ein Image der “Platte” gezogen. Als nächstes werde ich eine der Platten aus der Drobo ausbauen und direkt in der Linuxkiste scannen.

[Update 2009/04/22] Ich habe nun eine der Festplatten aus der Drobo direkt in meine Linuxkiste gesteckt. photorec hat viele Dateien gefunden, aber der Inhalt ist ein ziemlicher Remix und damit unbrauchbar. Ich werde jetzt mal testdisk drauflos lassen.This morning I was surprised again with an “empty” Drobo. All data in a broken ext3, with none of the backup blocks working. Gparted did find the partion, but fsck.ext3 refused to work. testdrive is now doing its scans.

[Update 2009/04/01] As it currently looks like, the complete ext3 journal has been broken. Running fsck did result in a complete empty filesystem. I did a image copy before the fsck. Next step is getting one of the disks out of the Drobo and scan it directly in the linux box.

[Update 2009/04/22] I moved on of the disks out of the drobo into a linux box directly. photorec discovered a lot of the files, but the content got a remix and is mostly useless. I will now try to use testdisk on it.