From: MMP Rupp Wolfgang (Wolfgang.Rupp@mm-packaging.com)
Date: Tue May 13 2003 - 04:50:57 EDT
A late summary, but I wanted the issue solved first.
Problem was: each mirror split the systems see the split unit
as a new device. This prevents backup automation because of
broken AdvFS definitions. See below for original post.
The symptoms I described are normal behaviour for Tru64.
Solution: use ACS 8.7 and the "parent_wwid=[unit]" feature. This
makes sure that the new wwid for the new device is numerically
related to the parent unit's wwid. Therefore, each time the
mirror is split, the split off unit will get the same wwid and
the system will see it as the same device. Works fine now.
Caveat: do not delete the "unused" device files after a mirror
rebuild, or you _will_ get a new device with the next split.
Thanks to all who replied, especially Jan Mark Holzer of HP who
pointed me to "parent_wwid".
Wolfgang Rupp
Network Administrator
MM Packaging Europe GmbH
Floragasse 7
A-1040 Wien
Tel: +43 1 50257 238
Fax: +43 1 50257 260
---[original post]---
I got a weird problem here: with Command Scripter, a Unix cron
job triggers mirror splits. Additional units are then created
and presented to the cluster to "mount -o dual" for backup.
The problem is that with each split, the cluster sees the units
as new (additional) devices: last split I had /dev/disk/dsk57-60,
now I got 61-64. This is reproducible.
To automate split-mount-save, the split units have to be always
the same device number because of the file domain definitions.
What are we doing wrong? An example command scripter input for
split and rebuild is below.
---[end original post]---
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:18 EDT