toasters

toasters@lists.teaparty.net

2 participants
13529 discussions

disk_usage.pl script not working after upgrade to Ontap 6.3.1R1
by Maglinger, Paul 02 May '03

02 May '03

We were using a great perl script that we downloaded from NOW to monitor our quotas called disk_usage.pl. After upgrading from Ontap 6.1.1R2P1 to 6.3.1R1 it no longer works except for just one of the qtrees. None of the permissions or qtree styles have changed. Anyone had a similar experience? Our glory is not in never falling, but rising every time we fall. Paul Maglinger, A+, CA, CCA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com

1 0

Unicode Format Log Entries
by Steve Evans 01 May '03

01 May '03

I've been getting entry's in my logs that look like this since I upgrade ONTAP from 6.1.2R3 to 6.3.1R1 and updated the system documentation on the filer. Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: \~snapshot\nightly.0\etc\http\doc\html\filer Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: \~snapshot\nightly.0\etc\http\doc\html\netapp Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: \~snapshot\nightly.0\etc\http\doc\html\ontap Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: \~snapshot\nightly.0\etc\http\doc\pdfs\filer Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: \~snapshot\nightly.0\etc\http\doc\pdfs\netapp Thu May 1 01:45:44 PDT [10/100/1000-IV/e4:info]: CIFS attempted to access a directory that is not in Unicode format in a snapshot on vol0. Share relative path name: \~snapshot\nightly.0\etc\http\doc\pdfs\ontap Steve Evans SDSU Foundation (619) 594-0653

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

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