throatmonster Posted July 31, 2002 Report Share Posted July 31, 2002 I've been working with Dantz for some time now on various lockup problems with Retrospect Server 5.0 running on OSX (10.1.5). I've noticed is that Retrospect tends to lock up during or immediately after writing to the log file, especially when there is any other disk I/O activity on the drive (internal IDE boot drive) that Retrospect writes it's log files to. I'm beginning to suspect some kind of issue with disk I/O contention in OSX when Retrospect is using the internal drive. For those of you that see spurious lockups in Retrospect under OSX: can you review the lockups and establish any patterns of lockups that seem to be related to logfile writing? Is anyone out there making heavy use of the save volume that OSX writes it's logfiles to, that is *not* experiencing any lockup problems? Thanks for any feedback. Link to comment Share on other sites More sharing options...
CallMeDave Posted July 31, 2002 Report Share Posted July 31, 2002 In reply to: Is anyone out there making heavy use of the same volume that OSX writes it's logfiles to, that is *not* experiencing any lockup problems? When you say "making heavy use of" do you mean doing _other_ things while Retrospect is running? What would you define as 'heavy use?' Running Mail.app? Running a Photoshop filter? I've never seen Retrospect simply lock up (although I have seen memory leaks in LaunchCFMApp, and I have seen that process crash too). What are _your_ experiences that lead you to this suspicion? Dave Link to comment Share on other sites More sharing options...
throatmonster Posted August 2, 2002 Author Report Share Posted August 2, 2002 >> What are _your_ experiences that lead you to this suspicion? Over the last month, I've experienced and documented over a dozen lockups and/or quits when Retrospect is running. By comparing the logs to what's on the screen when the lockup happens, it is apparent that Retrospect most commonly locks up or quits immediately after writing to it's log file. I've now moved Retrospect to a completely different machine, and have had 1 quit already (first nightly script run on new machine). It had made it's last entry of a particular script's run, but hadn't started the next script yet. I've seen reports floating around about some weaknesses that OSX has regarding file contention when writing to disk, although I can't profess to understand the actual technical issue. I'm just wondering if this is affecting Retrospect's stability. Link to comment Share on other sites More sharing options...
CallMeDave Posted August 2, 2002 Report Share Posted August 2, 2002 In reply to: I've now moved Retrospect to a completely different machine, and have had 1 quit already (first nightly script run on new machine). That just amazes me, since I have run Retrospect on at least 6 different OS X machines and have never seen it 'lock up.' I've seen LaunchCMFApp crash, but never had the machine freeze. What, if anything, is common between the two machines? Did you bring any particular hardware from the first over to this new one? Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.