Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 6 subscribers
  • Views 3931 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

Sophos AV Hangs

Lankidden

Hi Guys,

Along with many others, have now installed Sophos on MBP OSX 10.6.4. HD 350Gb, 250GB available. Initial scan displayed approx 500k files needed scanning, which went smoothly in background, until hanging at around 75k. I cancelled scan after around twenty minutes, and restarted scan some time later. Again the scan hung at around 75k, but this time I left it to sulk on it's own. Some two hours or so later an OS window came up saying that my launch disc was now full, and files needed to be deleted. Initially thinking this must be referring to some scratch disc I was not too concerned, but then I checked the available  space on the HD, and indeed available space was a big fat ZERO. After returning from a rapid visit to the facilities ( ! ! ! ! !) I rebooted, and was very relieved to see that available space had reverted to around 250Gb, so presumably all's well that ends well.

So, having made sure that both my Time Machine & external HD Back-ups are up to date, I am somewhat loath to go for a third scan.

Any suggestions as to what might be my problem, or is it just that Sophos, perish the thought, sadly couldn't recognise some sort of problem, and fell over in the attempt?

All thoughts and advice gratefully received.

Lankidden

Oxford UK

:1000215


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

    Hi Lankidden, 

    Thanks for posting this it helps a lot.

    Ive been looking into some of the reports of slow scanning times, scans seemingly sticking on certain files, and disk space getting used up.

    We have found that certain DMG files (newer ones produced by 10.6) can sometimes be mis-classified as UTF-16 rather than DMG.  

    This causes them to be scanned incorrectly, and if the DMG is of a suitably large size can result in the OS paging memory onto disk (so you see the disk getting used up).

    You can test this to see if this is the issue you are seeing.

    If you create a customer scan and configure it to scan your local drives and partitions.  

    Now configure it to not scan archive files, and add an exclusion for *.dmg (add any file first, then double click the entry to be able to just type *.dmg).

    Try running this scan.  If you are seeing the above issue then the scan should complete in a much better time, and shouldnt use up disk space at all.

    We have a code fix for the identified DMG mis-classification issue and this will be released in the next few weeks once it has completed testing.

    If the scan still causes the issue then please let me know and ill see what else we can look at to try and resolve this issue for you as soon as possible.

    Thanks

    :1000222
Reply
  • 0

    Hi Lankidden, 

    Thanks for posting this it helps a lot.

    Ive been looking into some of the reports of slow scanning times, scans seemingly sticking on certain files, and disk space getting used up.

    We have found that certain DMG files (newer ones produced by 10.6) can sometimes be mis-classified as UTF-16 rather than DMG.  

    This causes them to be scanned incorrectly, and if the DMG is of a suitably large size can result in the OS paging memory onto disk (so you see the disk getting used up).

    You can test this to see if this is the issue you are seeing.

    If you create a customer scan and configure it to scan your local drives and partitions.  

    Now configure it to not scan archive files, and add an exclusion for *.dmg (add any file first, then double click the entry to be able to just type *.dmg).

    Try running this scan.  If you are seeing the above issue then the scan should complete in a much better time, and shouldnt use up disk space at all.

    We have a code fix for the identified DMG mis-classification issue and this will be released in the next few weeks once it has completed testing.

    If the scan still causes the issue then please let me know and ill see what else we can look at to try and resolve this issue for you as soon as possible.

    Thanks

    :1000222
Children
No Data