toasters

toasters@lists.teaparty.net

13531 discussions

Re: quota size limits (was: "quotas to track disk usage")
by sirbruce＠ix.netcom.com 06 Oct '97

06 Oct '97

On 10/05/97 21:27:29 you wrote: > >sirbruce <sirbruce(a)ix.netcom.com> writes: > >> There was a bug submitted... that's all I know. It should be >> trivial to implement a clamping option like df_2gb_limit, unless >> there is something really annoying in the quotad protocol that >> prevents this. > >Since I'm only wanting to use quotas for usage tracking, not hard or >soft limits, the solution is to turn on only part of the quota system, >the clients don't need to know. Aha! Yes, this is exactly the conclusion I came to a while back, and hit myself for not thinking of it before... just mount noquota, even though the filer keeps tracking usage. Sorry, I thought I had mentioned that in my original email some weeks back. Bruce

1 0

Re: quota size limits (was: "quotas to track disk usage")
by sirbruce＠ix.netcom.com 06 Oct '97

06 Oct '97

On 10/05/97 17:36:18 you wrote: > >On 09/05/97 01:40:58 Daniel Quinlan wrote: > >>> Given these parameters: >>> >>> - I would like to use quotas to track user disk space usage (but not >>> limit it) > >Bruce <sirbruce(a)ix.netcom.com> replied: > >> Easily done, but there are some caveats. >> >> [...] >> >> 2. Some clients can't deal with quotas great thatn 8GB, and >> there is currently no option on the filer to limit this (this >> is filed as a bug), so you'd have to restrict your users to 8GB. >> If you have any over that, you don't want them in the quota system. >> >> So, you'd want something like: >> >> # Quota Target type disk files >> # ------------- ----- ---- ----- >> /newhome tree >> * user@newhome 8G >> >> The first line might not even be necessary, but it's worth >> including just for reference. Hmm, unless it breaks the >> clients the same way. Maybe the 8G can be omitted from >> the user entry as well? I don't know, I haven't tried it. >> The line might also be ncessary for the file to be parsed >> properly. >> >> What Netapp really needs to do is a default quota report by >> uid/gid type of command on the filer, to avoid the need to >> set up quotas to track usage. > >Since we have users using more than 8GB, this is a major problem. Agreed. >What operating systems have the 8 GB limit? I have no idea. I think both SunOS 4.x and 5.x had problems, but I'm not sure. I would expect that newer OSes would be less likely to have the problem (it's similar to the 2GB disk/partition size issue). >Has there been any work >to address these issues? There was a bug submitted... that's all I know. It should be trivial to implement a clamping option like df_2gb_limit, unless there is something really annoying in the quotad protocol that prevents this. >Will it work without the "8GB" in the user >entry? I don't know. Bruce

2 1

Consistent crashing on quota initialization
by Brian Tao 06 Oct '97

06 Oct '97

Could someone try reproducing this problem? I know it pretty much requires a Netapp that you don't mind the risk of crashing, but maybe there are some new Netapp owners out there. ;-) I have two F210's both running OnTap 4.0.4N_970627_1000 (this is what came installed on them). I create some quota trees, turn on the quotas, and then reboot the filer while the quotas are being initialized. After it comes back up, quotas are off. If I try to turn them on, the filer crashes. I've been able to do this several times to both F210's. An excerpt from the syslog is included below (I've forwarded the whole thing to Netapp support). Sun Oct 5 23:32:12 EDT [rc]: saving 55M to /etc/crash/core.1-small ("wafl_nfs_lookup: inconsistent directory entry {x0 0 525472 103351382} <quota.db> in {x0 0 555944 103344539}.") Sun Oct 5 23:32:57 EDT [rc]: saving 256M to /etc/crash/core.1 ("wafl_nfs_lookup: inconsistent directory entry {x0 0 525472 103351382} <quota.db> in {x0 0 555944 103344539}.") Sun Oct 5 23:35:20 EDT [rc]: relog syslog Sun Oct 5 23:29:29 EDT [tn_login_0]: Login from host: adminhost Sun Oct 5 23:35:20 EDT [rc]: NetApp Release 4.0.4N_970627_1000 boot complete. -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

1 0

Re: reducing the size of a NetApp -- temporarily
by sirbruce＠ix.netcom.com 06 Oct '97

06 Oct '97

On 10/05/97 18:00:36 you wrote: > >And since we can add new drives by swapping them in, it doesn't seem >like it would hurt to only bring 13 drives online at first. Since we >have an active filesystem, can someone tell me what the best route to do >this is? Any caveats? Don't forget to calculate the space you'll need for snapshots and so on too... also, the filesystem optimizes much better if you have lots of free space rather than always running the ragged edge. You don't have to add a whole shelf at once, so if 14 or 15 drives makes more sense for you, do that. Also, feel free to leave one in as a hot spare. >I have had one report from someone at NetApp that I should erase disk >labels (I don't know if he meant all of them, just the ones being >removed, or the ones staying) before starting, and another that it would >be fine to just yank the disks I don't want and newfs the remaining >ones. Yes, yank all the disks you don't want and boot off floppy, and then newfs the filesystem. That is the best way, and won't take very long at all on an F630. Stay away from other shortcut, quickie schemes that can have lots of hidden dangers. Bruce

1 0

quota size limits (was: "quotas to track disk usage")
by Daniel Quinlan 06 Oct '97

06 Oct '97

On 09/05/97 01:40:58 Daniel Quinlan wrote: >> Given these parameters: >> >> - I would like to use quotas to track user disk space usage (but not >> limit it) Bruce <sirbruce(a)ix.netcom.com> replied: > Easily done, but there are some caveats. > > [...] > > 2. Some clients can't deal with quotas great thatn 8GB, and > there is currently no option on the filer to limit this (this > is filed as a bug), so you'd have to restrict your users to 8GB. > If you have any over that, you don't want them in the quota system. > > So, you'd want something like: > > # Quota Target type disk files > # ------------- ----- ---- ----- > /newhome tree > * user@newhome 8G > > The first line might not even be necessary, but it's worth > including just for reference. Hmm, unless it breaks the > clients the same way. Maybe the 8G can be omitted from > the user entry as well? I don't know, I haven't tried it. > The line might also be ncessary for the file to be parsed > properly. > > What Netapp really needs to do is a default quota report by > uid/gid type of command on the filer, to avoid the need to > set up quotas to track usage. Since we have users using more than 8GB, this is a major problem. What operating systems have the 8 GB limit? Has there been any work to address these issues? Will it work without the "8GB" in the user entry? - Dan

1 0

Help
by Jim Grinnell 02 Oct '97

02 Oct '97

help

2 1

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

01 Oct '97

On Wednesday, October 01, 1997 9:48 AM, Marc Nicholas [SMTP:marc@hippocampus.net] wrote: > My first question would be: when Sybase? :-) > > (I'm just plain greedy...) > > > -marc > --- > Marc Nicholas - Hippocampus OSD Inc. > 416 979 9000 - fax: 416 979 8223 - http://www.hippocampus.net > 125 John St. - Suite #100 - Toronto - Ontario - M5V 2E2 - CANADA > "Inter/Intra/Extra[net] consulting, services, hardware and software sales" There is no technical reason that we currently know of that would prevent any other database from making similar use of a filer for storing its datastores. Care still needs to be taken with configuration as you would any time you are splitting the files of a particular application across platforms, but putting all the datastores for a particular database instance on the filer for any given RDBMS should work fine. As has already been mentioned, we here at Network Appliance talk to our Sybase database over NFS with stores on the filer and have done so for quite some time without problems. It is rumored that Sybase pulled back from allowing NFS access to its data but I have not been able to confirm this yet. We can say (empiracally at least) that it works. The real answer to your question is that we have had some introductory discussions with Sybase and will continue to work with them to gain their certification. You can be of assistance in this by mentioning to your Sybase representatives of your interest in getting your Sybase stores onto the filer. This is precisely how the intial interest was generated at Oracle when a very large Oracle customer indicated that Oracle really should support storage on a filer. I believe that similar interest expressed to Sybase will generate similar support. At the very least, if you have a test Sybase environment, I would give it a try. You will not be able to operate in "raw" Sybase mode, of course, but should still see similar if not increased performance over the network. Bruce Clarke

1 0

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

NetApp for mail spool?
by Gregory Gulik 18 Sep '97

18 Sep '97

I have a feeling this topic has been discussed to death, but here goes anyway: Has anyone had luck with using a NetApp for a mail spool? We did some tests, and although the locking worked fine most of the time, we did find that it dropped some messages for no reason whatsoever. In our case, the client machines are SPARCs running Solaris 2.5.1 Is there a problem with the locking on the NetApp, or are the Solaris libraries lying about the locks being in place and the writes taking place properly?

5 4

Re: NetApp for mail spool?
by Gregory Gulik 18 Sep '97

18 Sep '97

Do you have recommendations on where to find examples of code that incorporates this stonger locking you mention? -----Original Message----- From: David Schairer <njal(a)concentric.net> To: matthew zeier <mrz(a)3com.com> Cc: madhatta(a)mathworks.com <madhatta(a)mathworks.com>; greg(a)wwa.com <greg(a)wwa.com>; toasters(a)mathworks.com <toasters(a)mathworks.com> Date: Wednesday, September 17, 1997 5:57 PM Subject: Re: NetApp for mail spool?

1 0

"Interrupted system call" to F230 news spool
by Brian Tao 17 Sep '97

17 Sep '97

One of my inn 1.4unoff4 news reader servers started throttling itself just today with "Interrupted system call writing article file" (happened twice in the past 24 hours). The spool is on an F230 running 4.0.3, 256MB of read cache and 4MB of write cache. The news server is an Ultra 170, 512MB of RAM, ~250 to 300 readers around peak times. The two are on a FDDI ring. The F230 hovers around 65% CPU usage, so I don't think that's the problem, but the Ultra is reporting 900 to 1200 packets per second both in and out of its FDDI interface. Half of its time is spent in the kernel, according to top(1). The mounts are NFSv3 over UDP. Would dropping back down to NFSv2 help any? I'm trying to determine if this is a network congestion problem, or an OS limitation (on either the Netapp or the Sun). -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

3 3

Filer response time
by Dave Heiland 15 Sep '97

15 Sep '97

I'm looking for a way to monitor the performance of my F630 filer, in addition to checking cpu levels, network traffic or other information provided by sysstat. Specifically, since the LADDIS benchmarks plot nfs ops versus response time, I was wondering how I can check the response time of my filer from the client's perspective. Is it just a matter of running nfsstat -m on clients and checking the round-trip times, or is there another command or program that can be used? Dave -- David J. Heiland Lucent Technologies dheiland(a)lucent.com CIO Department Malmesbury, England

1 0

Pardon my ignorance
by Kevin L. Gross 11 Sep '97

11 Sep '97

Sorry to send to the entire list, but I can't find the original message from this list telling me how to get off of it, if there was one. Could some kind soul overlook my ignorance and tell me the address to send to in order to remove myself from this list? Thanks, -Kevin

2 1

Re: snapshot scheduling
by mds46523＠ggr.co.uk 11 Sep '97

11 Sep '97

This sounds like another task that would be easier if we could load servlets onto the filers. On Sep 11, 6:05, Daniel Quinlan wrote: > Subject: snapshot scheduling > One of our filers has high data turn-around so I have limited the > snapshot lifetime to 2 days (the default) to keep usage at about 10%. > We use 4 days on our other filer because it experiences a lower rate of > data turn-around. > > > snap list > working........................ > %/used %/total date name > ---------- ---------- ------------ -------- > 1% ( 1%) 0% ( 0%) Sep 10 20:01 hourly.0 > 3% ( 3%) 2% ( 2%) Sep 10 16:01 hourly.1 > 5% ( 3%) 4% ( 2%) Sep 10 12:01 hourly.2 > 6% ( 3%) 5% ( 2%) Sep 10 08:01 hourly.3 > 8% ( 4%) 6% ( 3%) Sep 10 00:01 nightly.0 > 8% ( 4%) 6% ( 3%) Sep 09 20:01 hourly.4 > 10% ( 4%) 7% ( 3%) Sep 09 16:02 hourly.5 > 12% ( 5%) 10% ( 3%) Sep 09 00:01 nightly.1 > > Unfortunately, 2 days means that if someone deletes a file on Friday, it > will be gone by the next work day, Monday. There is also a lower rate > of data turn-around on the weekend. 3 days would be ideal, except on > weekdays where it can sometimes push the snapshot usage higher than I > want. > > Is there some way (other than a remote cron job twice a week) to acheive > what I want -- variable snapshot lifetimes according to the day of the > week? > > If not, it would be a nice feature. Either that, or options to force > deletion of n number of nightly snapshots (over m days old) when > snapshot usage goes over some percentage. > > Dan > > -- > Daniel Quinlan (at work) Linux, our last best hope for Unix > quinlan(a)transmeta.com http://www.pathname.com/~quinlan/ > ... > (Got BOFH? Looking for good ones.) >-- End of excerpt from Daniel Quinlan -- -Mark, TSG Unix admin and support, int 782 4412, ext +44 1438 76 4412. PTP: What sheeplike qualities should you be developing?

1 0

snapshot scheduling
by Daniel Quinlan 11 Sep '97

11 Sep '97

One of our filers has high data turn-around so I have limited the snapshot lifetime to 2 days (the default) to keep usage at about 10%. We use 4 days on our other filer because it experiences a lower rate of data turn-around. > snap list working........................ %/used %/total date name ---------- ---------- ------------ -------- 1% ( 1%) 0% ( 0%) Sep 10 20:01 hourly.0 3% ( 3%) 2% ( 2%) Sep 10 16:01 hourly.1 5% ( 3%) 4% ( 2%) Sep 10 12:01 hourly.2 6% ( 3%) 5% ( 2%) Sep 10 08:01 hourly.3 8% ( 4%) 6% ( 3%) Sep 10 00:01 nightly.0 8% ( 4%) 6% ( 3%) Sep 09 20:01 hourly.4 10% ( 4%) 7% ( 3%) Sep 09 16:02 hourly.5 12% ( 5%) 10% ( 3%) Sep 09 00:01 nightly.1 Unfortunately, 2 days means that if someone deletes a file on Friday, it will be gone by the next work day, Monday. There is also a lower rate of data turn-around on the weekend. 3 days would be ideal, except on weekdays where it can sometimes push the snapshot usage higher than I want. Is there some way (other than a remote cron job twice a week) to acheive what I want -- variable snapshot lifetimes according to the day of the week? If not, it would be a nice feature. Either that, or options to force deletion of n number of nightly snapshots (over m days old) when snapshot usage goes over some percentage. Dan -- Daniel Quinlan (at work) Linux, our last best hope for Unix quinlan(a)transmeta.com http://www.pathname.com/~quinlan/ ... (Got BOFH? Looking for good ones.)

1 0

Re: SCSI shelf faults?
by sirbruce＠ix.netcom.com 10 Sep '97

10 Sep '97

On 09/10/97 16:47:03 you wrote: >Sorry, I guess I should have said that I have 1 chain. Physically there >are two shelves. NetApp engineer installed the shelves. I suppose he >could have gotten it wrong. This is especially likely with new products with a limitation that is new but not widely advertised. But it's easy to check... just run in there and see if they are connected to the card or to the secondary connector on the back of the chasis. (sysconfig -v may or may not report the right stuff if it's miscabled. Bruce

1 0

Jump to page:

2026

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