Why is my log full of these shfs outputs?

Feb 12 22:11:21 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxDB No such file or directory
Feb 12 22:11:21 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxData No such file or directory
Feb 12 22:11:25 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxDB No such file or directory
Feb 12 22:11:25 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxData No such file or directory
Feb 12 22:11:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxDB No such file or directory
Feb 12 22:11:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxData No such file or directory
Feb 12 22:11:27 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxDB No such file or directory
Feb 12 22:11:27 Tower emhttp: get_filesystem_status: statfs: /mnt/user/DropboxData No such file or directory
Feb 12 22:11:33 Tower shfs/user: shfs_readdir: fstatat: 26bfi?^B (2) No such file or directory
Feb 12 22:11:33 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk5/TimeMachine/<machine_name>.sparsebundle/bands (2) No such file or directory
Feb 12 22:11:49 Tower shfs/user: shfs_readdir: fstatat: 26bfi?^B (2) No such file or directory

I've deleted those DropboxD[ata/B] directories/shares. And I just checked on the TimeMachine sparsebundle, and that directory does exist and contains files. I'm not currently using TimeMachine, so I may just archive those and remove the share as well. Do I need to do a system reboot for these emhttp/shfs/user loggings to go away? They just seem unnecessary and clutter -- unless something is FUBAR about my config.