toasters April 1998

toasters@lists.teaparty.net

66 participants
93 discussions

Y2K Testing & compliance
by Thomson, Michael 25 Sep '98

25 Sep '98

Hi there! I've been asked some questions by our Y2K project team, specifically related to NetApp, and I'm unsure how to respond. >From the web page (http://www.netapp.com/y2k_table.html) it seems that the only thing that is 'preliminarily evaluated' is DOT 4.1. Can anyone give the authorative answer to: 1) Are there any plans to use a hardware clock that stores 4-digit years? 2) What Y2K tests were performed on DOT 4.1 3) Have later releases (4.1.3, 5.0, etc.) had the same tests run on them before release? 4) Can customers get access to NetApp test plans and results, directly or via a non-disclosure agreement? More generally, are people inclined to believe that, once certified by NetApp, the appliances can be treated as 'any other' NFS server by client machines, or would you advocate specific interoperational testing with NetApp kit? Cheers, Mike Thomson -- \\|||// Minds are like parachutes; (@ @) They only work when open. *---oOO-(_)-OOo------------------------------------* * Michael Thomson Email: mt53590(a)ggr.co.uk * * Unix Specialist Internal: 782 4393 * * Glaxo Wellcome External: 01438 764 393 * * Fax: 01438 763 204 * * .oooO Oooo. Mobile: 0498 725 047 * *--( )---( )-----------------------------------* \ ( ) / (Quote: Sir James Dewar) \_) (_/

4 6

F330 running at 100%
by Christoph Doerbeck 04 May '98

04 May '98

Greetings, Today we experienced an F330 pegging at 100% CPU. netstat and nfsstat didn't reviel anything eye popping, and so I'm asking for suggestions as to what might cause this? I would guess that a network interface shouldn't be capable of causing this, but I'll let you tell me.... Here's the system info: ===== SYSCONFIG-V ===== NetApp Release 3.1c: Wed Apr 3 16:40:37 PST 1996 System ID: XXXXXXXX slot 0: System Board 90 MHz (NetApp System Board I) Memory Size: 256 MB slot 0: SCSI Host Adapter 0 (QLogic ISP 1020) 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) slot 0: Ethernet Controller e0 MAC Address: 00:a0:98:00:00:20 (100tx) slot 4: Dual SCSI Host Adapter (NetApp SCSI Adapter I) SCSI Host Adapter 4a 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) SCSI Host Adapter 4b slot 6: NVRAM (NetApp NVRAM I) Memory Size: 8 MB Battery 1 Status: 100% (3.29v) Battery 2 Status: 100% (3.29v) slot 7: Ethernet Controller e7 (Znyx) MAC Address: 00:c0:95:f8:4b:6c (100tx) slot 8: FDDI Network Adapter f8 (DEC 3002) MAC Address: 08:00:2b:b3:10:71 (Dual Attach Fiber) slot 9: Dual SCSI Host Adapter (NetApp SCSI Adapter I) SCSI Host Adapter 9a 0: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 1: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 2: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 3: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 4: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 5: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) 6: SEAGATE ST15230N 0638 Size=3.9GB (8386733 blocks) SCSI Host Adapter 9b - Christoph

3 4

file locking problem
by Jason D. Kelleher 01 May '98

01 May '98

This past Saturday we moved our mail spool from a SunOS 4.1.3_U1 system to our NetApp F330 running ONTAP 4.3.3. Since then, we've had problems with procmail processes hanging on open file locks. This only occurs when someone leaves mailtool or dtmail running. Does anyone have any idea why mailtool won't handle file locking when mounting the spool from a NetApp, but will when mounting from a SunOS system? Any insight would be greatly appreciated. jason --- Jason D. Kelleher kelleher(a)susq.com Susquehanna Investment Group 610.617.2721 (voice) 401 City Line Ave, Suite 220 610.617.2916 (fax) Bala Cynwyd, PA 19004-1122

2 1

Re: file locking problem
by sirbruce＠ix.netcom.com 30 Apr '98

30 Apr '98

On 04/30/98 10:59:37 you wrote: > > > > This past Saturday we moved our mail spool from a SunOS 4.1.3_U1 >system to our NetApp F330 running ONTAP 4.3.3. Since then, we've had >problems with procmail processes hanging on open file locks. This only >occurs when someone leaves mailtool or dtmail running. > > Does anyone have any idea why mailtool won't handle file locking >when mounting the spool from a NetApp, but will when mounting from a >SunOS system? > > Any insight would be greatly appreciated. I would try applying the numerous patches for 4.1.3_U1, particularly the NFS patches and the mailtool patches from your descriptions. I might also check out upgrading to 4.1.4 and it's associated patches. Actually, I'm assuming your clients are the same flavor as your old mail spool server. If you have Solaris 2.x clients, there are patches for them as well. If the problem still persists you can talk to Netapp, probably get them a trace and they can find out who isn't doing locking correctly. Bruce

1 0

Re: syslog.conf
by varun＠netapp.com 29 Apr '98

29 Apr '98

> From dfinkels(a)siac.com Wed Apr 29 10:05:13 1998 ... > > Gentle readers, > Before I ask NetApp directly, I was curious if anyone knew of > the > syslog level that NetApp filers use? I want to redirect syslog daemon > messages to a remote host but keep the NetApp-specific messages in a > different file from the regular UNIX system messages. I was hoping it > used something like level1 or level2. If anyone knows the answer I'd be > most appreciative to this kind person. > I'm not sure you can log NetApp specific messages to a different file since the filer uses the same levels as regular Unix systems - (see na_syslog.conf(5)). What you could do is log NetApp specific messages to a remote system and grep for the filer's hostname in the remote system's messages file. It's probably easiest to drive this with a cron script. You might also be interested in Swatch which is a tool (publically available, I think) that allows you to monitor messages files and trigger on user defined events.

1 0

syslog.conf
by dfinkels＠siac.com 29 Apr '98

29 Apr '98

Gentle readers, Before I ask NetApp directly, I was curious if anyone knew of the syslog level that NetApp filers use? I want to redirect syslog daemon messages to a remote host but keep the NetApp-specific messages in a different file from the regular UNIX system messages. I was hoping it used something like level1 or level2. If anyone knows the answer I'd be most appreciative to this kind person. -- Daniel Alex Finkelstein Infrastructure Enhancement Group Systems and Technologies Support phone 212.383.2951 pager 917.427.1630 Securities Industry Automation Corporation

1 0

subscribe
by Lisa Malgeri 29 Apr '98

29 Apr '98

1 0

RE: RAM and NVRAM for F330
by sirbruce＠ix.netcom.com 27 Apr '98

27 Apr '98

On 04/27/98 10:24:26 you wrote: > >> Sounds very much like a shipping issue to me. > > >NetApp Field Support 101: >------------------------- >Practice saying: > >"Of Course We test this hardware! It must be a shipping problem!". > >We've only had one in here for 6 months and I've already learned >that. I don't know if there's anything to it, but it sounds like >a prevalent enough story that NetApp should change their >shipping/handling/packing procedures. Sounds like they've >identified it as a problem to many of us, so how long before >it's fixed? > >-Jeff >(2 bad drives and an EMU shelf with a bad slot in two weeks) If you really want this question answered, you should probably contact Netapp directly, not email this list. While there are employees of Netapp that answer questions here from time to time, it's certainly not the usual channel of communication for addressing issues such as the one you bring up. Bruce

1 0

RE: Budtool to backup netapp
by Weeks, Thomas 27 Apr '98

27 Apr '98

So is ANYONE satisfied with any 3rd party NDMP colutions? IT's a nice fast protocol.. but I'm not seing a lot of support... Is the major advantage with NDMP (besides speed) that it backs up both your ACLs AND your UFS file permissions? Is there any other wayt o do this? Tom D Tek > -----Original Message----- > From: Jason D. Kelleher [SMTP:kelleher@susq.com] > Sent: Thursday, April 23, 1998 9:55 AM > To: Alan Phoenix > Cc: 'toasters(a)mathworks.com' > Subject: Re: Budtool to backup netapp > > In message <17AD4E991EBDD111B6E000A0C99DD8350BA1(a)ntmail05.pc.sas.com>, > Alan > Phoenix writes: > >Has anyone tried using Budtool to backup a netapp? > > Yup. We've been using BudTool to backup our F330 for about 5 > months. We spent a month or two working the kinks out of it before we > let it touch our filer. Here's what we found: > > 1) BudTool's reporting is horrible. End of story. Anyone who > tells you otherwise is either deranged or hasn't actually used > the product. Fortunately, if you know Perl, writing a script > to > parse the logfile and send out a readable report (and page on > fatal errors) is fairly trivial. > > 2) BudTool's built in scheduling could only have been written by a > fool who liked GUIs and never actually had to support a backup > solution in a production environment. cron and a small shell > script handled this problem. (AMANDA has the best backup > scheduling in my opinion. Someday there'll be a vendor who > picks up on it.) > > 3) User level restores aren't supported for NDMP and only work for > UNIX clients if your willing to throw security out the window. > When doing a restore via NDMP, the destination for the restore > has to be on a filer. If your users need to be able to restore > data from tape, pick another product. If you're willing to > pull > stuff off tape for them (the GUIs not bad, but not great > either) > occasionally, then you'll be ok. > > 4) Having one BudTool server control a directly connected 100 tape > DLT400 jukebox, a 5 tape stacker connected to our F330, and a 5 > tape stacker connected to our research departments number > cruncher is pretty nifty. Having all the tape and file > histories in one place is nice too. > > 5) BudTool has a utility called btcp which will copy all your most > current backup requests (Lev 0s and all necessary incrementals) > to a set of tapes for offsite storage. It doesn't just dd a > bunch of tapes. Very nice. Unfortunately, btcp is a little > brain-dead and tries to copy _all_ the requests to one set of > tapes. If you have a couple hundred GB worth of backups, this > can take a really long time. Again, a little shell script > fixed > this problem. > > > All in all, I don't think I've ever been 100% satisfied with any > software product. But BudTool gets the job done (with a little help). > > > jason > > --- > Jason D. Kelleher kelleher(a)susq.com > Susquehanna Investment Group > All opinions expressed are my own, etc, etc...

1 0

RE: RAM and NVRAM for F330
by Jeff Stampes 27 Apr '98

27 Apr '98

> Sounds very much like a shipping issue to me. NetApp Field Support 101: ------------------------- Practice saying: "Of Course We test this hardware! It must be a shipping problem!". We've only had one in here for 6 months and I've already learned that. I don't know if there's anything to it, but it sounds like a prevalent enough story that NetApp should change their shipping/handling/packing procedures. Sounds like they've identified it as a problem to many of us, so how long before it's fixed? -Jeff (2 bad drives and an EMU shelf with a bad slot in two weeks)

1 0

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 April 1998