i, the time out is from node a to b seconds, but from node b to a 15 minutes. what I saw was, that the handle changed in /var/lib/nfs/rmtab from 0x000002 to 0x000003 although the fsid is the same on both nodes. how can the 15minute timeout occur? Mit freundlichem Gruss, Dirk Laurenz Systems Engineer Fujitsu Siemens Computers R DE ISC SOP PS N/O Hildesheimer Strasse 25 30880 Laatzen Germany Telephone: +49 511 84 89 18 08 Telefax: +49 511 84 89 25 18 08 Mobile: +49 170 22 10 781 Email: mailto:dirk.laurenz@xxxxxxxxxxxxxxxxxxx Internet: http://www.fujitsu-siemens.com Firmenangaben: http://www.fujitsu-siemens.de/imprint.html > -----Original Message----- > From: Neil Brown [mailto:neilb@xxxxxxx] > Sent: Saturday, June 28, 2008 1:44 AM > To: Oeltze, Benjamin > Cc: Laurenz, Dirk; linux-nfs@xxxxxxxxxxxxxxx > Subject: RE: Sm-notify > > On Friday June 27, Benjamin.Oeltze@xxxxxxxxxxxxxxxxxxx wrote: > > Hi, > > maybe I can specify Dirks question. > > Thanks. > > > > > We are trying to set up a NFS Cluster and want to use sm-notify to inform the > Clients if the Server has failed over. > > We have found a Howto that says: sm-notify uses files under /var/lib/nfs/sm to > determine the Clients it has to inform. > > Our Problem is, that ther are no files in this place even if we connet with a client. > Is there anything we have forgotten? > > Files do not get created in /var/lib/nfs/sm until the client tried to > get a lock on some file (or part of a file). Then the file is > created. > Some minutes after the last lock is dropped, the file should be > removed (though I recall there were some issues related to that, it > might depend on exactly which kernel you are running). > > If no file locking is involved, there is no need to inform the client > of failover. They will transparently start accessing the new server > through the old IP address, possible after a short timeout. > > NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
