Re: [Moosefs-users] Connection timed out at mfsmount on boot

[Ricardo J. B. <ric...@da...>]

El Sábado 25/02/2012, Stas Oskin escribió:
> Moreover, I noticed that running mount twice, causes double fuse mount,
> with unknown effects on system behavior.
> Meaning the MFS client unable to detect that it already mounted, and just
> mounts again.
>
> Will the additional mounting in rc.local cause such effect?

Yes, you're right. I should have mentioned it but it slipded from my mind: mfsmount
has an option (-o nonempty: allow mounts over non-empty file/dir) that I believe is
off by default, that instructs fuse to mount anyway, causing double-mounts.


In CentOS 5 and CentOS 6, mfs 1.6.20 installed from repoforge.org it doesn't
double-mount:


[root@mds01 ~] # cat /etc/redhat-release
CentOS release 6.2 (Final)

[root@mds01 ~] # grep ^mfs /etc/fstab
mfsmount      /mnt/mfs        fuse     defaults,noatime,_netdev,mfsmaster=mds01,mfssubfolder=/   0 0

[root@mds01 ~] # mount -a -t fuse
mfsmaster accepted connection with parameters: read-write,restricted_ip ; root mapped to root:root
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
error in fuse_mount


[root@bkpmds01 ~] # cat /etc/redhat-release
CentOS release 5.7 (Final)

[root@bkpmds01 ~] # grep ^mfs /etc/fstab
mfsmount      /mnt/mfs        fuse     defaults,noatime,_netdev,mfsmaster=bkpmds01,mfssubfolder=/  0 0

[root@bkpmds01 ~] # mount -a -t fuse
mfsmaster accepted connection with parameters: read-write,restricted_ip ; root mapped to root:root
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
error in fuse_mount


> Regards.
>
> On Sat, Feb 25, 2012 at 10:56 AM, Stas Oskin <sta...@gm...> wrote:
> > Hi.
> >
> > So you advice both having mount -a -t fuse in rc.local, and chkconfig
> > netfs for Linux systems?
> >
> > Regards.
> >
> >
> > On Fri, Feb 24, 2012 at 1:18 AM, Ricardo J. Barberis <
> >
> > ric...@da...> wrote:
> >> Also, beware of gigabit networks: some NICs are very slow at
> >> establishing link
> >> and mfsmount (or any other network filesystem) will fail mounting
> >> anyway, even using _netdev on fstab as suggested by Michał.
> >>
> >> I have 'mount -a -t fuse' in /etc/rc.local just beacuse of this.
> >>
> >> And, if you use _netdev you also have to enable mounting network
> >> flesystems on
> >> boot: 'chkconfig netfs on' in RedHat and derivatives should do the
> >> trick.
> >>
> >>
> >> PS: Michał, could you add that last bit about netfs to the Reference
> >> Guide?
> >> Thanks!
> >>
> >> El Martes 21/02/2012, Michał Borychowski escribió:
> >> > Hi Stas!
> >> >
> >> > What platform do you use? The solution with /etc/fstab works only on
> >>
> >> Linux
> >>
> >> > platforms (tested on Debian). On other platforms you need to prepare a
> >> > script in /usr/local/etc/rc.d which will run mfsmount with needed
> >>
> >> options.
> >>
> >> > And on Linux you need _netdev option, as written on
> >> > http://www.moosefs.org/reference-guide.html in "Mounting the File
> >>
> >> System"
> >>
> >> > section.
> >> >
> >> > Kind regards
> >> > Michal
> >> >
> >> > From: Stas Oskin [mailto:sta...@gm...]
> >> > Sent: Sunday, January 15, 2012 10:01 AM
> >> > To: MooseFS
> >> > Subject: Connection timed out at mfsmount on boot
> >> >
> >> > Hi.
> >> >
> >> > We have the mfsmount set in fstab, but noticed it never properly works
> >>
> >> on
> >>
> >> > boot.
-- 
Ricardo J. Barberis
Senior SysAdmin / ITI
Dattatec.com :: Soluciones de Web Hosting
Tu Hosting hecho Simple!

------------------------------------------