Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Todd, On Tue, Dec 13, 2005 at 09:54:40AM -0500, Todd Denniston wrote: > Raoul Borenius wrote: > >On Mon, Dec 12, 2005 at 10:27:36AM -0500, Todd Denniston wrote: > > > >>>>If it looks like the drbd failover worked, that is, the /var/lib/nfs > >>>>symlink was pointed to drbd0, and drbd0 was there before nfs started.. > >>>>it > >>>>may be something else that is causing stales during failover. > >>> > >> > >>Just for clarification: > >>You indicate you use a softlink to put the drbd0 filesystem in place of > >>/var/lib/nfs, but above you mount drbd0 at /var/lib/nfs ... which is it, > >>and is it the same on BOTH systems? > > > > > >Both nodes are always setup identical. I just tried two different setups: > > > >1.) the 'simple' setup with only one drbd as described in > > http://linux-ha.org/DRBD_2fNFS, i.e. with a symlink from /var/lib/nfs > > to the drbd-volume. Everything works perfectly, no errors on failover. > > > >2.) a setup without symlink but /var/lib/nfs as /dev/drbd0 and > >/srv/nfs/mail > > as /dev/drbd1. I get stale nfs errors during failover. > > > > I find setup 2 to be interesting in its failure, because I would think it > should work the same, but I have no idea why it fails. I have now. Just to let you all know, upgrading the Debian-kernel from 2.6.8-2-686-smp to 2.6.12-1-686-smp did the trick. No more errors. Thanx for your help and time!