Re: Gluster vs NFS export sync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2014-07-11 at 14:22 +0530, Santosh Pradhan wrote: 
> On 07/11/2014 06:10 AM, Franco Broi wrote:
> > Hi
> >
> > Is there any way to make Gluster emulate the behaviour of a NFS
> > filesystem exported with the sync option? By that I mean is it possible
> > to write a file from one client and guarantee that the data will be
> > instantly available on close to all other clients?
> 
> I think FUSE also supports the sync option with mount similar to NFS.

There's 2 types of NFS sync, server and client but they behave very
differently. With sync at the client end, NFS just calls fsync on close
(I think), with sync at the server end, all writes are synchronous. 

Opening the file with O_SYNC also doesn't give the desired effect
although you'd think it would. NFS must have some way of communicating
the file attribute changes to all the clients immediately the write
completes.

> 
> Man page snippet for fuse(8):
> OPTIONS
>         Most of the generic mount options described in mount are 
> supported (ro, rw, suid, nosuid, dev,
>         nodev, exec, noexec, atime, noatime, sync, async, dirsync). 
> Filesystems are mounted  with
>         nodev,nosuid by default, which can only be overridden by a 
> privileged user.
> 
> Thanks,
> Santosh
> 
> >
> > Cheers,
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users@xxxxxxxxxxx
> > http://supercolony.gluster.org/mailman/listinfo/gluster-users
> 


_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux