Re: [SSI-devel] testing drbd?

[Roger T. <op...@bl...>]

>   drbd4: short read expecting header on sock: r=-512
>   drbd0: short read expecting header on sock: r=-512

The short read messages indicate the other drbd peer has gone down.  You
can disregard this during a node down event.

>   fsck 1.35 (28-Feb-2004)
>   e2fsck 1.35 (28-Feb-2004)
>   fsck.ext3: No such file or directory while trying to open /dev/drbd/0
>
>   The superblock could not be read or does not describe a correct ext2
>   filesystem.  If the device is valid and it really contains an ext2
>   filesystem (and not swap or ufs or something else), then the superblock
>   is corrupt, and you might try running e2fsck with an alternate
> superblock:
>       e2fsck -b 8193 <device>
>
>   /etc/rc.d/rc.sysrecover running
>
> And node2 just hangs there.  Node1's console is still responsive.

Are you still having this problem?  You are running SSI-1.2.x on Fedora
Core 2 right?  Do you know how to figure out where in rc.sysrecover it
stopped?

-Roger