Re: [SSI-devel] testing drbd?
Brought to you by:
brucewalker,
rogertsang
From: Jiann-Ming Su <suj...@gm...> - 2005-03-11 15:15:05
|
On Fri, 11 Mar 2005 10:05:57 -0500, Roger Tsang <rog...@gm...> wrote: > Since I already explained where rc.sysrecover fits in the scheme of > all things, it is logical to arrive at the simple conclusion that a > rc.sysrecover problem is not drbd related - with the exception of the > changes to rc.sysrecover you made specifically for drbd. That's only > change to 1 line in that script. Your rc.sysrecover problem is likely > to be just an embarassing typo, but until you debug it nobody really > knows for sure. > That's usually what it ends up being. I was hoping with the output I've pasted that you would know immediately the obvious mistake I made. In the rc.sysrecover and SSIfailover scripts, the DEVICE is listed as /dev/drbd/0 (which is the / filesystem). But, on each node when I show mount, the filesystems are listed as "/dev/1/drbd/0" for node1 and "/dev/2/drbd/0" for node2. I guess somewhere in the boot process, the context of the fstab gets changed for each node? For the record, node2 will boot independently of node1. So, I'm not sure why fsck complains about an invalid ext2 superblock. I'll take a closer look today. -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman |