I've used the upstream module for our production cephfs cluster, but i've
noticed a bug where timestamps aren't being updated correctly.
Modified files are being reset to the beginning of Unix time.
It looks like this bug only manifest itself in applications like MS Office
where extra metadata is added to files. If I for example modify a text
file in notepad everything is working fine, but when I modify a docx (or
.xls for that matter), the timestamp is getting a reset to 1-1-1970.
You can imagine that this could be a real dealbreaker for production use
(think of backups/rsyncs based on mtimes which will render useless).
Further more the return values for free/total disk space is also not
working correctly when you mount a share in Windows. My 340TB cluster had
7.3EB storage available in Windows ;) This could be fixed with a
workaround by using a custom "dfree command =" script in the smb.conf,
but VFS will override this and thus this script will not work (unless you
remove the lines of codes for these disk operations in vfs_ceph.c).
My experience with the VFS module is pretty awesome nonetheless. I really
noticed an improvement in throughput when using this module instead of an
re-export with the kernel client. So I hope the VFS module will be
maintained actively again any time soon.
On Fri, 6 Feb 2015, Sage Weil wrote:
On Fri, 6 Feb 2015, Dennis Kramer (DT) wrote:
Hi,
Is the Samba VFS module for CephFS actively maintained at this moment?
I haven't seen much updates in the ceph/samba git repo.
You should really ignore the ceph/samba fork; it isn't used. The Ceph VFS
driver is upstream in Samba and maintained there.
That said, it isn't being actively developed at the moment, but I'm hoping
to change that shortly! We do some basic nightly testing in the ceph lab
but I'd be very interested in hearing about users' experiences.
Thanks!
sage
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
