Re: Expiration not working
2000-04-19 14:28:59
Subject: |
Re: Expiration not working |
From: |
Richard Sims <rbs AT BU DOT EDU> |
Date: |
Wed, 19 Apr 2000 14:28:59 -0400 |
>I saw this too last week! Investigation showed a very large I/O on a disks
>containing one of the databases. As soon as I broke the database mirror
>everything ran fine again.
Sounds almost like an internally triggered resync, for some reason.
I wonder if Q DB or other inspections would help uncover the cause?
I'm on the same 3.1.2.50 as you, Eric, but haven't encountered that (yet).
Richard Sims, BU
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Expiration not working, Brian Johnson
- Re: Expiration not working, Kirsten Gloeer
- Re: Expiration not working, Talafous, John G.
- Re: Expiration not working, Brian Johnson
- Re: Expiration not working, Mike Wiederkehr
- Re: Expiration not working, Talafous, John G.
- Re: Expiration not working, Richard Cowen
- Re: Expiration not working, Loon, E.J. van - SPLXM
- Re: Expiration not working, Joe Faracchio
- Re: Expiration not working,
Richard Sims <=
- Re: Expiration not working, Tab Trepagnier
- Re: Expiration not working, Matthew Glanville
- Re: Expiration not working, Richard Sims
- Re: Expiration not working, Brian Johnson
- Re: Expiration not working, Thomas A. La Porte
- Re: Expiration not working, Matthew Glanville
- Expiration not working, Brian Johnson [mailto:bjohnson
|
|
|