Re: Fixing a botched StoreOnce Software store?

Re,

FYI the basic procedure established in a case with HP Support is to:

1. Bump to 7.03 as there are relevant fixes in this patch bundle
2. Stop the store and SO Software
3. Remove s.bad_integrity should it exist
4. Remove the house keeping queue
5. Remove any zero-sized regular file in the store (of which I had 611)
6. Start the store again, with tracing enabled, and check where you stand.

For me, this changed a number of error messages from "zero length file" to "no such file or directory", but I'm seemingly able to recycle and omnimm --delete_unprotected_media damaged media and have the store housekeep and compact again (it would not touch zero-length files, not even when retiring objects for deletion, so the manual removal seems necessary). I'm not going to try writing to it again before every broken medium is wiped. Sometimes verify will fail on opening the medium and lock up that medium, so it won't even be purged by delete_unprotected_media. I've found a restart of StoreOnceSoftware to cure this state.

Now a little script is working though some 1300 remaining suspect media I pushed to a limbo pool, verifying them[1], and pushing those that verify good back to the pool where they belong. What doesn't pass muster is recycled, SO restarted and finally unprotected media is purged. Let's see how it ends, the verifying chore will likely take another day.

[1] The key to scriptable verification is to find out how to call omnimver correctly for a B2D medium. I was so tired of clicking the GUI I tried everything until I found:

omnimver -deviceb2d-gateway-name-slotlocation-id

eg

omnimver -device B2D-1-G1 -slot da7c78c2_5317b729_09cf_1cf9

The location-id is the hex string you get from omnimm -list_pool in the Location column, where it looks like that:

# omnimm -list_pool B2D-1_MediaPool | head

Status Medium Label                  Location                               Full Protected
==========================================================================================
Poor   B2D-1_MediaPool_7855           [B2D-1: da7c78c2_5313c2aa_09cf_1be8 No   04/28/14 01:51:56
Poor   B2D-1_MediaPool_7856           [B2D-1: da7c78c2_5313c992_09cf_1bf0 No   04/28/14 02:36:30
Poor   B2D-1_MediaPool_7858           [B2D-1: da7c78c2_5313c992_09cf_1bf4 No   04/28/14 02:19:37
[...]

For some odd reason, the location id is not the same as the medium id, which gave me extra pause. Anyway, it's working now.

HTH,

Andre.