Hi,
Here is the summary with my advfs mkfdmn problem.
thank you for the replies from:
digital_at_astro.ocis.temple.edu (Balaji)
Viktor Holmberg.
Balaji gave me some indepth guidance of things to check such
as checking the disklabel on node 2, checking the asecdb file
on both nodes to make sure the are the same with
sum /var/ase/config/asecdb.... etc.
Viktor gave me an excellent suggestion also.
That was making sure the disk wasn't reserved for node 1 by
doing a scu -f /dev/rrz??? release device and then trying to
reserve it on node 2 with scu -f /dev/rrz??? reserve device.
however, Digital (Compaq) CSC actually helped me out on this,
although there wasn't really a fix.
We tried totally deleting the devices in the HSZ and then re-creating
them. We found any disk we tried to initialize on node 2 came up with
the error. The resulting fix was to reboot the ASE cluster and all was
well after that. The CSC and I believe the root of the problem is the
old version of DU we are running which is 3.2g and we do not have
any patches on the system except one for ADVFS. CSC suggested
installing a jumbo patch, but we are in the planning stage of upgrading the
system to the latest DU version with the most recent patches. I'll
hold off on interim patches for now.
original question follows.
thanks,
Allan
> ----------
> From: SIMEONE, Allan J.
> Sent: Tuesday, October 06, 1998 11:41 AM
> To: 'alpha-osf-managers_at_ornl.gov'
> Subject: advfs mkfdmn problem
>
> Hello All,
>
> I'm having a problem creating an advfs domain. We have an
> ASE cluster with 2 DU3.2G systems. The disks are connected
> through each system with dual HSZ50's.
>
> I added 2 rz40 disks in the ba356 shelf and mirrored them through
> the HSZ on node 1 of the cluster. If I log on node 2 and go into
> hszterm, I see the added disks which are mirror set M14.
>
> I was asked to add an ASE service with the disks on node1. I
> made the advfs domain with no problem and then the fileset and
> added the ase service. I was then asked to have the service on
> node 2 instead of node 1.
>
> So, since I don't ASE too well yet, I decided to test some things
> with it. Instead of modifying the service to make node 2 the primary
> node, I decided to delete the service to see what happens, such as
> will it keep my test data on the disk and not delete it, etc....
>
> Anyway, that test failed miserably as it hung ASE and crashed node
> 1 when I went to delete the service, but that isn't the reason for this
> mail :-)
> It did keep my data if anyone is interested :-)
>
> Upon reboot, I went into ASE and noiticed the service did delete. I
> removed
> the fileset and removed the advfs domain for the disk on node 1
> (as we had to rename the domain also) using the appropriate commands
> with advfs (rmfset and rmfdmn).
>
> I then went on node 2 and proceeded to add the advfs domain there for the
> same disks with mkfdmn and an error comes up saying...
>
> Error checking for overlapping partitions: No domain definition
> /etc/fdmns/deglance_dmn mkfdmn: can't create new domain 'glcsam_dmn'
>
> The deglance_dmn does exist but on node 1 with an ASE service. If I go
> back to node 1, I can create the domain successfully. I believe I can
> just
> go ahead and create everything on node 1 and make the ase service primary
> on node 2, but I would like to know if I have a major problem here as I
> can't
> create an advfs domain on node 2.
>
> Anyone know why I'm having a problem creating an advfs domain on node 2?
>
> I already tried removing /dev/*z41* on both nodes and recreated them with
> MAKE_RAID_LUNS, but that didn't do anything. I am trying to create the
> advfs domain on partition C.
>
> thanks,
> Allan
>
Received on Thu Oct 08 1998 - 19:44:58 NZDT