Just a bit of a feedback here.One of our hadoop 0.16.4 namenodes had gotten a disk full incident today. No second backup namenode was in place. Both files fsimage and edits seem to have gotten corrupted. After quite a bit of debugging and fiddling with a hex edtor we managed to resurrect the files and continue with just minor loss.
Thankfully this only happened on a development cluster - not on production. But shouldn't that be something that should NEVER happen?
cheers -- Torsten
