Re: [Moosefs-users] Question re: win32 client/access

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

You would need to consider your network topology (e.g. in our 
environment we have the moosefs master and chunk servers and mfs mount 
clients in their own back end network segment, and a virtual machine 
that runs mfsmount and samba is the access point or "gateway" into the 
file system for the windows users.  We tried to follow the design as one 
would do an iSCSI san, where dedicated "SAN" network segments are used 
for the back end storage to the application servers that is different 
from the front end facing network segments the end users and clients 
invoke the applications with.

You might also consider the amount of network IO operations that would 
be done between the windows machines and the (SCP operations?) mount 
point that exposes the mfsmount-ed file system. Where by depending on 
the speed of the network (100MB, GB ethernet) and the amount of 
concurent requests, you might find contention for the network link and 
this could reduce the performance of the file system as a whole. but 
this is entirely subjective .

But functionally there is no technical consideration why you could not 
run mfsmount on the mfsmaster node.

On 12-02-13 1:17 PM, JJ wrote:
> Now that our moosefs install is functional,
> We want to provide access to our Clients that are bound
> to a Window-based OS.
>
> I would like to know if mounting (using mfsmount, running ./configure
> per the client installl) on the mfsmaster is a good idea?
>
> If it suggested ok to do, then I can ask our Windows users to install
> WinSCP and then I'd alter the mfs user's $home directory to be /mnt/mfs
>