Problems restarting vxesfsd
Restarting vxesfsd fails if processes are accessing the ESFS mount point when NetBackup is attempting to shut it down.
See the following log to determine if this is the problem:
/usr/openv/esfs/log/ops/esfs-run.process_id
In the following example, the mount point directory is /space/d2c/storage.
Wed Jul 5 15:44:34 CDT 2017 Calling "umount /space/CC/storage"
to stop vxesfsd gracefully
umount: /space/d2c/storage: target is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
Wed Jul 5 15:44:45 CDT 2017 Sending SIGKILL to vxesfsd
Wed Jul 5 15:44:45 CDT 2017 Calling "umount /space/CC/storage"
after hard kill of vxesfsd
umount: /space/CC/storage: target is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
Wed Jul 5 15:44:45 CDT 2017 Sending SIGKILL to vxespNote that after the hard kill of vxesfsd, the target remains busy.
To check if any processes are using the ESFS mount point
- Unmount the mount directory:
umount mount_dir
or
lsof mount_dir
- Verify that the directory is not mounted:
mount | grep mount_dir
or
lsof | grep mount_dir
- Restart vxesfsd:
/usr/openv/esfs/bin/vxesfsd start /usr/openv/pdde/pdconfigure/pdde start