RE: Disk Crash
I am facing a similar situation with one of my systems. In my case I
had mirrored rootdbs. My primary disk failed so I allocated a different
area on another disk and set the symbolic link to the new area. I can
bring the new rootdbs primary chunk online through mirroring. But every
time that I sut the system down and startup again the primary rootdbs is
marked as being down. And I set similar messages in the online.log
file. We continue to use the system with the mirrored copy of rootdbs
but need to find a way to get back to the safety of a mirrored rootdbs
that recovers fully.
Regards
Malcolm
-----Original Message-----
From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]
On Behalf Of Neil Truby
Sent: 20 September 2004 22:27
To: informix-list@iiug.org
Subject: Re: Disk Crash
Er, am I missing something?
You had a link to a chunk on disk A.
Disk A failed.
So you changed the link to point to a completely unconnected chunk on
disk B. Now you're wondering why the data that used to be on disk A
isn't by magic now on disk B just because you retrospectively switched a
symlink.
I am missing something, aren't I ...?
"Roger Cariah" <rogerc@ppsl.co.tt> wrote in message
news:cinbm3$n9g$1@news.xmission.com...
>
>
> Hi,
>
> One of my physical disk that had the roodbs critical chunk crashed. I
> had symbolic links to these disks so I relocated the symbolic link to
> a new chunk and proceeded to initialize my instance. I was unable to
> do so, and got the following on my log file:
>
> :47:31 Assert Failed: chunk failed sanity check
>
> 12:47:31 Informix Dynamic Server Version 7.31.FC5
> 12:47:31 Who: Session(1, root@olympus.ppsl.co.tt, 0, 76079144)
> Thread(6, main_loop(), 204856028, 1)
> File: rspartn.c Line: 7354
> 12:47:31 Results: Chunk 1 is being taken OFFLINE.
> 12:47:31 Action: Restore chunk from archive. If this is a temporary> dbspace
> chunk, drop and add the dbspace to enable it.
> 12:47:32 See Also: /tmp/af.3ee09a3
> 12:47:32 Process exited with return code 1: /bin/sh /bin/sh -c
> /informix/rt/exe /etc/ppsl_log_full.sh 3 4 "Chunk is off-line, mirror> is
> active: 5369532744." "ch unk fa 12:47:32 I/O error, Primary Chunk
> '/informix/rt/chunks/rchkd' -- Offline (sanity)
>
> Any ideas as to why I'm getting the above messages? I am trying to
> avoid doing a cold restore but will consider this as a last resort.
> Any suggestions as to my next move/checks before pursing this cold
> restore.
>
> much thanks
> roger
>
>
> The information in this communication and any attachments are deemed
> by
PPSL
> to be confidential and may be legally privileged and protected from
> disclosure. It is intended solely for the addressee. If you are not
> the intended recipient, any use, review, dissemination, distribution
> or
copying
> of this information is strictly prohibited. Please notify the sender
> and delete this message and any attachments immediately from your
> system. PPSL will not be held liable for any incomplete transmission
> of this
message
> nor any delay in its receipt.
>
>
> sending to informix-list
sending to informix-list
Online? IDS?
"malcolm weallans" <malcolm.iiug@btopenworld.com> wrote in message
news:ciono3$qss$1@news.xmission.com...
>
> I am facing a similar situation with one of my systems. In my case I
> had mirrored rootdbs. My primary disk failed so I allocated a different
> area on another disk and set the symbolic link to the new area. I can
> bring the new rootdbs primary chunk online through mirroring. But every
> time that I sut the system down and startup again the primary rootdbs is
> marked as being down. And I set similar messages in the online.log
> file. We continue to use the system with the mirrored copy of rootdbs
> but need to find a way to get back to the safety of a mirrored rootdbs
> that recovers fully.
>
> Regards
>
> Malcolm
>
> -----Original Message-----
> From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org]
> On Behalf Of Neil Truby
> Sent: 20 September 2004 22:27
> To: informix-list@iiug.org
> Subject: Re: Disk Crash
>
>
> Er, am I missing something?
> You had a link to a chunk on disk A.
> Disk A failed.
> So you changed the link to point to a completely unconnected chunk on
> disk B. Now you're wondering why the data that used to be on disk A
> isn't by magic now on disk B just because you retrospectively switched a
> symlink.
>
> I am missing something, aren't I ...?
>
> "Roger Cariah" <rogerc@ppsl.co.tt> wrote in message
> news:cinbm3$n9g$1@news.xmission.com...
> >
> >
> > Hi,
> >
> > One of my physical disk that had the roodbs critical chunk crashed. I
> > had symbolic links to these disks so I relocated the symbolic link to
> > a new chunk and proceeded to initialize my instance. I was unable to
> > do so, and got the following on my log file:
> >
> > :47:31 Assert Failed: chunk failed sanity check
> >
> > 12:47:31 Informix Dynamic Server Version 7.31.FC5
> > 12:47:31 Who: Session(1, root@olympus.ppsl.co.tt, 0, 76079144)
> > Thread(6, main_loop(), 204856028, 1)
> > File: rspartn.c Line: 7354
> > 12:47:31 Results: Chunk 1 is being taken OFFLINE.
> > 12:47:31 Action: Restore chunk from archive. If this is a temporary> > dbspace
> > chunk, drop and add the dbspace to enable it.
> > 12:47:32 See Also: /tmp/af.3ee09a3
> > 12:47:32 Process exited with return code 1: /bin/sh /bin/sh -c
> > /informix/rt/exe /etc/ppsl_log_full.sh 3 4 "Chunk is off-line, mirror> > is
> > active: 5369532744." "ch unk fa 12:47:32 I/O error, Primary Chunk
> > '/informix/rt/chunks/rchkd' -- Offline (sanity)
> >
> > Any ideas as to why I'm getting the above messages? I am trying to
> > avoid doing a cold restore but will consider this as a last resort.
> > Any suggestions as to my next move/checks before pursing this cold
> > restore.
> >
> > much thanks
> > roger
> >
> >
> > The information in this communication and any attachments are deemed
> > by
> PPSL
> > to be confidential and may be legally privileged and protected from
> > disclosure. It is intended solely for the addressee. If you are not
> > the intended recipient, any use, review, dissemination, distribution
> > or
> copying
> > of this information is strictly prohibited. Please notify the sender
> > and delete this message and any attachments immediately from your
> > system. PPSL will not be held liable for any incomplete transmission
> > of this
> message
> > nor any delay in its receipt.
> >
> >
> > sending to informix-list
>
>
> sending to informix-list
On Tue, 21 Sep 2004 02:20:13 -0400, malcolm weallans wrote:
Did you just relink and restart the engine? No, try either of the following:
1 - Shutdown
2 - dd the mirror chunk to the replacement chunk
3 - restart
OR
1 - Shutdown
2 - relink the original chunk link to the current mirror
3 - relink the original mirror link to the replacement chunk
4 - restart
5 - drop the 'mirror' chunk
6 - readd the mirror chunk.
Art S. Kagel
> I am facing a similar situation with one of my systems. In my case I had
> mirrored rootdbs. My primary disk failed so I allocated a different area on
> another disk and set the symbolic link to the new area. I can bring the new
> rootdbs primary chunk online through mirroring. But every time that I sut
> the system down and startup again the primary rootdbs is marked as being
> down. And I set similar messages in the online.log file. We continue to
> use the system with the mirrored copy of rootdbs but need to find a way to
> get back to the safety of a mirrored rootdbs that recovers fully.
>
> Regards
>
> Malcolm
>
> -----Original Message-----
> From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On
> Behalf Of Neil Truby
> Sent: 20 September 2004 22:27
> To: informix-list@iiug.org
> Subject: Re: Disk Crash
>
>
> Er, am I missing something?
> You had a link to a chunk on disk A.
> Disk A failed.
> So you changed the link to point to a completely unconnected chunk on disk
> B. Now you're wondering why the data that used to be on disk A isn't by
> magic now on disk B just because you retrospectively switched a symlink.
>
> I am missing something, aren't I ...?
>
> "Roger Cariah" <rogerc@ppsl.co.tt> wrote in message
> news:cinbm3$n9g$1@news.xmission.com...
>>
>>
>> Hi,
>>
>> One of my physical disk that had the roodbs critical chunk crashed. I had
>> symbolic links to these disks so I relocated the symbolic link to a new
>> chunk and proceeded to initialize my instance. I was unable to do so, and
>> got the following on my log file:
>>
>> :47:31 Assert Failed: chunk failed sanity check
>>
>> 12:47:31 Informix Dynamic Server Version 7.31.FC5 12:47:31 Who:
>> Session(1, root@olympus.ppsl.co.tt, 0, 76079144)
>> Thread(6, main_loop(), 204856028, 1)
>> File: rspartn.c Line: 7354
>> 12:47:31 Results: Chunk 1 is being taken OFFLINE. 12:47:31 Action:>> Restore chunk from archive. If this is a temporary dbspace
>> chunk, drop and add the dbspace to enable it.
>> 12:47:32 See Also: /tmp/af.3ee09a3
>> 12:47:32 Process exited with return code 1: /bin/sh /bin/sh -c
>> /informix/rt/exe /etc/ppsl_log_full.sh 3 4 "Chunk is off-line, mirror is>> active: 5369532744." "ch unk fa 12:47:32 I/O error, Primary Chunk
>> '/informix/rt/chunks/rchkd' -- Offline (sanity)
>>
>> Any ideas as to why I'm getting the above messages? I am trying to avoid
>> doing a cold restore but will consider this as a last resort. Any
>> suggestions as to my next move/checks before pursing this cold restore.
>>
>> much thanks
>> roger
>>
>>
>> The information in this communication and any attachments are deemed by
> PPSL
>> to be confidential and may be legally privileged and protected from
>> disclosure. It is intended solely for the addressee. If you are not the
>> intended recipient, any use, review, dissemination, distribution or
> copying
>> of this information is strictly prohibited. Please notify the sender and
>> delete this message and any attachments immediately from your system. PPSL
>> will not be held liable for any incomplete transmission of this
> message
>> nor any delay in its receipt.
>>
>>
>> sending to informix-list
>
>
> sending to informix-list