The state of the deduplication scheduler daemon, fsdedupschd, is maintained across reboots. If you started the fsdedupschd daemon prior to a reboot, the daemon is automatically restarted after the reboot. If you stopped the fsdedupschd daemon prior to a reboot, it remains stopped after the reboot. The default fsdedupschd daemon state is stopped.

You must enable deduplication on the file system before you can start or stop the scheduler daemon.

See Enabling and disabling deduplication on a file system.

The following command starts the fsdedupschd daemon:

# chkconfig --add fsdedupschd
# service fsdedupschd start

The following command stops the fsdedupschd daemon:

# service fsdedupschd stop
# chkconfig --del fsdedupschd