Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 11749 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Disk space used by Sophos

markdu

Hi,

I am hoping that someone here can advise me on how to free up disk space after updates or reconfigure Sophos update manager to delete old update directories automatically.

These directories are using up enormous amounts of disk space. I have been deleting them manually (all update directories in windows\temp\sophos_autoupdate1), except for the latest one of course. I would have thought that the update manager would have done this for me.

The first time I did this I recovered 20Gb of disk space.

I am running Sophos on WinXP Pro 32bit

Any ideas anyone?

:15571


This thread was automatically locked due to age.
Parents
  • 0

    HI,

    I would suspect that something is locking the temp directory under sophos_autoupdate1  and as a result it isn't being deleted after the update.  Then on the next update it has to create another directory.

    I would suggest maybe using ProcessExplorer to find any open handles to any of the files or folders in the sophos_autoupdate1 directory.  Maybe something like an indexing service is locking the files during the update so they can't be removed at the end.

    If you can capture an update happening whilst running ProcessMonitor that could also offer some insight on what might be going wrong.  It seems like a runtime thing to me so I don't believe a reinstall would help.

    ProcessMonitor and ProcessExplorer can be found here:

    http://technet.microsoft.com/en-gb/sysinternals


    Regards,

    Jak 

    :15583
Reply
  • 0

    HI,

    I would suspect that something is locking the temp directory under sophos_autoupdate1  and as a result it isn't being deleted after the update.  Then on the next update it has to create another directory.

    I would suggest maybe using ProcessExplorer to find any open handles to any of the files or folders in the sophos_autoupdate1 directory.  Maybe something like an indexing service is locking the files during the update so they can't be removed at the end.

    If you can capture an update happening whilst running ProcessMonitor that could also offer some insight on what might be going wrong.  It seems like a runtime thing to me so I don't believe a reinstall would help.

    ProcessMonitor and ProcessExplorer can be found here:

    http://technet.microsoft.com/en-gb/sysinternals


    Regards,

    Jak 

    :15583
Children
No Data