It's a Type 1 file. And editing any record even a new one in the file (really a directory) would result in the problem. I would think, if it was a bad spot on the disk, predictive support should have shown it by now. Even if it was bad, everything is mirrored with MirrorDisk/UX, LVM w/OnlineJFS. That LE should have gone stale and the mirror should have taken over. But it's a direction I haven't considered and worth looking into. Thanks.
As for it being large, even the small/new records did this. We left them there for a couple hours, waiting until we could bring the system down and it still never worked.
>>> [EMAIL PROTECTED] 01/27/04 04:56PM >>>
I had this happen a couple of times when I worked on an HP system. Turned out to be a bad spot on the disk drive. Then again how big is the como file? If the file is large it could take a while to bring it into memory, if it doesn't get a memory full error first.
_______________________________________________ u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users