+----- On Mon, 19 Jul 1999 14:20:21 CDT, "Mohler, Jeff" writes: | One of our customers is doing some evaluations of netapp. | While evaluating the new server he was using Windows(NT)2000. | He has defined some directories and files on the server from the NT. | While/after playing around (setting) with the security features on the | just defined files and directories the netapp server will hang. | Only reboot of the sever will revive it. | The customer claims he can recreate the problem at will. | Has anyone encountered such problems. | Do any of you have any words of wisdom? | The customer dos not like to accept the fact that win2000 is not yet | formally supported. he claims that win2000 talks CIFS, and even if MS is | doing wrong things at most the filer should complain but for sure not | hang... | --- | | Geesh..talk about a loose-loose situation. | | I would not expect NetApp to spend more than a _few_ man hours on this | problem, while they continue to hammer out solid released for solid software | platforms. | | While I agree it should not hang, theres no way to tell what NT2000 feature | is not working properly. |
I think that you missed the point Jeff, the W2K machine can halt and catch fire for all I care but the filer should at worst have degraded performance, regardless of the provocation. That's why we pay more for filers than for an Alpha PC.
/Michael
| I would not expect NetApp to spend more than a _few_ man hours on this | problem, while they continue to hammer out solid released for solid software | platforms. | | While I agree it should not hang, theres no way to tell what NT2000 feature | is not working properly. |
I think that you missed the point Jeff, the W2K machine can halt and catch fire for all I care but the filer should at worst have degraded performance, regardless of the provocation. That's why we pay more for filers than for an Alpha PC.
i'd have to agree. being a site with a large installed filer base, and several thousand users, people are going to plug random machines into the network, some will play nice, and some not so nice, but they shouldn't take the filer down with them. not only is it frustrating for me personally, but it also has the added effect of making it hard to convince higher ups that NetApps are a good place to spend money for distributed storage.
-steve
While/after playing around (setting) with the security features on the just defined files and directories the netapp server will hang. Only reboot of the sever will revive it.
...
I would not expect NetApp to spend more than a _few_ man hours on this problem, while they continue to hammer out solid released for solid software platforms.
While I agree it should not hang, theres no way to tell what NT2000 feature is not working properly.
...
I think that you missed the point Jeff, the W2K machine can halt and catch fire for all I care but the filer should at worst have degraded performance, regardless of the provocation. That's why we pay more for filers than for an Alpha PC.
There is an old saying in networking:
Be conservative in what you send.
Be liberal in what you receive.
It is absolutely unacceptable for a filer to hang simply because someone sends it garbage data.
It's true that W2K is till in Beta (alpha?), but we believe that we have done everything necessary to support W2K (if you are running a recent enough release), and we are very interested in hearing about problems that people have.
Dave
-
armijoļ¼ cs.unm.edu -
Dave Hitz -
Michael Salmon