UPDATE: KZPAC/SWXCR with V5.1B pk4
From: Adametz, Bluejay (bluejay_at_fujigreenwood.com)
Date: 08/05/04
- Previous message: Maglinger, Paul: "Perl running slow after migration from 5.1a to 5.1b PK3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 05 Aug 2004 12:05:08 -0400 To: tru64-unix-managers@ornl.gov
Peter Gergen and Martin Koerfer, as well as HP, suggested that the problem
might be with the ddr.db and/or ddr.dbase files. They are identical between
the working(standalone) system and the non-working(clustered) systems. And,
according to HP (upon review), the SWXCR controller isn't treated as a SCSI
device anyway.
Because of the tight schedule I have on this project, I may be forced to
drop back to patch kit 3 if HP doesn't come up with something soon.
More news as it happens...
Original question:
> I just built a new cluster and, while the non-clustered
> system I started
> with has no problems, when I boot the cluster system, neither
> cluster member
> can access it's SWXCR disks. hwmgr shows the disks, but
> attempting to even
> show the disk label results in "No such device or address". Before
> attempting to access the disk, drdmgr shows a server for the
> disks, but
> afterwards, it reports "No Server".
- Bluejay Adametz
Conformity is the refuge of the unimaginative.
- Previous message: Maglinger, Paul: "Perl running slow after migration from 5.1a to 5.1b PK3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
