[Linux-cluster] Re: Samba failover "impossible" due to missing cifs client reconnect?

[Lon Hohberger]

On Thu, 2005-09-08 at 09:15 +0200, Axel Thimm wrote:
> On Wed, Sep 07, 2005 at 04:12:52PM -0500, Christopher R. Hertel wrote:
> > On Wed, Sep 07, 2005 at 10:51:16PM +0200, Axel Thimm wrote:
> > : :
> > > > I just tested this.  On a W/XP box I browsed through some directories on a 
> > > > share served by Samba.  I then shut Samba down, and tried viewing some 
> > > > different subdirectories of the same share.  Windows coughed up an error 
> > > > dialog.  I then restarted Samba and Windows got happy again.  I could 
> > > > browse through all of the subdirectories in the share.
> > > 
> > > Yes, that does work, but what I wanted to setup is a transparent
> > > failover, so that network I/O recovers w/o any manual interaction.
> > >
> > > I.e. I don't want to (soft) relocate the samba shares onto another
> > > node due to load ballancing considerations and generate user visible
> > > I/O errors and failures on a dozen clients.
> > 
> > I guess I'm not really clear on what it is you're trying to accomplish.
> > Can you provide a little more description of what you'd like to see 
> > happen, and what kinds of environments you expect?
> 
> A cifs client performs a largish copy operation. During that the share
> is relocated to a different node. The copy operations should stall
> during the relocation and resume after 10-20 seconds.

Can't do it, as far as I know... SMB has too much internal state
information.

-- Lon