Menu
▾
▴
moosefs-users
|
From: Michał B. <mic...@ge...> - 2012-02-21 06:26:57
|
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. When the system comes up, it just logs: Jan 15 06:55:51 ovsa1 mfsmount[6926]: file: 63934, index: 0, chunk: 24383640, version: 1 - writeworker: connection with (C0A80214:9422) was timed out (unfinished writes: 5; try counter: 1) Jan 15 06:55:52 ovsa1 mfsmount[6926]: writeworker: write error: 26 Jan 15 06:55:55 ovsa1 last message repeated 3 times Jan 15 06:55:56 ovsa1 mfschunkserver[6252]: testing chunk: /dfs1/75/chunk_00000000015C3675_00000001.mfs Jan 15 06:55:56 ovsa1 mfsmount[6926]: writeworker: write error: 26 Jan 15 06:56:06 ovsa1 last message repeated 8 times Jan 15 06:56:06 ovsa1 mfschunkserver[6252]: testing chunk: /dfs5/A7/chunk_00000000015C38A7_00000001.mfs Jan 15 06:56:07 ovsa1 mfsmount[6926]: writeworker: write error: 26 Jan 15 06:56:16 ovsa1 last message repeated 8 times Jan 15 06:56:17 ovsa1 mfschunkserver[6252]: testing chunk: /dfs4/AE/chunk_00000000015BDEAE_00000001.mfs Jan 15 06:56:17 ovsa1 mfsmount[6926]: writeworker: write error: 26 Jan 15 06:56:26 ovsa1 last message repeated 7 times Jan 15 06:56:27 ovsa1 mfschunkserver[6252]: testing chunk: /dfs3/DB/chunk_00000000015C42DB_00000001.mfs Jan 15 06:56:27 ovsa1 mfsmount[6926]: writeworker: write error: 26 Jan 15 06:56:37 ovsa1 last message repeated 10 times Jan 15 06:56:37 ovsa1 mfschunkserver[6252]: testing chunk: /dfs2/BB/chunk_00000000015C2EBB_00000001.mfs Jan 15 06:56:37 ovsa1 mfsmount[6926]: writeworker: write error: 26 Jan 15 06:56:46 ovsa1 last message repeated 9 times Jan 15 06:56:47 ovsa1 mfschunkserver[6252]: testing chunk: /dfs1/90/chunk_00000000015C3690_00000001.mfs Jan 15 06:56:48 ovsa1 mfsmount[6926]: writeworker: write error: 26 Also, the mfsmount never retries to connect after these errors. Any idea how to resolve this, perhaps by increasing the timeout, or making mfsmount reconnect until it succeeds? Thanks in advance. |
|
From: Stas O. <sta...@gm...> - 2012-02-25 22:12:27
|
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? 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! >> >> ------------------------------------------ >> >> >> ------------------------------------------------------------------------------ >> Virtualization & Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> _______________________________________________ >> moosefs-users mailing list >> moo...@li... >> https://lists.sourceforge.net/lists/listinfo/moosefs-users >> > > |
|
From: Ricardo J. B. <ric...@da...> - 2012-02-28 22:49:32
|
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! ------------------------------------------ |
|
From: Ricardo J. B. <ric...@da...> - 2012-02-23 23:18:19
|
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! ------------------------------------------ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X