toasters April 2003

toasters@lists.teaparty.net

95 participants
102 discussions

RE: Data ONTAP Upgrade
by Sam Schorr 04 Nov '03

04 Nov '03

For all the inquiring minds, I found this under the download section: ********************************************************************** DEBUG PATCH RELEASE 6.3.1D8 Based on release 6.3.1 ********************************************************************** This is a DEBUG patch, which means it has fixes that have not been released in a regular software version yet. These fixes, if validated, will be checked in and released in a future release after adequate QA and testing. Fixes contained in this patch release are: 85294 Ineffective nlm GRANTED requested (callback) 78177 Renaming a small number of files repeatedly causes WAFL dir size to grow 83697 CPU at 100% after 6.2.1 upgrade from 6.1.3R1, with low NFS Ops and Disk Ops 80286 Problem accessing ~snapshot directory when using the "nosymlink_strict_security" share option 82176 File access can fail when using a widelink that maps to a share that supports widelinks 78570 Slow FTP performance with clustering enabled. 80332 SNMP may stop responding after accessing miscGlobalStatus on FAS9xx appliances. 81905 kma.c crash in wafl_zombie_growfile_handler 83681 CIFS file owner may be set incorrectly 85651 CIFS SETUP fails with "DSA is unwilling to perform" 85653 can't set file attributes when restoring with Veritas NetBackup 81631 isp2100 not handling port_logged_out status correctly for CT requests 86862 Master filer panic during takeover - memory leak from dup_user_field() 86464 Volume SnapMirror from an F840,F880,F9XX to a platform other than F840,F880 or F9XX on restarting may lead to corruption on destination. -----Original Message----- From: Hill, Aaron [mailto:aaron.hill@navitaire.com] Sent: Sunday, February 16, 2003 2:14 PM To: 'Chris Blackmor' Cc: 'Paul McGuinness (ext. 771)'; 'toasters(a)mathworks.com' Subject: RE: Data ONTAP Upgrade Hey there, I welcome questions. Unfortunately, my answers may not be sufficient to satisfy your mental hunger. To be honest, I don't know exactly what the D8 does. I was informed that it fixes the snapmirror code. The error was found to occur only in our "specific" circumstance. So what was/is our circumstance? 1) F880 source snapmirroring 3 batch area volumes to an F820 target across a 20Mbit Ethernet WAN. 2) The amount of data change per day is high. Approximately 10-40Gb per volume. 3) We were experiencing poor throughput across the WAN link (carrier issue) and had to frequently abort the snapmirror and delete snapshots from the F880 source in order to prevent snapshot space over-running production data space. This throughput has since been addressed (before D8). 4) The F820 target panicked a couple of times and dumped to the ok prompt. One of the target volumes was found to be corrupt. It was difficult to say if the source filer caused it or the target filer developed the corruption independently. We had some cases open and ran wafl checks and scans on both filers as a result. No errors were turned up. 5) The crash dump file was ftp'd to NetApp. This lead to the 6.3.1D8 debug release. When I get some more time, I might read into it a bit further. For now, I am more than happy that they have addressed the issue and fixed it very quickly. We have not had any problems with 6.3.1 or the D8 releases. Thanks, Aaron -----Original Message----- From: Chris Blackmor [mailto:chris.blackmor@amd.com] Sent: Sunday, February 16, 2003 6:48 AM To: Hill, Aaron Cc: 'Paul McGuinness (ext. 771)'; 'toasters(a)mathworks.com' Subject: Re: Data ONTAP Upgrade What does the D8 fix for snapmirror? Inquiring minds want to know. ;) C- On Fri, Feb 14, 2003 at 07:18:19PM -0600, Hill, Aaron wrote: > We are running 6.3.1 on one filer (F880) and 6.3.1D8 (debug release for a > snapmirror problem we were having) on another (F820). 2 others still running > 6.2.2 I believe. > > As far as I know, all new F960s being shipped have 6.3.1 on them. > > So overall, I have to say I recommend it. If you are snapmirroring, make > sure you put 6.3.1D8 on your destination filer, that is the advice from our > NetApp representative. > > Thanks, > Aaron Hill > Systems Engineer > www.navitaire.com > > > -----Original Message----- > From: Paul McGuinness (ext. 771) [mailto:Paul.McGuinness@fineos.com] > Sent: Saturday, February 15, 2003 2:58 AM > To: 'toasters(a)mathworks.com' > Subject: Data ONTAP Upgrade > > Hi, > I have a F720 currently running on Data ONTAP 6.1.2R2 and everything is > running fine. > My question is to those of you 6.6.2 (the current GA release) and those of > you on 6.3.1. > > I was going to upgrade to 6.2.2, just to keep my system up to date, but > according to the NOW site there are a good few more active systems running > 6.3.1. > > Would 6.3.1 be a better upgrade to go to? I also see that there is now a 6.4 > first customer shipment release (12th Feb) but I think I'll leave that for > those of you who have filers to play with.... > :o) > > So 6.6.2 or 6.3.1? > > > > > > ************************************************************************** > The information contained in this e-mail is confidential, > may be privileged and is intended only for the use of the > recipient named above. If you are not the intended > recipient or a representative of the intended recipient, > you have received this e-mail in error and must not copy, > use or disclose the contents of this email to anybody > else. If you have received this e-mail in error, please > notify the sender immediately by return e-mail and > permanently delete the copy you received. This email has > been swept for computer viruses. However, you should > carry out your own virus checks. > > > Registered in Ireland, No. 205721. http://www.FINEOS.com > ************************************************************************** -- -------------------------------------------------------------------- * Chris Blackmor _______ | * * Advanced Micro Devices \____ | | Toto... I've * * Phone: (512) 602-1608 /| | | | a feeling we're * * Fax: (512) 602-5155 | |___| | | not in Kansas * * Email: chris.blackmor(a)amd.com |____/ \| | anymore. * -------------------------------------------------------------------- * My comments are mine, and mine alone. * --------------------------------------------------------------------

2 1

Recoverable failing disk
by Dan OBrien 30 Apr '03

30 Apr '03

Sage advice requested, please. I've been getting a couple of correctable failures on this drive per week for the last few months. Should I just keep going with it or just fail it by hand and be done with it? -------- Original Message -------- Sun Apr 27 01:00:00 EDT [raid_scrub_admin]: Beginning disk scrubbing... Sun Apr 27 01:05:20 EDT [isp_main]: Disk 7a.2(0xfffffc0000dd6c40): op 0x28:0003eb68:0080 sector 256991 recovered error - (1 17, 2) Sun Apr 27 07:46:59 EDT [consumer]: Scrub found 0 parity inconsistencies Sun Apr 27 07:46:59 EDT [consumer]: Scrub found 0 media errors Sun Apr 27 07:46:59 EDT [consumer]: Disk scrubbing finished... ------------------------------------------------------------------------------ Thanks, Dan O'Brien, dmobrien(a)lcsi.net Cell: 614-783-4859 Work: 614-476-8473 Home: 740-927-2178 Pataskala, OH

1 0

Running CVS via netapp NFS ?
by Charles Bartels 30 Apr '03

30 Apr '03

Hi, Is there any general consensus on running CVS over the netapp's NFS? A while back I heard that it was not advisable but I thought things might have changed. -C.

3 2

Re: Running CVS via netapp NFS ?
by Chris Good 30 Apr '03

30 Apr '03

Charles Bartels wrote: > Is there any general consensus on running CVS over the netapp's NFS? > A while back I heard that it was not advisable but I thought things might > have changed. Worked fine for us for as long as I can remember which I think is late 97 possibly early 98.

1 0

LDAP Integration
by markallen 30 Apr '03

30 Apr '03

Sun has announced they will no longer support nis or nisplus in the future and the upgrade path is to LDAP using the iplanet directory server 5.1 on Solaris 9. I upgraded a test environment that is now serving hosts, netgroups, passwd, group, and autmount tables via LDAP. I have Solaris and AIX clients binding to this server. Data Ontap 6.4 came with ldap support but I haven't had any luck getting it to work. I would like to get hosts, passwd, group, and netgetgroup services from LDAP. Here is a listing of my settings: options ldap ldap.base dc=my,dc=domain,dc=com ldap.enable on ldap.name cn=proxyagent,ou=profile,dc=my,dc=domain,dc=com ldap.passwd ****** ldap.port 389 ldap.servers 1xx.2xx.1xx.xx ldap.servers.preferred 1xx.2xx.1xx.xx cat /etc/nsswitch.conf passwd: ldap files hosts: ldap files group: ldap files netgroup: ldap files Any help would be greatly appreciated. I make added these changes and tested it by pinging a host that is in the ldap database and had no luck. -Mark

1 0

RE: i need help making sense of what happened here
by Daniel Finn 30 Apr '03

30 Apr '03

Interesting. Not slots are empty on these. -----Original Message----- From: Dirk Schmiedt [mailto:Dirk.Schmiedt@munich.netsurf.de] Sent: Tuesday, April 29, 2003 2:47 PM To: Daniel Finn Cc: 'toasters(a)mathworks.com' Subject: Re: i need help making sense of what happened here Daniel Finn wrote: >Today a disk failed, but different from what I'm used to seeing. It appears >now that I look at it that disk 4.19 failed and it took spare disk 4.38 and >began rebuilding on that. What seems strange though is that it kept trying >to read or write to disk 4.19 until I physically pulled the disk out. Why >would this have happened? > Hello Daniel It appears, that the electronic controller of your disk failed. The filer tried to tell the disk "you are broken" and tried to write on the disks label, to make shure wherever this disk will go to ... it will tell any technician by it's raidlabel: I am broken. In your case I also see SES error messages for this shelf. ... let's calculate: Disk 19=16+3 Let me guess ... This is a FC-7/8/9 shelf and the slot 2 is/was empty? The slots 2 AND 3 should be filled both in those old schelves, just in case one of those disks breakes... I think you can ignore the warnings you have seen. They were produced by the disks electronic. Smile & regards Dirk

3 2

rdate and time keeping.
by Gavin Kelman 30 Apr '03

30 Apr '03

We're using rdate to keep our Filer's clock in sync to prevent clock skew errors when compiling things on NFS mounts. There seems to be a bug in OnTap 6.3.1R1. The clock works it's way out of sync, (hence why we use rdate), and we get: Tue Apr 29 15:25:18 BST [Java Thread:notice]: TimeDaemon: Rdate (rfc868) server 'dali.lionbio.co.uk' reports that the time is Tue Apr 29 15:25:21 BST 2003, but the filer thinks the time is Tue Apr 29 15:25:18 BST 2003. This time offset is too large to cause us to modify the time automatically (max allowable skew: 1.000 secs). If the time reported by the time server is correct, set the filer time using the 'date' command. So, to clear this, I set the time by hand using "date". This works fine and we occasionally see: Tue Apr 29 16:04:06 BST [Java Thread:info]: TimeDaemon: Time offset within tolerance [dali.lionbio.co.uk]: actual -0.640 secs, tolerance 1.500 secs, not changing time. And after a time we get the first out-of-sync message. In effect, rdate is doing nothing at all to change the time, as the Max Skew rdate will change over is 1 second, but won't bother changing until it's at least 1.5 seconds out of sync. Surely, this is broken? Cheers, Gavin. -- Gavin Kelman Unix Administrator Email : gavin(a)metahusky.net

5 5

AW: CIFSDispatcher Error
by stefan.holzwarth＠adac.de 30 Apr '03

30 Apr '03

I also see that connection terminations. I think you should decrease the cache time to avoid "too less" communication with the DC. Kind Regards Stefan Holzwarth -----Ursprüngliche Nachricht----- Von: Kumar, Rahul [mailto:rahul.kumar@eds.com] Gesendet: Mittwoch, 30. April 2003 08:08 An: Michael Schipp; toasters(a)mathworks.com Betreff: RE: CIFSDispatcher Error Is there ay way to increase the cache time on filer Shd I enable opslock for cifs shares Rahul -----Original Message----- From: Michael Schipp [mailto:mschipp@asi.com.au] Sent: Wednesday, April 30, 2003 11:35 AM To: Kumar, Rahul; 'toasters(a)mathworks.com' Subject: RE: CIFSDispatcher Error From the NOW site. ------------------------------------------------------------------------ ---- Answered You can expect this from the filer. It is mostly due to idle timeouts between the Filer and it's authenticating DC. I would say it is most like ( by default ) a 15 minute drop after the last need to authenticate ( like a new logon, or new cifs share connect that isn't cached ) Thank you Michael A Schipp ASI Solutions IT LAN/WAN Administrator Phone : 02 9384 8095 Mobile : 0402 907 928 E-Mail : mschipp(a)asi.com.au Visit us at http://www.asi.com.au -----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: Wednesday, 30 April 2003 2:14 PM To: toasters(a)mathworks.com Subject: CIFSDispatcher Error Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

RE: CIFSDispatcher Error
by Kumar, Rahul 30 Apr '03

30 Apr '03

Is there ay way to increase the cache time on filer Shd I enable opslock for cifs shares Rahul -----Original Message----- From: Michael Schipp [mailto:mschipp@asi.com.au] Sent: Wednesday, April 30, 2003 11:35 AM To: Kumar, Rahul; 'toasters(a)mathworks.com' Subject: RE: CIFSDispatcher Error From the NOW site. ------------------------------------------------------------------------ ---- Answered You can expect this from the filer. It is mostly due to idle timeouts between the Filer and it's authenticating DC. I would say it is most like ( by default ) a 15 minute drop after the last need to authenticate ( like a new logon, or new cifs share connect that isn't cached ) Thank you Michael A Schipp ASI Solutions IT LAN/WAN Administrator Phone : 02 9384 8095 Mobile : 0402 907 928 E-Mail : mschipp(a)asi.com.au Visit us at http://www.asi.com.au -----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: Wednesday, 30 April 2003 2:14 PM To: toasters(a)mathworks.com Subject: CIFSDispatcher Error Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

RE: CIFSDispatcher Error
by Michael Schipp 30 Apr '03

30 Apr '03

From the NOW site. ---------------------------------------------------------------------------- Answered You can expect this from the filer. It is mostly due to idle timeouts between the Filer and it's authenticating DC. I would say it is most like ( by default ) a 15 minute drop after the last need to authenticate ( like a new logon, or new cifs share connect that isn't cached ) Thank you Michael A Schipp ASI Solutions IT LAN/WAN Administrator Phone : 02 9384 8095 Mobile : 0402 907 928 E-Mail : mschipp(a)asi.com.au Visit us at http://www.asi.com.au -----Original Message----- From: Kumar, Rahul [mailto:rahul.kumar@eds.com] Sent: Wednesday, 30 April 2003 2:14 PM To: toasters(a)mathworks.com Subject: CIFSDispatcher Error Fellow Toasters, On one of the F820, running Ontap 6.3.1R1 we are seeing lots of [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated [CIFSAuthen:info]: Connection with DC \\DC established [CIFSDispatcher:info]: Connection with \\DC terminated We have reset the machine account in win2k nativemode domain a few times but it doesn't seem to be helping. This error is not being seen on our 3 other filers Regards Rahul **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

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 2003