Re: Marking a chunk up

Just because theres a chance there may be damage doesnt mean we should need tech support to dial in. A simple warning message on the 'onchunkup' command, or onspaces should suffice. This error occured in the first place because of a non-related scsi error (which I dont think affected the disk). BTW - onspaces only works if you have mirroring (which I dont! :-( ) Madison Pruet wrote in message <36ED12E7.907123A3@informix.com>... >Because the chunk was marked down for a reason, usually because of some type of >inconsistancy or hardware failure. If the underlying reason for the chunk being >marked down is not resolved, then simply marking the chunk up will usually result >in data corruption. > >Kai Shen wrote: > >> you may try 'onspaces -s -O', but I must admit, it didn't work on our machine. >> I also would like to know why Informix keeps this as such a secret. >> >> Regards, >> Kai >> >> Mike Aubury schrieb: >> >> > Is there any way to mark an online chunk up, after it has gone down without >> > doing a restore. >> > >> > (Assuming that the data is ok etc.) >> > >> > TIA > > >

Mike Aubury wrote: > > Just because theres a chance there may be damage doesnt mean we should need > tech support to dial in. > > A simple warning message on the 'onchunkup' command, or onspaces should > suffice. This error occured in the first place because of a non-related scsi > error (which I dont think affected the disk). > > BTW - onspaces only works if you have mirroring (which I dont! :-( ) No onspaces will work without mirroring in versions 7.21 or later it just depends on why/how the chunk has been marked down. If it was from a simple disk I/O error the chunk will be marked 'down' and onspaces CAN indeed mark it back up. However if the chunk is offline because a restore was not completed it will have been marked 'inconsistent' and onspaces cannot (or will not it really does not matter) mark such a chunk online only tech support can. Art S. Kagel