Re: [Moosefs-users] automount in debian

[Piotr T. <pio...@co...>]

You can try with bridge 'forward delay' option (in dom0).
Maybe the problem you suffer is that the bridge/interface is in learning state 
(for forward delay time, default is 15 sec) before the state will change to 
forwarding.

Regards,
Piotr Teodorowski

On Wednesday 01 of June 2011 23:21:23 Josef wrote:
> The network device with a moosefs master is eth1 and the master was
> running. But I found out, that there is a huge delay between the network
> is up and between it actually starts working. I forgot to mention, that
> it is a Xen PV guest, so I guess it takes some time before the Xen host
> adds the guest eth to its bridge. So I have solved it by a stupid init
> script, that waits 10 seconds and remounts all fuse filesystems:
> 
>      echo "Remounting for MFS"
>      sleep 10
>      mount -a -t fuse
> 
> Nicer solution would be to add a delay to ifup script of a network
> interface...
> 
> Dne 6/1/11 10:55 AM, Michal Borychowski napsal(a):
> >> -----Original Message-----
> >> From: Josef [mailto:pe...@p-...]
> >> Sent: Tuesday, May 31, 2011 4:41 PM
> >> To: moo...@li...
> >> Subject: [Moosefs-users] automount in debian
> >>
> >> Hello,
> >>       I'm having problems with automount under debian (squeeze). I have
> >> this line in my fstab:
> >> /opt/mfs/bin/mfsmount /mnt/mfs fuse
> >> mfsmaster=172.16.100.2,mfsport=9421,_netdev 0 0
> >>
> >> during the startup debian finds out, that it is a net device, so calls
> >> if-ip.d/mountmfs, but I fails:
> >>
> >> Configuring network interfaces...if-up.d/mountnfs[eth0]: waiting for
> >> interface eth1 before doing NFS mounts ... (warning).
> >
> > This message comes from Debian init scripts and means, that eth0 has been
> > initialized, but eth1 isn't yet, so mounting of network filesystems is
> > delayed until initialization of the remaining network interfaces.
> >
> >> can't connect to mfsmaster ("172.16.100.2":"9421")
> >
> > It's mfsmount message, probably occurs after initialization of eth1.
> >
> > There are a few possible causes, e.g.:
> > - master is not running yet
> > - given host is not accessible yet (maybe there is some delay between
> >    initializing network interface and network being accessible?)
> >
> >
> > Kind regards
> > Michal Borychowski
> 
> ---------------------------------------------------------------------------
> --- Simplify data backup and recovery for your virtual environment with
>  vRanger. Installation's a snap, and flexible recovery options mean your
>  data is safe, secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> _______________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users
>