Hi, Is there a config to have the gluster NFS server start on boot? I'm having this weird issue where in a two brick replica (one offline temporarily) the NFS server will show as Online: N. The NFS server will only startup if I make a change to an option (such as change the cache size) or the second host comes up. The volume is however still mountable through glusterfs. Here are my configs: performance.cache-size: 1GB server.allow-insecure: on performance.io-thread-count: 8 auth.allow: 172.16.*.* storage.owner-uid: 36 storage.owner-gid: 36 nfs.disable: no performance.quick-read: off performance.read-ahead: off performance.io-cache: off performance.stat-prefetch: off cluster.eager-lock: enable network.remote-dio: enable cluster.quorum-type: none cluster.server-quorum-type: none nfs.register-with-portmap: on Any suggestions? Thanks, Andrew -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140203/f35c6e21/attachment.html>
Vijay Bellur
2014-Feb-03 10:40 UTC
[Gluster-users] Gluster NFS server not starting on boot
On 02/03/2014 04:03 PM, Andrew Lau wrote:> Hi, > > Is there a config to have the gluster NFS server start on boot? > > I'm having this weird issue where in a two brick replica (one offline > temporarily) the NFS server will show as Online: N. The NFS server will > only startup if I make a change to an option (such as change the cache > size) or the second host comes up. > > The volume is however still mountable through glusterfs. > > Here are my configs: > performance.cache-size: 1GB > server.allow-insecure: on > performance.io-thread-count: 8 > auth.allow: 172.16.*.* > storage.owner-uid: 36 > storage.owner-gid: 36 > nfs.disable: no > performance.quick-read: off > performance.read-ahead: off > performance.io-cache: off > performance.stat-prefetch: off > cluster.eager-lock: enable > network.remote-dio: enable > cluster.quorum-type: none > cluster.server-quorum-type: none > nfs.register-with-portmap: on > > Any suggestions? >Looking up the nfs log file in /var/log/glusterfs might provide some clue. -Vijay