Post by: Xairbusdriver on March 24, 2009, 04:24:24 PM
Most of the time, there were reports of files that were out of order or that were being repaired. Just before opening this TS window, the scrolling stopped showing several orphaned files and "Indirect node 9992093 needs link count adjustment." That's fine with me, I have nothing against Indirect node 9992093. I think it is just as nice as node 9992092 and 9992094. Can occasionally hear some disk noises. Nothing is locked up. Force Quit and Activity Monitor agree that DU is behaving normally, if extremely slowly. DU is using a constant 1.1% of cpu cycles running 5 threads, messages sent is increasing, Virtual Memory is steady at 465.68. Report details scrolling again, mostly orphaned files, Indirect node adjustments, invalid first link in hard drive and a few "Whada you lookin at?!" lines. 
OK, I finally found something that needs more cpu cycles than Folding@Home will part with. I paused those processes and DU cpu usage jumped to 98+%. Obviously some work going on behind the scenes, working on the 856.1GB volume!
Still showing seven minutes remaining, but I'm not about to "Stop Repair" much less "Force Quit!" 
I doubt, however, that I will do this repair after so long a delay between this and the next one... 
Post by: Xairbusdriver on March 24, 2009, 06:46:44 PM
At least i won't have to ever do that again! 
Post by: Xairbusdriver on March 25, 2009, 11:12:44 AM
Post by: tacit on March 25, 2009, 10:57:32 PM
QUOTE(Xairbusdriver @ Mar 25 2009, 04:12 PM) <{POST_SNAPBACK}>
Went to bed before the repairs finished last night. Everything was fine this morning, "Repairs completed" message awaited me. I guess it just takes a good deal of time for finding and repairing 856GBs! Next time, I'll do a 'Check for needed problems.'
Orphaned and crosslinked files can take tremendous amounts of time to repair; I've seen cases where they can require more than 24 hours to complete, and heard of cases where repairs take longer than 48 hours.
Example the orphaned and crosslinked files carefully. Some of them are unquestionably going to be damaged.
Post by: Xairbusdriver on March 26, 2009, 01:51:37 PM
QUOTE
Exam[ine] the orphaned and crosslinked files carefully. Some of them are unquestionably going to be damaged.
Good advice, except there are several hundred thousand of them! This was my Time Machine BU drive and I suspect that's where the problems came from. Either because of errors in the very early stages of use or from 'simple' confusion about what was where. I've checked some of the most critical files, which are backed up elsewhere, also. The ones that are truly damaged will be those that I won't need/use for a year or so and have only one copy! 
My real problem is that I should really be using that drive for nothing but TM and get another for all the other methods I use for backups. I still think Apple is cahoots with HD makers...
At least the prices seem to be lower than a year ago.