Starting and Stopping Nexfscli

 

It is also recommended that the nexfscli is used to manually start and stop the nexfs server.

 

Starting, stopping nexfs with nexfscli

 

To start nexfs run:

 

nexfscli server start

To nicely stop nexfs, run:

 

nexfscli server stop


 

While it is always advisable to perform a nice nexfs server stop, which pauses client traffic and attempts to flush any open buffers, if a  fast and hard stop of nexfs is required, run:

 

nexfscli server forcestop

 

Note: running a force stop is not recommended other than as a last resort, a force stop will not flush open data buffers to permanent storage, which could result in data corruption. 

 

Manually Starting Nexfs

 

the Nexfs server can be manually started using the synopsis

 

nexfs.server [-o OPTION][,OPTIONS[,..]  mountpoint

 

OPTIONS:

  allow_other   Required to allow users other than root to access the nexfs storage pool from the fuse mountpoint

  no_forget  Option must be included for NFS to work correctly

  mountpoint Must be provided at startup, this is the mountpoint where the Nexfs fuse filesystem will be mounted.

Example: nexfs.server -o allow_other,no_forget /mnt/nexfs

Manually Stopping Nexfs using the Advanced Management method

While Nexfs can be stopped by issuing a umount against the Nexfs fuse mountpoint, the umount method is highly discouraged unless a clean shutdown cannot be completed

It is recommended to use nexfscli to manually stop Nexfs, for advanced management users and automation Nexfs can be stopped programmatically using the Nexfs management file interface

Automatic startup and shutdown of Nexfs (systemd)

A systemd startup script for nexfs can be installed using nexfscli by running:

nexfscli installsystemdservice

Getting the Nexfs server status

 

To get the current Nexfs server status, run

 

nexfscli server status

 

Which for a running Nexfs server will result in output that includes the server status:

 

Nexfs Mountpoint: /mnt/nexfs
Server Status: OK
...