| Title: | WinNT-Clusters |
| Notice: | Info directories moved to DECWET::SHARE1$:[NT_CLSTR] |
| Moderator: | DECWET::CAPPELLOF |
| Created: | Thu Oct 19 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 863 |
| Total number of notes: | 3478 |
I have a customer running NT Clusters on AlphaServer 2100's
who claims that his file shares were lost following a reboot
of the Cluster. He claims that following the reboot all the
file shares were "grayed out" and that he had to delete and
recreate the file shares to get them to work. Since he has
over 300 file shares, this is a lot of work and he does not
want to go through this again.
Has anyone else seen this problem or have any suggestions
on recreating this many file shares with user protections
should the shares be lost in a future reboot.
Thanks in advance for any help,
Hill...
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 683.1 | CSC32::HOEPNER | A closed mouth gathers no feet | Thu Mar 13 1997 17:39 | 6 | |
Which version of NT Clusters is your customer running?
How long did he wait before determining the shares were gone.
Sometimes it takes a while for the devices to come on line.
| |||||
| 683.2 | Customer is running NT Clusters V1.0 with Service Pack 1 | PRMS01::HCARTER | M. Hill Carter @DTN 339-7781 | Fri Mar 14 1997 11:07 | 2 |
The Customer is running NT Clusters V1.0 with Service Pack 1.
| |||||
| 683.3 | MPOS01::naiad.mpo.dec.com::mpos01::cerling | I'[email protected] | Mon Mar 17 1997 10:21 | 9 | |
I would tend to agree with Mary Jo's assessment. SP1 caused the failover time of shares to increase significantly. If, during the reboot, the shares came up on the 'wrong' system, and they were set to failback, then you would have this timing problem. I noticed that failover took up to thirty seconds per share. Have your customer apply SP2. I think that fixed the timing problem. tgc | |||||