Thread: [Moosefs-users] MooseFS init files

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi.

Are there any init.d files for RedHat MooseFS installations?

Regards.

On Tue, 6 Jul 2010 01:04:02 +0300
Stas Oskin <sta...@gm...> wrote:

> Hi.
Hi,
> 
> Are there any init.d files for RedHat MooseFS installations?
No. I'll try to cook some for Redhat/CentOS, and ask the dev team to
include it in the main repository. Until then, I won't be able to
provide RPM with it. So, at best, you'll have to wait for the next
stable version.
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

On Tue, 6 Jul 2010 13:00:21 +0300
Stas Oskin <sta...@gm...> wrote:

Hi,
> Hi.
> 
> Thanks, I will try to write some of my own, and we could compare them.
Please find attached the ones I just created. TOTALLY untested.
It should just work I hope. Feedback welcome.
> 
> Based on fact MFS daemonic itself, it should be quite easy.
> 
> Only question, is how to run mount operation, together with fstab (the
> manual says the system needs to run "mount -a -t fuse.mfs") sometime.
MFSMASTER_IP:9421 on /mnt/mfs type fuse.mfs (rw, nosuid, nodev,
allow_other, default_permissions)
See http://www.moosefs.org/reference-guide.html
Regards,
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

On Tue, 6 Jul 2010 15:14:21 +0300
Stas Oskin <sta...@gm...> wrote:

> > Please find attached the ones I just created. TOTALLY untested.
> > It should just work I hope. Feedback welcome.
> > >
> > > Based on fact MFS daemonic itself, it should be quite easy.
> > >
> > > Only question, is how to run mount operation, together with fstab (the
> > > manual says the system needs to run "mount -a -t fuse.mfs") sometime.
> > MFSMASTER_IP:9421 on /mnt/mfs type fuse.mfs (rw, nosuid, nodev,
> > allow_other, default_permissions)
> >
> 
> 
> Thanks!
> 
> Will give them a look.
> 
> Just for understanding, how do you handling the on-boot mounting?
Reread my answer, it's already there :)
And please don't forget to reply to the list too.
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

> Reread my answer, it's already there :)
>

I see, what about "mount -a -t fuse.mfs" requirement?

Do you skip it somehow?

On Tue, 6 Jul 2010 16:31:20 +0300
Stas Oskin <sta...@gm...> wrote:

> > Reread my answer, it's already there :)
> >
> 
> I see, what about "mount -a -t fuse.mfs" requirement?
If the fs is mounted via fstab, you don't need the mount command line.
Or did I miss a step ?
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

>From http://www.moosefs.org/reference-guide.html:

As of 1.6.x the mfsmount may be set up in the /etc/fstab to facilitate
having MooseFS mounted on the system startup:
MFSMASTER_IP:9421 on /mnt/mfs type fuse.mfs (rw, nosuid, nodev, allow_other,
default_permissions)
*And additionally, the system dependent mount script would need to invoke
something like mount -a -t fuse.mfs.*

The doc is vague and need an actual example.  Make sure mfsmount command
is in the path for root.

This is my example (/etc/fstab):

mfsmount                /mnt/mfs                fuse
mfswritecachesize=0,mfsmaster=secintmoosemaster01,mfssubfolder=/virt-rep
o       0 0

From: Stas Oskin [mailto:sta...@gm...] 
Sent: Tuesday, July 06, 2010 9:52 AM
To: Laurent Wandrebeck
Cc: moo...@li...
Subject: Re: [Moosefs-users] MooseFS init files

>From http://www.moosefs.org/reference-guide.html:

As of 1.6.x the mfsmount may be set up in the /etc/fstab to facilitate
having MooseFS mounted on the system startup:
MFSMASTER_IP:9421 on /mnt/mfs type fuse.mfs (rw, nosuid, nodev,
allow_other, default_permissions)
And additionally, the system dependent mount script would need to invoke
something like mount -a -t fuse.mfs.

Hi.

This is my example (/etc/fstab):
>
>
>
> mfsmount                /mnt/mfs                fuse
> mfswritecachesize=0,mfsmaster=secintmoosemaster01,mfssubfolder=/virt-repo
> 0 0
>
>
Thanks for the example.

Laurent, this probably means that there is no need for mfsmount init file as
it will be mounted straight from fstab.

In case mfsmount crashes, what would bring it back online? fstab?

On Wed, 7 Jul 2010 11:55:48 +0300
Stas Oskin <sta...@gm...> wrote:

> Hi.
> 
> This is my example (/etc/fstab):
> >
> >
> >
> > mfsmount                /mnt/mfs                fuse
> > mfswritecachesize=0,mfsmaster=secintmoosemaster01,mfssubfolder=/virt-repo
> > 0 0
> >
> >
> Thanks for the example.
> 
> Laurent, this probably means that there is no need for mfsmount init file as
> it will be mounted straight from fstab.
> 
> In case mfsmount crashes, what would bring it back online? fstab?
mount -a will do the trick.
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

The proper way to mount MooseFS from fstab is to put there a line similar to
this one:

Mfsmount  /mnt/mfs  fuse  mfsmaster=mfsmaster.gem.lan,mfsport=9421,_netdev
0 0

You can also use all available options (-o parameter) for mfsmount (apart
from "debug"). 

Now MooseFS resources should be automatically mounted during system startup.
Without restart you can test this entry by issuing:
mount -a -t fuse
which means to remount all filesystems (of the given types) mentioned in
fstab.

Regards
Michal

> -----Original Message-----
> From: Laurent Wandrebeck [mailto:lw...@hy...]
> Sent: Friday, July 09, 2010 10:17 AM
> To: Stas Oskin
> Cc: Scoleri, Steven; moo...@li...
> Subject: Re: [Moosefs-users] MooseFS init files
> 
> On Wed, 7 Jul 2010 11:55:48 +0300
> Stas Oskin <sta...@gm...> wrote:
> 
> > Hi.
> >
> > This is my example (/etc/fstab):
> > >
> > >
> > >
> > > mfsmount                /mnt/mfs                fuse
> > > mfswritecachesize=0,mfsmaster=secintmoosemaster01,mfssubfolder=/virt
> > > -repo
> > > 0 0
> > >
> > >
> > Thanks for the example.
> >
> > Laurent, this probably means that there is no need for mfsmount init
> > file as it will be mounted straight from fstab.
> >
> > In case mfsmount crashes, what would bring it back online? fstab?
> mount -a will do the trick.
> --
> Laurent Wandrebeck
> HYGEOS, Earth Observation Department / Observation de la Terre
> Euratechnologies
> 165 Avenue de Bretagne
> 59000 Lille, France
> tel: +33 3 20 08 24 98
> http://www.hygeos.com
> GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C
> F64C

Hi.

This is my example (/etc/fstab):
>
>
>
> mfsmount                /mnt/mfs                fuse
> mfswritecachesize=0,mfsmaster=secintmoosemaster01,mfssubfolder=/virt-repo
> 0 0
>
>

Can you please tell why you disabling the write cache completely in your
example?

Is there any issue using the default 128MB cache?

Regards.

By the way, the master file should have the snippet from here added:
http://www.moosefs.org/news-reader/items/metadata-ins-and-outs.html

This would enable it to automatically replay the logs.

On Thu, 8 Jul 2010 22:04:56 +0300
Stas Oskin <sta...@gm...> wrote:

> By the way, the master file should have the snippet from here added:
> http://www.moosefs.org/news-reader/items/metadata-ins-and-outs.html
> 
> This would enable it to automatically replay the logs.
Looks like a good idea. Michal, do you see any point for not adding
this to init master script ? 
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

Hi!

As we wrote at the website:
"While it is possible to create a script to perform the metadata restore operation, it is recommended that the metadata restoring commands be issued manually to observe any errors that might occur during the fixing operation."

So we do not recommend it :) It can be done automatically but only when someone fully understands what he is doing and what (bad) consequences it could bring. Possibly it could be done as an option. And if some errors appear admin should be somehow informed about them.

Regards
Michał 

> -----Original Message-----
> From: Laurent Wandrebeck [mailto:lw...@hy...]
> Sent: Friday, July 09, 2010 10:21 AM
> To: Stas Oskin
> Cc: moo...@li...
> Subject: Re: [Moosefs-users] MooseFS init files
> 
> On Thu, 8 Jul 2010 22:04:56 +0300
> Stas Oskin <sta...@gm...> wrote:
> 
> > By the way, the master file should have the snippet from here added:
> > http://www.moosefs.org/news-reader/items/metadata-ins-and-outs.html
> >
> > This would enable it to automatically replay the logs.
> Looks like a good idea. Michal, do you see any point for not adding this to
> init master script ?
> --
> Laurent Wandrebeck
> HYGEOS, Earth Observation Department / Observation de la Terre
> Euratechnologies
> 165 Avenue de Bretagne
> 59000 Lille, France
> tel: +33 3 20 08 24 98
> http://www.hygeos.com
> GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C D17C
> F64C

Stas,

Did you have time to test the init scripts I posted ?

Regards,
-- 
Laurent Wandrebeck
HYGEOS, Earth Observation Department / Observation de la Terre
Euratechnologies
165 Avenue de Bretagne
59000 Lille, France
tel: +33 3 20 08 24 98
http://www.hygeos.com
GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
D17C F64C

By the way, Steve init files are working great.

On Fri, Jul 9, 2010 at 11:32 AM, Laurent Wandrebeck <lw...@hy...> wrote:

> Stas,
>
> Did you have time to test the init scripts I posted ?
>
> Regards,
> --
> Laurent Wandrebeck
> HYGEOS, Earth Observation Department / Observation de la Terre
> Euratechnologies
> 165 Avenue de Bretagne
> 59000 Lille, France
> tel: +33 3 20 08 24 98
> http://www.hygeos.com
> GPG fingerprint/Empreinte GPG: F5CA 37A4 6D03 A90C 7A1D  2A62 54E6 EF2C
> D17C F64C
>

Hi.

> Mfsmount  /mnt/mfs  fuse  mfsmaster=mfsmaster.gem.lan,mfsport=9421,_netdev
> 0 0
>
>

What is the purpose of _netdev in this line?

Regards.

El Dom 25 Julio 2010, Stas Oskin escribió:
> Hi.

Hi!

> > Mfsmount  /mnt/mfs  fuse 
> > mfsmaster=mfsmaster.gem.lan,mfsport=9421,_netdev 0 0
>
> What is the purpose of _netdev in this line?
>
> Regards.

It tells the mount init scripts that you need to have networking up before 
mounting those filesystems, as the local filesystems get usually mounted 
earlier in the boot process.

At least that's true for RedHat and its derivatives.

Regards,
-- 
Ricardo J. Barberis
Senior SysAdmin - I+D
Dattatec.com :: Soluciones de Web Hosting
Su Hosting hecho Simple..!

Thread: [Moosefs-users] MooseFS init files

Fault tolerant, POSIX-compliant, Net Distributed Storage / File System

moosefs-users