distributed filesystem over internet/VPN Post: 302696103

Sponsored Content

Special Forums Hardware Filesystems, Disks and Memory distributed filesystem over internet/VPN Post 302696103 by Domino on Tuesday 4th of September 2012 09:51:46 AM

09-04-2012

Registered User

distributed filesystem over internet/VPN

On this forum was already posted similar question, but it was 4 years ago and didn't give me answers.

I have two groups of engineers that works in far locations connected via VPN. Physically, the connection is a DSL. Currently we have a linux server in one location that provide files over SMB/CIFS. Thus live of people in the second location is a nightmare.

I can change a lot on the server, but one thing must remain. Workstation need to access files using standard windows mechanisms (SMB/CIFS). No extra software (drivers, clients etc).

To solve it, I want to install second server in the second location and use a distributed filessystem that mainly works in replication mode. Files on both servers will be redistributed by samba in the local network.

There is a great list of distributed filesystems on wikipedia.

The most advanced seams to be lustre. But I have some doubts if it will work for me. Lustre is dedicated to a true cluster with a high speed connection (10GigE or special hardware like RDMA). It also stripe space from all nodes, while I rather want to have replication/mirroring.

XtreemFS seams to be more adequate to me. At least from functional site. But it seams that it is JAVA based solution... I'm very afraid for the performance. There is also some limitation for read/write replication.

GlusterFS: according to some blog this filesystem is not good choice for high-latency connection like DSL. (sorry, forum disallow me to publish valid link, add http prefix: joejulian.name/blog/glusterfs-replication-dos-and-donts/)

What is your recommendation?
Had anyone similar problem?

Domino

View Public Profile for Domino

Find all posts by Domino

3 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Wanted: Geographically distributed filesystem solution

I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices. I want to evaluate several solutions, and I'm open to solutions ranging from free,...

2. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

Hi, I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local. Please tell me the commands which I can run...

3. IP Networking

Internet connection single interface through vpn

Hi. Can you please help me with a routing problem? There are 2 networks: 192.168.10.0/24 (eth0) 192.168.11.0/24 (eth0:1) The default gateway is 192.168.10.1 iPv4 routing is already enabled and working. With vpnc I've built up an VPN connection and can access my home network...

LEARN ABOUT SUNOS

xfs_freeze

xfs_freeze(8)                                                 System Manager's Manual                                                xfs_freeze(8)

NAME

       xfs_freeze - suspend access to an XFS filesystem

SYNOPSIS

       xfs_freeze -f | -u mount-point

DESCRIPTION

       xfs_freeze suspends and resumes access to an XFS filesystem (see xfs(5)).

       xfs_freeze  halts  new access to the filesystem and creates a stable image on disk.  xfs_freeze is intended to be used with volume managers
       and hardware RAID devices that support the creation of snapshots.

       The mount-point argument is the pathname of the directory where the filesystem is mounted.  The filesystem must be  mounted  to  be  frozen
       (see mount(8)).

       The  -f flag requests the specified XFS filesystem to be frozen from new modifications.  When this is selected, all ongoing transactions in
       the filesystem are allowed to complete, new write system calls are halted, other calls which modify the  filesystem  are  halted,  and  all
       dirty data, metadata, and log information are written to disk.  Any process attempting to write to the frozen filesystem will block waiting
       for the filesystem to be unfrozen.

       Note that even after freezing, the on-disk filesystem can contain information on files that are still in the process of  unlinking.   These
       files will not be unlinked until the filesystem is unfrozen or a clean mount of the snapshot is complete.

       The  -u  flag  is used to un-freeze the filesystem and allow operations to continue.  Any filesystem modifications that were blocked by the
       freeze are unblocked and allowed to complete.

       One of -f or -u must be supplied to xfs_freeze.

NOTES

       A copy of a frozen XFS filesystem will usually have the same universally unique identifier (UUID) as the original, and  thus  may  be  pre-
       vented from being mounted.  The XFS nouuid mount option can be used to circumvent this issue.

       In  Linux  kernel version 2.6.29, the interface which XFS uses to freeze and unfreeze was elevated to the VFS, so that this tool can now be
       used on many other Linux filesystems.

SEE ALSO

       xfs(5), lvm(8), mount(8).

                                                                                                                                     xfs_freeze(8)