toasters

toasters@lists.teaparty.net

13531 discussions

No CPU stats with filer-mrtg
by Scott MacDonald 16 Jul '98

16 Jul '98

After reading the reports in this list, I've managed to get filer-mrtg installed and working fine except for the CPU stats, which are all permanently zero. The network, NFS and disk stats are great, but I'd like the CPU as well. Has anyone else had the same problem, or could advise me where to look to fix this. I know nothing about SNMP, so trying to find out what's wrong is a bit difficult. TIA, Scott. _______________________________________________________________ Scott MacDonald Mobile Systems International Plc Tel: 0171 971 8798 System Administrator Fax: 0171 971 8712 E-Mail: scott(a)msi-uk.com _______________________________________________________________

1 0

filer-mrtg
by David B. Ritch 13 Jul '98

13 Jul '98

I've been playing with filer-mrtg, the mrtg-based monitoring package available from NOW. It's a really nice package. It contains some Solaris binaries. The source for some of this is available in the MRTG package. Unfortunately, the source for snmpget is not. Does anyone know where I could get the source for snmpget? Thanks, David Ritch

2 1

subscribe
by Farouk Al-Shorafa 09 Jul '98

09 Jul '98

1 0

posting history - who's wordy and who's quiet?
by Tom Yates 08 Jul '98

08 Jul '98

i was looking for a reason to have fun with perl modules for chopping up email addresses, so here's the prolixity summary for the lifetime of the list. i've cut-off at ten posts. 99 Brian Tao 86 sirbruce(a)ix.netcom.com 55 Alexei Rodriguez 49 Daniel Quinlan 47 Tom Yates 45 Dave Hitz 37 Guy Harris 30 Jaye Mathisen 30 David Drum 25 Kenneth Whittaker 23 sthaug(a)nethelp.no 22 Chris Caputo 21 Marc Nicholas 19 alexei(a)cimedia.com 19 Karl Swartz 18 Jonah Yokubaitis 16 Weeks, Thomas 16 Matthew Zeier 16 Bruce Sterling Woodcock 16 Amy Chused 15 Jim Davis 15 Christoph Doerbeck 14 Mark D Simmons 14 Dave Cole 13 rasmus(a)bellglobal.com 13 Simmons Mr M D 12 Rasmus Lerdorf 12 Ragnar Lonn 12 Brian Pawlowski 11 Steve Gremban 11 Keith Brown 11 Jason D Kelleher 10 Philip Thomas 10 Ketil Kirkerud 10 Dave Pascoe Tom Yates - Unix Chap - The Mathworks, Inc. - +1 (508) 647 7561 MAG#65061 DoD#0135 AMA#461546 1024/CFDFDE39 0C E7 46 60 BB 96 87 05 04 BD FB F8 BB 20 C1 8C

5 4

'quota resize' - any way around it ?
by James FitzGibbon 08 Jul '98

08 Jul '98

Is there *any* way (and I'm open to any suggestions) to get around the inability of 'quota resize' to handle additions/deletions from the /etc/quotas file ? The problem I'm stuck with is trying to provide realtime addition of users (with quotas) on a 100GB filer without having to turn quotas off and on, which is currently a 26 minute process. During these 26 minues, no quotas are enforced. Acceptable once a night, but not as often as they want me to run it. A few of ideas (in order of ascending lunacy): - just accept the fact that NetApp doesn't consider this wish to very important and turn the quotas on/off as often as is feasible. - set a default quota for the export, and just create a new quotas file once per night. - preload the /etc/quotas file with entries for all possible UIDs, then just change the quota as they request it. This way the /etc/quotas will always be the same length and contain the same number of users. - get NetApp to allow an SNMP SET request to implement this functionality - try to figure out the format of /etc/db/quota.db and manipulate it directly. - kidnap Dave Hitz (presuming he's still there) and have him add the feature at gunpoint. - Quit. TIA. -- j. James FitzGibbon james(a)ican.net System Engineer, ACC Global Net Voice/Fax (416)207-7171/7610

4 4

Re: Trouble with Unix groups running NIS
by sirbruce＠ix.netcom.com 06 Jul '98

06 Jul '98

On 07/06/98 13:07:49 you wrote: > >The group file should be OK; at least its never complained before. Well, how big is the "uk" group, or the group just before it? Maybe more than 512 characters? 1024 characters? Some sort of boundary along those lines. >How >would you increase the buffer anyway ? Presumably, its an option in the >rc file... You can't. This is why I said you'd have to get Netapp to release a patch or new release with a larger buffer. Assuming, of course, that the Netapp's buffer is really too small; as I said, it could be that the buffer is in line with what your NIS master can handle but you've gone beyond that limit. Bruce

1 0

DataONTAP 5.0.1 IP cache bug
by dfinkels＠siac.com 06 Jul '98

06 Jul '98

-- Daniel Alex Finkelstein Infrastructure Enhancement Group Systems and Technologies Support phone 212.383.2951 pager 917.427.1630 Securities Industry Automation Corporation SIAC has found a bug with the 5.0.1 OS of DataONTAP. There appears to be no time-to-live on the cached IP addresses of hosts. Changes in the IP addresses of hosts in DNS or NIS are not recognized until the NetApp is either rebooted or "exportfs -a" is executed. To force re-reading of DNS and NIS data, we have set up cronjobs to reboot our 6 NetApp 520's weekly.

3 3

Re: Trouble with Unix groups running NIS
by sirbruce＠ix.netcom.com 06 Jul '98

06 Jul '98

On 07/06/98 11:54:37 you wrote: > >Hello, > >I'm trying to set up group quotas on my filer, but I keep getting the >following message back : > >tap> quota on >Mon Jul 6 11:38:07 BST [rc]: getgrp: Input buffer not large enough >quota: group name 'uk' not found (/etc/quotas line 7). >quota: quotas not turned on. >tap> > > >What is this getgrp thing and how can I enlarge the input buffer ? Well, my GUESS is that the error, essentially, is saying that your entry for the group "uk" is too long. Normally I'd say check the group file on the filer but you mention NIS in the subject line, so I'd say check the group file on the NIS master. The filer *should* be able to accept group lines as big as your UNIX server. Either your group line is actually too big on your UNIX server (in which case it probably was broken and you just didn't know it), or the filer's buffer needs to be increased. In the latter case, you'll have to wait for a patch or new release that has a bigger buffer. Bruce

2 1

Trouble with Unix groups running NIS
by Raymond Brennan 06 Jul '98

06 Jul '98

Hello, I'm trying to set up group quotas on my filer, but I keep getting the following message back : tap> quota on Mon Jul 6 11:38:07 BST [rc]: getgrp: Input buffer not large enough quota: group name 'uk' not found (/etc/quotas line 7). quota: quotas not turned on. tap> What is this getgrp thing and how can I enlarge the input buffer ? "I read a dictionary once; I thought it was a poem about everything" -Anon

1 0

SNMP support on filers
by agy 03 Jul '98

03 Jul '98

Hello All, NetApp is planning to enhance the SNMP support in the filer in an upcoming release of the OS. Due to some risk factors, I'd rather not promise that it will be the next major release (next year), but that is the current plan. Things we definitely plan to do when this support is added: (a) GETs for general CIFS-related filer parameters. (b) GETs for statistics on all SMB requests, both cumulative and per client. (c) Generic TRAP support, with settings and parameters for each available trap manageable through Filerview. I would welcome feedback on: (a) Additional GETs you think are necessary. (b) Trap support considerations. (b) Specific traps you think should be implemented. (d) Other things pertaining to SNMP that would be helpful. It would help us if you could indicate the relative importance-- to your company's future infrastructure plans--of things that you suggest. Thanks, Alan --------------------------------------------------------------- Alan G. Yoder agy(a)netapp.com Network Appliance, Inc. 2770 San Tomas Expressway voice 408-367-3031 Santa Clara, CA 95051 fax 408-367-3451 ---------------------------------------------------------------

3 2

bug fix for na_snapmon
by Daniel Quinlan 02 Jul '98

02 Jul '98

Hi everyone. I just fixed a minor bug in na_snapmon (it would try to delete dump snapshots all of the time instead of just the ones that were more than two days old). The copy that I put up on my NetApp web page doesn't have that problem: http://www.pathname.com/~quinlan/netapp/ That could actually cause some problems for older releases (before 4.3x) affected by bug #650 that would crash the filer if you tried deleting a snapshot that's in use. Now, na_snapmon makes the assumption that dumps older than two days are safe to delete, or at least you're running 4.3 or later. Dan

1 0

Re: SNMP support on filers
by Daniel Quinlan 02 Jul '98

02 Jul '98

Hi Alan. There are a few things: - Information located in the "Tree" field of the "quota report" is missing from the SNMP quota information. (this is bug 8704, and log 35271) - Putting CIFS and HTTP statistics into SNMP, starting with the same information that's in "sysstat", but also the other information you can get from the "cifs" command. - getting snapshot information via SNMP - per-client NFSop/CIFSop/HTTPop statistics Thanks. Dan

1 0

Re: SNMP support on filers
by sirbruce＠ix.netcom.com 02 Jul '98

02 Jul '98

On 07/02/98 11:01:03 you wrote: > >Hello All, > NetApp is planning to enhance the SNMP support in the filer >in an upcoming release of the OS. Due to some risk factors, >I'd rather not promise that it will be the next major release >(next year), but that is the current plan. > > Things we definitely plan to do when this support is added: >(a) GETs for general CIFS-related filer parameters. >(b) GETs for statistics on all SMB requests, both cumulative > and per client. >(c) Generic TRAP support, with settings and parameters for > each available trap manageable through Filerview. > > I would welcome feedback on: >(a) Additional GETs you think are necessary. >(b) Trap support considerations. >(b) Specific traps you think should be implemented. >(d) Other things pertaining to SNMP that would be helpful. My main advice would be to make sure anything obtainable through SNMP is also obtainable from the command line and from the remote GUI; i.e. if you're going to have per-client stats for CIFS in SNMP then it should be available via a "cifs stats" command or similar as well. Bruce

1 0

na_snapmon: snapshot monitor
by Daniel Quinlan 01 Jul '98

01 Jul '98

I finally got fed up with deleting snapshots by hand when they started using too much disk space, so I created a simple snapshot monitor that automatically deletes snapshots when they start using more than 100% of the space reserved for snapshot usage. Now, I configure each filer to schedule more snapshots than I really want and I use only "snap reserve" to limit how much disk usage is taken by the snapshots. If a filer's data turnover rises, it automatically scales the number of snapshots back. For example: Jun 26 10:30:36 sodium na_snapmon: rsh uranium snap delete hourly.3 Jun 26 10:33:03 sodium na_snapmon: rsh neptunium snap delete nightly.1 Jun 26 10:34:49 sodium na_snapmon: rsh thorium snap delete hourly.2 Jun 26 10:40:04 sodium na_snapmon: rsh neptunium snap delete hourly.3 It will also try to delete dump snapshots that are older than two days old, and it will also ignore snapshots that have been specially created or renamed. The best way to run this is as root cron job, every ten minutes or so. This runs on Linux now, but should also work on Solaris. Other Unix systems with very minimal modification. ------- start of cut text -------------- #!/usr/bin/perl # na_snapmon - monitor snapshot usage and keep it under control # Copyright (C) 1998 Daniel Quinlan # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. use Getopt::Std; require "find.pl"; sub usage; sub trim_snapshots; sub snap_delete; my $limit; my $prog; $prog = $0; $prog =~ s@.*/@@; getopts("hd"); if ($opt_h) { &usage; exit 0; } foreach $dir (@ARGV) { my $df_worked = 0; if (! -d $dir) { warn("$prog: $dir: no such snapshot mount point"); } open (DF, "df -k $dir |"); while (<DF>) { if (/[0-9]%/) { $df_worked = 1; ($fs, $blocks, $used, $avail, $capacity, $mount) = split; if ($capacity !~ /^[0-9]?[0-9]%/) { $fs =~ s/:.*//; trim_snapshots($fs, $dir); } } } close (DF); } sub trim_snapshots { my ($filer, $dir) = @_; my (@list, @snapshots, %atime); # read snapshot list opendir(DIR, $dir) || die "can't opendir $dir: $!"; @snapshots = grep { ! /^\.\.?$/ && -d "$dir/$_" } readdir(DIR); closedir DIR; # sort by atime foreach $entry (@snapshots) { $atime{$entry} = -A "$dir/$entry"; } @snapshots = sort {$atime{$a} <=> $atime{$b}} @snapshots; # maybe delete something while ($s = (pop @snapshots)) { # try to delete old dump snapshots, but since this might # fail, keep trying to delete after this one. if ($s =~ /^snapshot_for_dump\.[0-9]+$/ && time - $atime{$s} >172800) { snap_delete($filer, $s); next; } # skip manual snapshots next if ($s !~ /^(hourly|nightly|weekly)\.[0-9]+$/); # leave one snapshot at all times next if ($s =~ /^hourly\.0$/); snap_delete($filer, $s); last; } } sub snap_delete { my ($filer, $snapshot) = @_; if ($opt_d || ($> != 0)) { print "debug: rsh $filer snap delete $snapshot\n"; } else { system("logger -t na_snapmon \"rsh $filer snap delete $snapshot\""); system("rsh $filer snap delete $snapshot"); } } sub usage { print <<EOF; usage: $prog [-hd] [list of snapshot mount points] -h print this help -d debugging mode: don't do, just show EOF } ------- end ----------------------------

1 0

Quotas
by Raymond Brennan 01 Jul '98

01 Jul '98

I'm sort of new to all this, so here goes : I want to create a root directory called, say, dog. I then want to create a subdirectory called pup. I want to limit the size to which pup can grow to, say, 50 Mb. The thing is, the quota qtree command won't accept slashes in the qtree name. Also, if I create "dog" by doing # mkdir dog then do #cd dog # mkdir pup then go to the quotas file on /etc and do /dog/pup 10G 10K and run quota on I get "/dog/pup is not a quota tree. In short, how do I set quotas on file systems a number of steps down the tree ? Why can't I do /dog/pup 5G /dog/puppy 5G

1 0

OT 5.?
by Weeks, Thomas 01 Jul '98

01 Jul '98

Just curious... how is the OT 5.x software working for eveyone? Any problems? Stability probs? Backout (to 4.3.4) problems? What about quotas and the like? Just curious... Tom > -----Original Message----- > From: Mark D Simmons [SMTP:mds@gbnet.net] > Sent: Monday, June 29, 1998 1:48 AM > To: quinlan(a)transmeta.com; toasters(a)mathworks.com > Subject: Re: what data is being used? > > I recall asking for this in an RFE sense a year ago as it would be > incredibly > useful. Sun just put the capability to track the load on disks at the > partition > level in Solaris 2.6 - this sort of stat on a filer would be just as > useful IMHO > > Per quota tree seemed most natural to me as that is already a > distinctive > structure in filer housekeeping meta-data. Directory level gathering > might be > too much load to put on a filer which is meant to perform under high > demand... > > ...how about an admin command that flips a bit on a directory and > makes it a > watchpoint in the filesystem - accesses against anything beneath it > count on > that directory's stats. Even if the total number of such points were > limited > to put a boundary on overhead in the filer, it would still be a useful > analytical tool.

1 0

Re: what data is being used?
by Mark D Simmons 29 Jun '98

29 Jun '98

I recall asking for this in an RFE sense a year ago as it would be incredibly useful. Sun just put the capability to track the load on disks at the partition level in Solaris 2.6 - this sort of stat on a filer would be just as useful IMHO Per quota tree seemed most natural to me as that is already a distinctive structure in filer housekeeping meta-data. Directory level gathering might be too much load to put on a filer which is meant to perform under high demand... ...how about an admin command that flips a bit on a directory and makes it a watchpoint in the filesystem - accesses against anything beneath it count on that directory's stats. Even if the total number of such points were limited to put a boundary on overhead in the filer, it would still be a useful analytical tool.

1 0

Zowie! He's using 4 TB!
by Brian Rice 26 Jun '98

26 Jun '98

Has anyone else seen this little sparkle in the output of quota report? user sairam 4294947972 5120000 4294967282 512000 This shows up intermittently after I move a user to the filer with a restore rfD - . As you might imagine, it prevents the user from writing. Workaround is quota off; quota on. This is on an F630 running 4.3.3. I haven't filed a bug report yet, though I will as soon as I have confidence that I can state the sequence of events that triggers this phenomenon. Just curious to see if anyone else had seen it. Brian Rice brice(a)gnac.com

2 1

what data is being used?
by Daniel Quinlan 26 Jun '98

26 Jun '98

Are there any tools to gauge NFS load (reads, writes, NFS ops, whatever), perhaps on a quota tree or directory level. Why would I want to know such a thing? Say I have an 200GB F540 filer with two large trees. And I just purchased a 200GB F630 filer. I want to move one of the trees, but not both. I want to move the busier one, not the other one. There are some basic things I've been looking at in the above situation, but maybe someone here knows about a better method/technique/tool. I hoping someone will mention such an obvious solution that I'll be glad I didn't mention what sort of thing I've been doing. :-) - Dan

1 0

Re: Making CIFS hidden files from unix
by Daniel Quinlan 26 Jun '98

26 Jun '98

Steve Losen <scl(a)sasha.acc.virginia.edu> writes: > When we add new user accounts to our NetApp, we don't know if the owner > will use CIFS, unix, or both. (We use unix file protection semantics.) So > we are going to put unix dot files in the new home directory. But it > would be nice to prevent or discourage CIFS users from deleting them -- in > particular the .forward file. We were thinking that if we could make the > dot files "hidden" and "system", that that would help, even though CIFS > users can override and see hidden files if they want. > > [...] > > Is this overly complex? Is there a simpler way? Yes. I think so. A simpler solution is to configure sendmail to look for .forward files somewhere other than home directories. We put all .forward files (as well as procmail stuff) in a centralized location (physically on the mail server). For example, /local/mail/<username>/.forward /local/mail can be (auto)mounted to allow editing on clients. You can put symbolic links in user home directories, and it won't matter if people delete the links. This also allows for faster and more reliable mail delivery since the .forward files are now located on the mail server. You don't need to worry about someone's home directory being unavailable. - Dan

1 0

Making CIFS hidden files from unix
by Steve Losen 26 Jun '98

26 Jun '98

When we add new user accounts to our NetApp, we don't know if the owner will use CIFS, unix, or both. (We use unix file protection semantics.) So we are going to put unix dot files in the new home directory. But it would be nice to prevent or discourage CIFS users from deleting them -- in particular the .forward file. We were thinking that if we could make the dot files "hidden" and "system", that that would help, even though CIFS users can override and see hidden files if they want. Our account adding software is on unix, and I think I have a way to do what I want. I'll make a "new user" prototype directory and set the unix permissions on the dot files, then get on a PC and set "hidden" and "system" on them. I'll use the netapp dump utility to dump the prototype dir to a file. When I create a user, I'll use the netapp restore to bring back the prototype directory, chown the files to the new user, overwrite the .forward, and mv the prototype into place as the user's home dir. This preserves any CIFS hidden attributes, I presume. It looks like restore always restores back to the original location of the dumped directory. Is it possible to get restore to restore elsewhere? We're running NetApp Release 4.3.1. Is this overly complex? Is there a simpler way? Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

2 1

Re: always safe to delete dump snapshots?
by Paul Albers 25 Jun '98

25 Jun '98

Dan and Bruce, This was bug #650 and has been fixed in all the OnTap OS releases since 4.3x. The request to delete this snapshot_for_dump.<num> will fail. -paul At 08:42 AM 6/25/98 -0500, you wrote: >On 06/25/98 01:38:27 you wrote: >> >>Is it always safe to attempt to delete a snapshot_for_dump.<num>? >> >>Another way to phrase my question -- it will *never* succeed when a >>dump is in progress, right? >> >>Yes, I know it's supposed to not succeed, but since I'm writing a >>program to automatically delete snapshots, I'm exercising more >>paranoia than usual. > >Well, there USED to be an old bug that's been around since the >beginning that trying to delete one while a dump was in progress >would crash the filer. This bug was even mentioned in bold >letters in the admin guide (either in the snapshot or the dump >sections). Assuming they've fixed it to do what you say, then >you're correct. > >If they haven't, then you don't want to automatically delete those >files, unless you have some way of knowing ahead of time that they >are no longer associated with a dump process (say, one that failed >in some ungraceful way). Since this usually happened because of a >crash, one thing I used to do was include an automatic snap delete >at the end of the rc file to delete the snapshot_for_dump after the >filer had started up. The appearance of the snapshot_for_dump.n >mechanism broke that... I made the suggestion that having the OS >automatically delete those might be a good idea, but on the other >hand it might not... the user may really want to restart the >backup off that old image, rather than taking a new one right at >that moment. > >Bruce > > >

1 0

Re: always safe to delete dump snapshots?
by varun＠netapp.com 25 Jun '98

25 Jun '98

> From sirbruce(a)ix.netcom.com Thu Jun 25 06:45:51 1998 ... > Well, there USED to be an old bug that's been around since the > beginning that trying to delete one while a dump was in progress > would crash the filer. This bug was even mentioned in bold > letters in the admin guide (either in the snapshot or the dump > sections). Assuming they've fixed it to do what you say, then > you're correct. > This is bug 650. Fixed since release 4.2. You should get a "Snapshot in use by dump." message if you attempt to delete a snapshot that's being dumped.

1 0

Re: always safe to delete dump snapshots?
by sirbruce＠ix.netcom.com 25 Jun '98

25 Jun '98

On 06/25/98 01:38:27 you wrote: > >Is it always safe to attempt to delete a snapshot_for_dump.<num>? > >Another way to phrase my question -- it will *never* succeed when a >dump is in progress, right? > >Yes, I know it's supposed to not succeed, but since I'm writing a >program to automatically delete snapshots, I'm exercising more >paranoia than usual. Well, there USED to be an old bug that's been around since the beginning that trying to delete one while a dump was in progress would crash the filer. This bug was even mentioned in bold letters in the admin guide (either in the snapshot or the dump sections). Assuming they've fixed it to do what you say, then you're correct. If they haven't, then you don't want to automatically delete those files, unless you have some way of knowing ahead of time that they are no longer associated with a dump process (say, one that failed in some ungraceful way). Since this usually happened because of a crash, one thing I used to do was include an automatic snap delete at the end of the rc file to delete the snapshot_for_dump after the filer had started up. The appearance of the snapshot_for_dump.n mechanism broke that... I made the suggestion that having the OS automatically delete those might be a good idea, but on the other hand it might not... the user may really want to restart the backup off that old image, rather than taking a new one right at that moment. Bruce

1 0

always safe to delete dump snapshots?
by Daniel Quinlan 25 Jun '98

25 Jun '98

Is it always safe to attempt to delete a snapshot_for_dump.<num>? Another way to phrase my question -- it will *never* succeed when a dump is in progress, right? Yes, I know it's supposed to not succeed, but since I'm writing a program to automatically delete snapshots, I'm exercising more paranoia than usual. Thanks. - Dan

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