When trying to add an NFS share to your LMI appliance's archive configuration you may see the error displayed in the screenshot below. This article explains the most frequently seen cause for this behavior, assuming the NAS file share can be successfully mounted.



This error is the result of the web application, not engine_archive, trying to do a test write on the NFS share being added to the archive configuration. After engine_archive has mounted the share the web application tries the test write using a binary named rtnfsscp in /loglogic/bin. rtnfsscp will attempt a test mount of the NFS share to /loglogic/tmp/test_mount then attempt moving a file /tmp/nfswritetestfile to /loglogic/tmp/test_mount. If the test mount fails or if the file fails to be moved to the mounted file share then rtnfsscp reports that result to the web application. The web page will then display the error shown in the screenshot.

This article explains what causes the "device can't be used for NAS" error in the LogLogic LMI web interface and how to fix the issue.

Only applies to ST physical appliances and virtual appliances in STVirtual or MXVirtual mode

Although various issues (mostly environmental or NAS-related) can cause LMI to fail to mount the file share (and is outside the scope of this article), in this scenario the mount succeeds but the test write fails therefore LMI has to deem the share unusable and subsequently unmounts it. The most frequent reason for why the rtnfsscp utility fails to write a file to the share is due to the file share, in the NAS configuration, being set to read-only rather than read-write. Due to there being too many NAS solutions available on the market we can't provide specific directions but we recommend reviewing the NAS configuration to ensure that clients are allowed to write to the file share. Note that this setting differs from standard file system permissions that are visible from the LMI client end.