Re: [Moosefs-users] mfs 1.6.20

[Travis H. <tra...@tr...>]

to fix the networking so that things go over your internal private 
network segment instead of the public segment,
for the chunk server configuratons (mfschunkserver.cfg)
uncomment and edit the BIND_HOST

# BIND_HOST = *

by default it will listen on all interfaces.

Also, when setting the chunk servers, and mfsmount clients, be sure to 
specify the internal IP address (or even better, create an internal DNS 
name) for the internal MFS master node IP address.


Nautalus might do some kind of pre-crawl sub folders to cache file and 
content types, like a content indexer? I am not sure though, have not 
used it

On 12-02-08 3:38 PM, JJ wrote:
> Hello moosefs-users:
>
> I have managed to install our first moosefs test system.
> I have 3 identical boxes. All
> CentOS 5.7 /x86_64
> mfs 1.6.20 installed from source.
> fuse-devel-2.7.4-8.el5 across all installed via yum.
>
> My client is
> OpenSUSE 11.4
> mfs 1.6.20 installed from source and
> fuse-devel-2.8.5-5.1.i586 install via zypper.
>
> All 3 moose servers have a dedicated 10G ext3 /dev/hdb however I did not
> export anything on the mfsmaster, so I have 20G and
> http://ipa.ddr.ess:9425/mfs.cgi shows the same.
>
> du -sh on my client shows:
> mfsmaster:9421         19G 1001M   18G   6% /mnt/mfs
>
> It all appears good.
>
> The problem is that using nautilus to navigate (or from c-li)
> "nautilus /mnt/mfs " results in a>  5 minutes to show content?
> umounting and remounting doesn't seem to help or affect it.
>
> ls -al /mnt/mfs is very responsive however.
>
> I am following some hints I found at
> http://contrib.meharwal.com/home/moosefs
>
> I have assigned a VirtualIP to my moose hosts and the networking seems fine.
> I am accessing mfsmaster using the forward-facing/public IP from my client.
>
> Is there something else I need to investigate?
> Thank you for your time.
>
>
>