Hi
Perhaps. But they (ZoL) say its production ready. It worked since
CentosOS 6.1 to 6.6 and still working. Problem occurs if we change the
NFS version. Not the ZFS. And the problem also exsist with XFS on CentOS
7. Also it works with all old Ubuntu Clients here. The main problem
seems to be the client which seems to use NFS features which are not
(yet) working! Also with XFS you need to use NFS 4.1 or you will have
the old links/nodes. problem too.
As you say the Solaris/BSD NFS Server Version seems to work. Thats what
the ZFS mailing list said. If it works under FreeBSD its the NFS Server...
I could try some other file systems... But I would also like to know
what the issue is. I am still wondering what the problem is. because on
the server everything looks fine.
Timo
On 05/04/2015 10:22 AM, John R Pierce wrote:
On 5/4/2015 1:09 AM, tballin wrote:
Hello,
we want to migrate to CentOS 7(.1) , Server, Client etc ...
Right now we need to suspend that because we have some serious issues
with NFS4 shared ZFS ( kernel module - zfs on linux project ) Volumes
and CentOS 7 clients.
Our current server are CentOS6.5, if we share a zfs volume and do the
following on this share: client A reads/access file "z.txt". Now
client B replaces (copy, move, unlink+link ) files "z.txt" with a new
different version and now client A reads/access the file "z.txt" (
and only the file - do not do anything which does a "stat" on the
file e.g. "cat z.txt") the old version/content is read. As long as
you do something that issues a "stat" for the file/dir.
I've used ZFS file systems on a NFS Server extensively on Solaris, and
a fair bit with FreeBSD 9.x, 10.1, and its never had any such
issues. AFAIK, ZFS on Linux is still considered experimental.
____ ESET 11570 (20150504) ____
The message was checked by ESET Mail Security.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
