stability and resulting file system problems

[Thomas Klausner <wiz%NetBSD.org@localhost>]

Hi!

I updated my -current/amd64 kernel on Friday.
After a short while, all file system access seems to have been
blocked. I could switch windows in screen, but not open new shell
windows. I could only open remote connections with 'ssh host bash',
not with 'ssh host' (which would have used bash as login shell).

After rebooting, I had fsck trouble in phase 2:
BAD STATE 0 IN INODE 610616
After that error, fsck just exits.
I tried to "clri" the node from fsdb, but that didn't help.

Another file system fscks cleanly, but when mounting it rw, I get
an error about freeing a free inode and NetBSD drops into ddb. Problem
is, that is the root file system :(

Help! :(
 Thomas