If I may quote Roseanne Roseannadanna, "...well, it's always something.  If it's not one thing it's another..."  Yikes!

I also wonder if that is true with XP disk arrays and MPE/iX 7.0 if you do NOT have MPEMX36A or MPEMX61? patch loaded?  I don't know about 6.5 or 6.0 releases.  We ran into a problem with the out-of-order posting of partial pages on restores that garbled database files (we weren't restoring many that weren't database files) until that driver patch was put on.

Thanks Lars!

Howard Hoxsie

-----Original Message-----
From: Lars Appel [mailto:[log in to unmask]]
Sent: Saturday, September 07, 2002 8:02 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Powering down a 3000


Howard wrote...

> As long as you have XM enabled for your Image databases you should have
> no difficulty upon returning to full power once your "crisis" is over.

Watch out. I seem to recall that the recent (non-hp) disk models do
not "cooperate with XM" to guarantee consistent data in case of power
failures. They provide "sector atomicity" but use "write on arrival"
so that XM cannot guarantee complete 4K pages were written in case of
a power failure. This is why the UPS Monitor process will cause some
forced system abort when it is notified "battery running out of power
soon". The system abort stops I/O from the software side, so the disc
drives can use the remaining time to post the queued writes.

Lars.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *