Stuck in Fast Recovery?

Online 4.10.UD2 SCO 3.2.4.2 At 17:49 on Saturday I started the build of a huge index. At around 10:40 on Sunday, around 17 hours later, the box suffered a loss of power. It's essentially a read-only database; there were no other transactions in progress at the time. Online promptly went into Fast (sic) Recovery and has been in every since. The logs show that physical recovery completed successfully. tbstat -l shows: RSAM Version 4.10.UD2 -- Fast Recovery -- Up 22:40:45 -- 75024 Kbytes Physical Logging Buffer bufused bufsize numpages numwrits pages/io P-1 30 256 30 0 0.00 phybegin physize phypos phyused %used 10139a 64000 2637 30 0.05 Logical Logging Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-1 0 256 1 0 0 0.0 0.0 address number flags uniqid begin size used %used 804906f4 1 U---C-L 1 110d9a 16000 1974 12.34 80490710 2 F------ 0 114c1a 16000 0 0.00 8049072c 3 F------ 0 118a9a 16000 0 0.00 80490748 4 F------ 0 11c91a 16000 0 0.00 tbstat -u shows: RSAM Version 4.10.UD2 -- Fast Recovery -- Up 22:44:20 -- 75024 Kbytes Users address flags pid user tty wait tout locks nreads nwrites 804019b4 ------D 316 informix console 0 0 0 3 23808 80401a14 ------D 0 informix console 0 0 0 0 0 80401a74 ------F 317 informix 0 0 0 0 0 80401ad4 ------F 318 informix 0 0 0 0 0 80401b34 ------F 319 informix 0 0 0 0 0 80401b94 ------F 320 informix 0 0 0 0 0 80401bf4 ------F 321 informix 0 0 0 0 0 80401c54 --R-X-- 0 sjw 0 0 0 6046419 30 8 active, 80 total so this isn't the old Long-Transaction problem which is (in)famous for requiring level-0 restores; rather it looks like a straight rollback of the index create; hence the 6 million reads supposedly. So this recovery /should/ terminate, right? However, I'm approaching 23 hours recovery time and things are starting to get a bit worrying. How long should I hang on before starting the restore? This is a business-critical system. I've searched the archives but nothing really seems to give me any kind of idea as to how l should expect this to take. We're long past the 17-hour mark of course. 4.10.UD2 is unsupported so I guess my chances of having it tbzero'd are apporximately nil. Is it worth me keeping the faith? This really is incredibly frustrating not being able to do anything and having no indication whatsoever as to how long it's going to take. It's the only thing about Online that I really hate. Do the other "big boys" like Oracle and Sybase make people sit around for hours waiting for their business-critical boxes to "decide" to become usable again? (Btw, the answer to the question "What are you running 4.10.UD2 on a business critical system for?" is "Waiting for Online to to be released on Linux"!!!!) Stephen