Using a shared_root resource

Edit online

A shared_root resource represents a directory that can be used as a root (/) directory by one or more diskless clients. The shared_root resource offers drastic improvements in deployment times compared to the regular root resource, especially on large machine groups.

Anytime the client performs a network boot, the client STNFS mounts the directory specified as the shared_root directory over the root (/) directory to gain access to the shared_root directory. The shared_root directory remains mounted over the root (/) directory on the client as long as the client is running.

Because STNFS is used to mount the shared_root directory, any change made by a client to its root file system is kept local and is invisible to other clients and to the server of the shared_root resource. Any change a client makes to its root file system is also lost when the client is rebooted.

You can only use a shared_root resource with stateless clients. A regular root resource is required for clients that need persistence across reboots.

Note: Whenever the shared_root resource is deallocated, NIM changes only the client's configuration, so the client no longer uses the shared_root directory. NIM does not remove the common directory.

Note: Performing the sync_roots operation may leave the shared_root resource in the sync_roots Rstate which prevents the resource from being used. As a workaround, either redefine the shared_root resource or forcefully reset the master object to reset the shared_root state.