Re: strange disk states

In article <MPG.23601d3e22eb76219897b1@xxxxxxxxxxxxxxxx>, John Santos
<john.santos@xxxxxxxxxxxxxxxx> writes:

Looks pretty strange.

(If you did a "show device" for a single shadow set (e.g. $ show device
dsa510:, or a single member disk (e.g. $ show device $44$DKA400:), it
would list the shadow set (DSA) disk followed by all the members, which
would be a little easier to read. I missread the status of DSA510: at
first due to the info being scattered all over the place.)

SHOW DEVICE DSA510: reports the same: one member in state copying (34%
now) and one in state merging (0% merged).

Anyway, I expect if a two member shadowset were being merged and you
added a third member, you would see the first two *both* in merge
state, with the 3rd member as a copy target, but that's *not* what
you see.

Right---all my shadow sets have just two members.

You see a 2-member set with one as merging, and the 2nd as a copy
target... Was there originally a third member (maybe on NADILA?)

No. NADILA mounts the shadow set when booted (it's a satellite and my
most powerful system---ALPHAserver 1200---but to keep power costs down I
boot it only when needed (using when running CSWB)). I've never even
experimented with a three-member shadow set. In any case, all was OK
AFTER the last shutdown of Nadila; when the problem occurred, NADILA was
not in the cluster and hasn't been booted since then.

that was originally in merge state, but got dismounted before the
merge completed? I think in this case, it show change the remaining
member to "member" status, and the copy should proceed from it, so
the status would resemble DSA520:, but maybe there's a bug if a
copy is in progress at the same time as the merge, and you drop
one of the "merging" disks, it doesn't change the status of the
other one.

Maybe.

P.S. I know who R. Daneel Steele

That's R. Daneel Olivaw (in THE CAVES OF STEEL, among other books)

is, and Gladia and Elijah, but
who is Nadila? (It's been a while since I read any old Asimov.)

A minor character, IIRC from THE NAKED SUN. When I set up my cluster, I
made a list of 6-character names in Asimov's works. There are quite a
few. Many are minor characters, but Palver and Mallow are relatively
major. I think the mode of the distribution is actually at 6
characters. Also, ALPHAs get female characters and VAXes get male ones.
:-)

.

Relevant Pages

  • Re: strange disk states
    ... SHOW DEVICE DSA510: reports the same: one member in state copying and one in state merging. ... Was there originally a third member (maybe on NADILA?) ... No. NADILA mounts the shadow set when booted (it's a satellite and my ... A minor character, ...
    (comp.os.vms)
  • Re: two questions about MINICOPY
    ... It sounds like you may be blurring the distinction between shadow set merges ... and shadow set member copies. ... then a node crash with member removals. ... shadow set while an HBMM minimerge recovery takes place and additional bits ...
    (comp.os.vms)
  • Re: shadow minicopy
    ... >> a write occurs while that shadow member is dismounted. ... Does the bitmap reside on ... The shadow set and its ... Write Bitmapare created at *dismount*. ...
    (comp.os.vms)
  • Re: (DIS)MOUNT/POLICY=MINICOPY in mixed VAX-ALPHA cluster
    ... > member of a shadow set on it and another member on another node. ... > logical disks consist of a shadow set of two physical disks with the ... > can I just dismount a member and benefit from the fast copy when I add ...
    (comp.os.vms)
  • Re: Bad Shadow set member
    ... So I had to manually mount omitting the first member. ... Am I missing a qualifier? ... Automatically reconstructs a former shadow set to the way it was ...
    (comp.os.vms)