New answers tagged

3

The reason you're having problems getting an answer to your question is that it isn't really a matter of advantages or disadvantages. The access modes are very different, and it's therefore a matter of to what use you are going to put your server. File mode is the classic mode. Your file system is handled by your server, and lots of NFS clients can use the ...


1

The FS8600s are strictly UTF-8 (maybe UTF-16, but I think I recall UTF-8) compliant, so if you, in any way, try to put files with non-UTF8 compliant names on it (through CIFS or NFS or anything else), you will get the very non-descript 'Permission denied' error, you can put the files there, with a filename that is, apparently, the same, as long as it's UTF-8 ...


1

pNFS support file share and byte-range locks as NFSv4. Please refer to the address https://tools.ietf.org/html/rfc5661#section-12.5.1


1

As per RFC 5661 (nfs 4.1 incl. pnfs) https://tools.ietf.org/html/rfc5661#section-12.5.1 The requirement of NFSv4.1 that all user access rights MUST be obtained through the appropriate OPEN, LOCK, and ACCESS operations is not modified with the existence of layouts. Layouts are provided to NFSv4.1 clients, and user access still follows the rules of ...


0

Upon further inspection, the error kernel: nfsd: peername failed (err 107)! appears approximately every 6 seconds. The number seems to correspond to the connection_timeout option in the conf file, and indeed by stopping keepalived service, the error stops appearing altogether. It seems by using TCP_CHECK on port 2049, the NFS servers will log the "bad" ...



Top 50 recent answers are included