Dynamic File Services (DFS) volume move operation remains on scheduled status and does not complete.

  • 7009412
  • 22-Sep-2011
  • 27-Apr-2012


Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3
Novell Distributed File Services


When attempting to perform a Dynamic File Services (DFS) volume move operation, the job remains scheduled and does not complete. The following entries are visible in the /var/log/messages file on the server hosting the source volume when the DFS move job was created;

<date><time> <server_name> volmnd[9825]: Failed to find source volume
<date><time> <server_name> volmnd[9825]: Setting state to 6 for OperationID = 1316169870 (request 0x5aa3f0)


Verify that the NSS volume mount points for both the source and the target volumes are set to the default /media/nss/<vol_name>.

If this is not the case change the mount point of the source volume to the default before attempting the DFS move and do not set a different mount point when specifying the target volume during the creation of the move operation. If so desired the mount point can be changed after the move completes.

Additional Information

It should also be noted that the Service Location Protocol(SLP) and Novell Storage Management Services (SMS) plays an important role when performing DFS move operations. It should be verified that both SLP and SMS are working properly. This can be done by taking the following steps from the server console of the relevant servers;

1. Restart SLP by entering "rcslpd restart"
2. Now restart SMS by entering "rcnovell-smdrd restart". When restarting SMS verify it started properly by checking for the following entries within /var/log/messages:

<date><time> <server_name> smdrd[24914]: SMDR coming up
<date><time> <server_name> smdrd[24914]: Target name SERVER_NAME successfully advertised with SLP
<date><time> <server_name> smdrd[24914]: Loading TSA tsafs
<date><time> <server_name> smdrd[24914]: Module tsafs successfully loaded

3. Additionally to verify that TSAFS is loaded properly execute "/opt/novell/sms/bin/smsconfig -t" for example:

:~ # /opt/novell/sms/bin/smsconfig -t
The loaded TSAs are:

4. Now verify on both the source and target servers that SLP displays the SMDRD information for the relevant servers using "slptool findsrvs smdr.novell". The output can be limited by using grep eg. if the server name in question is "MYSERV" with an IP address of "" then the command can be "slptool findsrvs smdr.novell | grep -i myserv". The output should then look something like the below: