toasters September 2001

toasters@lists.teaparty.net

113 participants
151 discussions

Re: Unexplainable unresponsiveness of F820
by Kerry Schwab 05 Sep '01

05 Sep '01

I've run into a bug with the telnetd daemon on the F820. Closing a telnet session to the filer while it has pending output sometimes causes the whole filer to "hang". This is occuring on 6.0.1R3. I did find some related bugs in the knowledge base, but I've resorted to not using the telnet interface for now. == Kerry >>> <mcope(a)isisph.com> 09/05/01 10:46AM >>> I've recently moved files from a F740 onto a new F820. This happened on Monday and on Tuesday morning the F820 suddenly stopped serving data. It became so unresponsive that I was unable to even get in thru the console. I got prompted for a password but it never got to a command line prompt. The Filer didn't appear to be excessively busy beforehand and the network connection (Gigabit) still appeared to be fine. Basically, the Filer appeared fine externally and the LCD panel showed that there were 0 ops a second. The only way I could get the Filer "running" again was to cycle power. The Filer has been fine since then. There were no messages in the syslog and it didn't dump a core file (I know now how to force it to dump a core for diagnosis), so NetApp tech support hasn't been able to provide much assistance or explanation. I've seen this same behavior twice on the the F740 in the last 2 months but that had been diagnosed as a faulty Fibre Channel controller seizing up when the workload got too high. Other than the actual data files, the only thing these two Filers have in common is Data ONTAP 6.1R1. I'm running 6.1R1 on two other Filers and have had no problems. It just seems very coincidental that I didn't experience this on the F740 until after I installed this version of ONTAP. Anyone else seen this behavior before or noticed any irregularities with 6.1R1 (I'm not running in a cluster so the latest updates/bug fixes don't appear helpful) Thanx, Michael Cope UNIX/Linux Systems Administrator Isis Pharmaceuticals mcope(a)isisph.com UNIX is very user friendly... it's just highly selective about who it makes friends WITH!

1 0

netapp bad disk bug
by Collin LeGault 05 Sep '01

05 Sep '01

Hey everyone, I have a couple of netapps that are doing this same weird thing. They both are reporting a bad disk, and when you replace the disk, the red light comes on for the new disk, and the netapp marks it as a broken disk. They are F760, running 5.3.5R3 of ontap. Someone thought we should take a down time and reboot them to see if that fixed it, but I wanted to avoid the huge amount of work that would be and see if anyone here has any suggestions. If you need more information about the filers to figure this out, let me know. Thanks in advance, coLLin LeGault

2 1

RE: Filer hung up tight
by Jankowski Ted-CTJ012 05 Sep '01

05 Sep '01

It's in the same place on the 800 series as well. The curious thing it that with the front panels off, the button sticks out on the 700 series and is recessed in the 800 series. -Ted -----Original Message----- From: Sam Rafter [mailto:rafter@netapp.com] Sent: Thursday, August 23, 2001 6:49 PM To: Maglinger, Paul Cc: 'NetApps list server' Subject: Re: Filer hung up tight You do have one alternative in this situation. There's a synch button on the front of your filer. On the 700 series, it's the little hole under the LEDs. When you press that, the filer should drop to the ok prompt. From there, you can type 'sync'. There's a NOW article on doing just very thing: http://now.netapp.com/Knowledgebase/solutionarea.asp?id=3.0.620867.2715498&… In the 'nothing was working' checklist, was NFS/CIFS and FilerView checked as well? 850 ops is a lot to do nothing at all. If the number never fluctuated, I'd have my suspicions that it wasn't getting updated. We have watchdog systems in place to catch such things, so I'm a bit mystified. -Sam * It was Thu, Aug 23, 2001 at 04:26:24PM -0500 when Maglinger, Paul wrote: > > We have a 740 filer running 6.0.1R3. Last night I got a page that > "nothing was working". I headed into work and found that: > > > > 1) I could not telnet into the filer. > > 2) I could not get in through console either. > > 3) The display on the front of the filer said 850 ops but the activity > led wasn't flashing at all. > > > > I figured I had no choice, so I shut it down hard and brought it back > up. Everything came up fine. The message file posted a time stamp at > 11:00pm but nothing at midnight (this was 1:30am). The message file > also said that the fiiler was down for 6057 secs. The crash folder > had one file in it called "bounds" and just contained "-1 -1". > Backups were being performed at the time using Veritas Backup Exec. > The backup log said everything was going fine until it found a > "corrupted file", then it started skipping files until the filer was > rebooted and it started in backing up again. We're trying to figure > out what went wrong but didn't have much to go on. Anyone have any > thoughts where to look now (or if this happens again)? > > > > "No matter where you go, there you are." > > > > Paul Maglinger > > System Administrator > > Shoe Carnival, Inc. --

1 0

BCS VS ZCS Zone Disks
by Noll, Kevin 05 Sep '01

05 Sep '01

Hi All We have 9 x F760 Netapp Filers, 4 in Cluster Mode and the 9th one is what we have reserved for Snapmirror. We currently snapmirror volumes from these 8 filers to the backup filer. However, All existing filers have the old FC9 Disk Shelves with 36 gig disks in, and the new F760 Backup Filer has the new DC14 Disk Shelves with 72 gig drives. What should have been a disk for disk snapmirror configuration, either by having 36 gig to 36 gig or 36 gig x 2 to 72 gig disk, has become more complicated as the new disks have a different Zone. The new zone makes the new 72 gig disks slightly smaller than 2 x old 36 gig disks. I was wondering if anyone else might have encountered this problem yet, and if there is any workarounds as to disk zoneing, etc etc. Thanks KEVIN -----Original Message----- From: Jay Newton [mailto:jnewton@chkenergy.com] Sent: 04 September 2001 21:05 To: 'toasters(a)mathworks.com' Subject: Snapshots of QTREEs Is there a way to snapshot an individual QTREE from command line or must it be the entire volume. I have a volume set up for databases and I want to snapshot from command line individual QTREEs that represent different types of databases. Any help would be appreciated! Jay Newton Systems Engineer - Chesapeake Operating (405)810-2683 (405)879-9578 fax ******************************************************************************************** " This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message ". ********************************************************************************************

3 2

RE: BCS VS ZCS Zone Disks
by Noll, Kevin 05 Sep '01

05 Sep '01

Somehow, a comparison of block for block of the zcs disks and the bcs disks come out with zcs having a slightly bigger size. Under normal conditions, this small size difference would not really be seen, but if you try to do a snapmirror between the two, having the bcs disks as the destination, the filer complains that there is not enough space. So far we have had to work our disks with this formula. If a volume size of BCS disks is 4 = 1 parity 3 data (36 gig disks), then BCS disks would have to be 3 = 1 parity 2 data(72 gig disks. If a volume size of BCS disks is 9 = 1 parity 8 data (36 gig disks), the BCS disks would have to be 6 = 1 parity 5 data (72 gig disks instead of 5 = 1 parity and 4 data. So hence 4 data 72 gig disks are smaller than 8 36 gig disks. KEVIN -----Original Message----- From: Jeffrey Krueger [mailto:jkrueger@qualcomm.com] Sent: 05 September 2001 17:56 To: Noll, Kevin Cc: 'toasters(a)mathworks.com' Subject: Re: BCS VS ZCS Zone Disks It was my understanding that the ZCS disks were actually 520 block-per-sector disks rather than 512 blocks-per-sector and that the checksum was stored in the "extra" 8 blocks. This would essentially make it the same size as a 512 block disk with the same number of blocks, right? Maybe those disks are just smaller anyhow? -- Jeff On Tue, Sep 04, 2001 at 09:54:26PM +0100, Noll, Kevin wrote: > Hi All > > We have 9 x F760 Netapp Filers, 4 in Cluster Mode and the 9th one is what we > have reserved for Snapmirror. > > We currently snapmirror volumes from these 8 filers to the backup filer. > However, All existing filers have the old FC9 Disk Shelves with 36 gig disks > in, and the new F760 Backup Filer has the new DC14 Disk Shelves with 72 gig > drives. > > What should have been a disk for disk snapmirror configuration, either by > having 36 gig to 36 gig or 36 gig x 2 to 72 gig disk, has become more > complicated as the new disks have a different Zone. The new zone makes the > new 72 gig disks slightly smaller than 2 x old 36 gig disks. > > I was wondering if anyone else might have encountered this problem yet, and > if there is any workarounds as to disk zoneing, etc etc. > > Thanks > KEVIN ******************************************************************************************** " This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message ". ********************************************************************************************

1 0

cifs groups supported in ontap?
by neil lehrer 05 Sep '01

05 Sep '01

are the 6.1 variants supporting cifs groups? -- regards

1 0

Re: Volumes unmounting
by Ambrose_Earle＠shamrockfoods.com 05 Sep '01

05 Sep '01

I had a problem when Oracle used mounts that were not explicitly listed in exports. For example, I had mounted /vol/vol1/orafiles to /orafiles, but in the exports file on the filer I only had listed /vol/vol1. Everything was fine for weeks until I failed over. At that point, it was still mounted but it wasn't really there(permission denied, other weird messages) even though other similar mounts were fine and usable. I have since gone back and exported every directory that I mount to and I have failed over (and even survived some core dumps) without any further problems.

1 0

F85 retrofit ???
by Benoit Artuso 05 Sep '01

05 Sep '01

Hello, in my NOW console, i have a case opened called "F85 retrofit". I pretty sure that I never opened such a case and support(a)netapp.com does not answer my email. It really seems that NetApp opened a case behind my back to change something on our F85 (that works perfectly). Is there a problem with the F85 ? Does anyone know something more about that ? And, if there is such a problem, why NetApp does not tell me so ? Is it something that must be hidden ? I know there were some problems with the early F85 (they stopped selling them for 3 months !!!) but the marketing guy didn't know much more than "We don't sell this products until a 'we dont know' date". -- Benoit

1 0

Unexplainable unresponsiveness of F820
by mcope＠isisph.com 05 Sep '01

05 Sep '01

I've recently moved files from a F740 onto a new F820. This happened on Monday and on Tuesday morning the F820 suddenly stopped serving data. It became so unresponsive that I was unable to even get in thru the console. I got prompted for a password but it never got to a command line prompt. The Filer didn't appear to be excessively busy beforehand and the network connection (Gigabit) still appeared to be fine. Basically, the Filer appeared fine externally and the LCD panel showed that there were 0 ops a second. The only way I could get the Filer "running" again was to cycle power. The Filer has been fine since then. There were no messages in the syslog and it didn't dump a core file (I know now how to force it to dump a core for diagnosis), so NetApp tech support hasn't been able to provide much assistance or explanation. I've seen this same behavior twice on the the F740 in the last 2 months but that had been diagnosed as a faulty Fibre Channel controller seizing up when the workload got too high. Other than the actual data files, the only thing these two Filers have in common is Data ONTAP 6.1R1. I'm running 6.1R1 on two other Filers and have had no problems. It just seems very coincidental that I didn't experience this on the F740 until after I installed this version of ONTAP. Anyone else seen this behavior before or noticed any irregularities with 6.1R1 (I'm not running in a cluster so the latest updates/bug fixes don't appear helpful) Thanx, Michael Cope UNIX/Linux Systems Administrator Isis Pharmaceuticals mcope(a)isisph.com UNIX is very user friendly... it's just highly selective about who it makes friends WITH!

1 0

Volumes unmounting
by Noll, Kevin 05 Sep '01

05 Sep '01

Hi All We have an oracle Database mounted on an E4500. We then have 2 filers Filer A has volumes /vol/u01 /vol/u02 /vol/u03 Filer B has volumes /vol/u04 /vol/u05 /vol/u06 All volumes are mounted on this one E4500, but what we have expereienced is that from filer A, the /vol/u01 mount point UNMOUNTS periodically. About 10 times a day. Yet the rest of the volumes dont. Has anyone experienced this? THanks KEVIN ******************************************************************************************** " This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message ". ********************************************************************************************

3 2

Jump to page:

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 September 2001