toasters

toasters@lists.teaparty.net

13514 discussions

RE: Oracle on Netapps
by sirbruce＠ix.netcom.com 01 Oct '97

01 Oct '97

On 10/01/97 00:12:58 you wrote: >> Any questions feel free to contact me. > >My first question would be: when Sybase? :-) Always? Even Netapp has run Sybase on the filers for some time. Or is there some more specific Sybase feature that doesn't work over NFS? Bruce

2 1

RE: Oracle on Netapps
by sirbruce＠ix.netcom.com 01 Oct '97

01 Oct '97

On 10/01/97 01:11:19 you wrote: >Yup...you can't use a Sybase native filesystem...which is something Sybase >themselves recommend. > >We've been talking with our local NetApp reps about doing some evaluations >of Sybase on a native filesystem versus Sybase running against an NFS >filesystem just to see what the performance difference is like. Ah... well, I don't think the Oracle deal is going to allow Oracle "native filesystem" (i.e. raw) either. It's just so that Oracle will now let their stuff run over NFS if it's the filer. Or is there more to it than that? Bruce

1 0

RE: Oracle on Netapps
by Bruce Clarke 01 Oct '97

01 Oct '97

I am the technical contact in NetApp Marketing responsible for the Oracle relationship. The software that officially supports Oracle will be the 4.3 release of OnTap. This software goes to external Beta test this week and should be generally available by the middle of October. The changes to support Oracle were small but very relevant and will be documented in an upcoming whitepaper describing the correct configurations for NFS, Oracle, and OnTap to ensure maximum performance and reliability when storing Oracle database files. This paper will be available in October. Many customers have chosen to already run Oracle without these specific changes and have been having no problems. So I do encourage anyone interested in storing their datastores on a filer to start their testing immediately and to upgrade to OnTap 4.3 before going into production. Any questions feel free to contact me. Bruce Clarke Technical Manager - Business Development Network Appliance, Inc. Email: bclarke(a)netapp.com Phone: 408-367-3156 On Tuesday, September 30, 1997 11:14 AM, Brian Tao [SMTP:taob@nbc.netcom.ca] wrote: > Anyone have some technical information regarding the recent > announcement between Netapp and Oracle? Is there a new OnTap (5.0?) > that needs to be uploaded on the filers, or is it something that can > be done with the 4.x OS? What's special about this Oraclized version > of OnTap? > > http://www.netapp.com/news/level3b/news_rel_970922.html > > -- > Brian Tao (BT300, taob(a)netcom.ca) > "Though this be madness, yet there is method in't"

2 1

Oracle on Netapps
by Brian Tao 28 Sep '97

28 Sep '97

Anyone have some technical information regarding the recent announcement between Netapp and Oracle? Is there a new OnTap (5.0?) that needs to be uploaded on the filers, or is it something that can be done with the 4.x OS? What's special about this Oraclized version of OnTap? http://www.netapp.com/news/level3b/news_rel_970922.html -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

1 0

Null ethernet cable and/or private network
by David Drum 26 Sep '97

26 Sep '97

Hello everyone, Sitting here watching perfmeter report network collisions on the machine my NetApp is connected to is making me once again interested in exploring the possibility of setting up a null ethernet, full duplex 100 Mbps ethernet, or private switched ethernet segment connection. If anyone has done this I would appreciate someone setting me off in the right direction. Hardware and software (i.e. informing in.routed to use a particular interface) advice sought. net.karma offered. Regards, David K. Drum david(a)more.net -- It's hard to be bored when you're as stupid as a line. [1] Reality has a tendency to be so uncomfortably real. [2] You can only measure the size of your head from the inside. [3] When you proceed deliberately, mistakes don't cascade, they instruct. [4] [1] Vernor Vinge [2] Neil Peart [3] Larry Wall [4] Stewart Brand

2 4

Single vs. dual shelf performance on F230
by Brian Tao 25 Sep '97

25 Sep '97

If I had an F230 with, say, 6 drives, would I see any significant performance gain by placing 3 drives per shelf, rather than having all 6 drives on one shelf (and thus one controller)? This will be for heavily randomized file accesses (e.g., mail or news spool). -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

3 4

Re: Single vs. dual shelf performance on F230
by sirbruce＠ix.netcom.com 25 Sep '97

25 Sep '97

On 09/24/97 19:00:24 you wrote: > > If I had an F230 with, say, 6 drives, would I see any significant >performance gain by placing 3 drives per shelf, rather than having all >6 drives on one shelf (and thus one controller)? This will be for >heavily randomized file accesses (e.g., mail or news spool). You might see a minor performance improvement. I think the last time this sort of thing was measured it was reported to be negligible, and didn't really appear until you had 4 or 5 drives on one controller. But this was with different controllers, different drives, etc. so it may no longer apply. It probably can't hurt, and would certainly be worth trying. (Especially with random access... I suppose with a nice layout with good striping, it might be preferable to read it all from one controller at once... not sure how these things are handled at the low level.) Bruce

1 0

CIFS and NIS experiences?
by Daniel Quinlan 24 Sep '97

24 Sep '97

We're going to be using CIFS on our filers and I would like to hear about anyone's experiences with CIFS especially using it under NIS. I tried briefly enabling CIFS about a month ago on one of our filers, using NIS, and it worked, but the filer started having problems only a few minutes later, so I disabled CIFS and NIS. The problems were pretty severe ... of the "did someone shut nfs off?" variety, but I didn't have much of a chance to investigate. We are running 4.1d. We're using Solaris boxes as NIS servers. For my next try at CIFS, I'm thinking about not using NIS and just using a text copy of the passwd and group files. Has anyone else tried and/or had problems with CIFS under NIS? -- Daniel Quinlan (at work) Linux, our last best hope for Unix quinlan(a)transmeta.com http://www.pathname.com/~quinlan/

2 1

request
by David Drum 23 Sep '97

23 Sep '97

Hello, Since I know NetApp people are listening... I'd like to be able to use backslash line-continuation in the /etc files, e.g. /patches/Solaris_2.5.1_x86_Patches -ro,access=allinger.apg.more.net:\ b5fan.apg.more.net This ought not be too difficult to support in a future release. Regards, David K. Drum david(a)more.net -- It's hard to be bored when you're as stupid as a line. [1] Reality has a tendency to be so uncomfortably real. [2] You can only measure the size of your head from the inside. [3] When you proceed deliberately, mistakes don't cascade, they instruct. [4] [1] Vernor Vinge [2] Neil Peart [3] Larry Wall [4] Stewart Brand

1 0

seeing constant not responding messages
by Chris Caputo 21 Sep '97

21 Sep '97

I just the sent the following to support@netapp, but was also curious if anyone here had any insight. Is everyone on 4.1d happy? Chris ---------- Forwarded message ---------- Date: Thu, 18 Sep 1997 11:47:53 -0700 (PDT) From: Chris Caputo <ccaputo(a)alt.net> To: support(a)netapp.com Hi. We constantly (several times a minute) get the following and I have a feeling (because the drive lights go dark) it is affecting the performance of our NetApp box. At some point discussion on the toasters mailing list made me think that this was something that was going to be fixed after 4.0.1c, which is what we are running. Can you let us know if this is fixed in 4.1d? Should we upgrade regardless? Thanks, Chris Caputo President, Altopia Corporation PS: Here are the messages - they happen all of the time... Sep 18 11:43:51 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:43:52 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:43:55 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:43:56 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:43:57 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:43:57 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:43:59 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:43:59 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:03 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:04 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:07 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:07 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:08 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:08 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:09 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:09 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:11 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:12 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:14 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:14 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:21 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:21 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:25 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:25 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:26 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:26 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:30 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:30 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:32 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:33 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:36 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:36 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:36 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:37 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:39 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:39 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:40 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:40 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:42 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:42 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:43 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:44 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:44 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:45 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:49 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:49 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:51 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:51 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:44:56 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:44:56 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:01 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:01 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:01 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:02 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:03 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:03 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:04 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:05 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:06 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:06 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:11 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:11 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:15 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:16 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:19 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:19 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:24 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:24 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:30 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:30 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:30 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:30 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:35 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:35 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:41 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:42 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:47 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:48 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:48 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:49 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:49 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:45:50 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:50 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:45:50 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:04 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:05 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:13 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:13 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:15 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:15 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:33 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:33 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:39 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:40 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:42 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:42 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:43 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:43 tofu kernel: nfs server netapp1.alt.net:/home: is alive again Sep 18 11:46:44 tofu kernel: nfs server netapp1.alt.net:/home: not responding Sep 18 11:46:44 tofu kernel: nfs server netapp1.alt.net:/home: is alive again

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters