toasters November 2002

toasters@lists.teaparty.net

77 participants
76 discussions

SNMP gathering of per-client stats
by Dylan Northrup 08 Nov '02

08 Nov '02

I notice in the Netapp MIB v1.2 there's a pclTable and pclEntry that look like they'll provide reports of per-client NFS statistics. I seem to recall that you can get per-client stats on the command line, but you have to turn on statistics gathering with statit -b, then turn off stat gathering with statit -enc. Can you just turn on stats gathering and poll via SNMP at any time or do you have to stop gathering stats before you can poll them? If so, what kind of performance impact does that have on the filer? Thanks in advance for any info you might have. -- Dylan Northrup northrup(a)loudcloud.com Unix System Administrator EDS Automated Operations

2 1

Root/Boot Disk(Volume?) Safety
by devnull＠adc.idt.com 08 Nov '02

08 Nov '02

Dear Toasters, I have 2 filers, a F810 and a F740. We also have some Sun servers that do NIS, sendmail, web server etc. To protect from root/boot disk failures on my Sun, i either use rsync to copy the root disk to another machine with the same hardware architecture or mirror the disk to a "backup" disk on the same machine. I have 2 volumes on my F810 vol0(which has 2 disks) and vol1(11 disks) on a DS-14 shelf. I am trying to protect myself from the situation where i lose both my vol0 disks, which will mean that my filer will no longer know anything about itself and i cant really "connect" from my backup server to the netapp to recover everything. If i lose 2 disks on vol1, i will lose all data, but i can slap 2 new disks on the filer and still recover all data from my backups. Any recommendations, thoughts on the same ? I use Legato for backup and do my backups over NFS, by mounting the volumes to my backup server. /dev/null devnull(a)adc.idt.com

2 1

RE: netapp not writing disks to /etc/.broken_disks when they fail
by Jenner, April 07 Nov '02

07 Nov '02

Really? I'm using 6.2.1R2 and have never been able to see /etc/.broken_disks I'm using an F740 and an F840 > -----Original Message----- > From: Daniel Finn [mailto:DFinn@studentadvantage.com] > Sent: Thursday, November 07, 2002 9:22 AM > To: 'toasters(a)mathworks.com' > Subject: netapp not writing disks to /etc/.broken_disks when they fail > > > It's an F740 running ONTAP 5.3.5R2. Is this normal? All the > rest of the > netapps we have write to /etc/.broken_disks when a disk fails > but they are > also running a more up to date version of ONTAP. Is it > because of the older > version? >

2 1

RE: netapp not writing disks to /etc/.broken_disks when they fail
by Watanabe, Steve 07 Nov '02

07 Nov '02

I'm pretty sure /etc/.broken_disks was first in the 6.0 release. It is informational and not used to re-fail disks on boot. In releases prior to 6.2 Data ONTAP attempted to write "broken" onto disks that were failed. It doesn't make a lot of sense to try to write to a disk that is broken. And so... Starting with the 6.2 release the fact that a disk has been failed is kept in the Failed Disk Registry (FDR) and Data ONTAP no longer tries to write to these disks. The FDR is kept outside of the filesystem on a subset of the disks in the system. -Steve > -----Original Message----- > From: Jenner, April [mailto:April.Jenner@netapp.com] > Sent: Thursday, November 07, 2002 12:30 PM > To: 'Daniel Finn'; 'toasters(a)mathworks.com' > Subject: RE: netapp not writing disks to /etc/.broken_disks when they > fail > > > Really? > > I'm using 6.2.1R2 and have never been able to see > /etc/.broken_disks > > I'm using an F740 and an F840 > > > -----Original Message----- > > From: Daniel Finn [mailto:DFinn@studentadvantage.com] > > Sent: Thursday, November 07, 2002 9:22 AM > > To: 'toasters(a)mathworks.com' > > Subject: netapp not writing disks to /etc/.broken_disks > when they fail > > > > > > It's an F740 running ONTAP 5.3.5R2. Is this normal? All the > > rest of the > > netapps we have write to /etc/.broken_disks when a disk fails > > but they are > > also running a more up to date version of ONTAP. Is it > > because of the older > > version? > > >

1 0

netapp not writing disks to /etc/.broken_disks when they fail
by Daniel Finn 07 Nov '02

07 Nov '02

It's an F740 running ONTAP 5.3.5R2. Is this normal? All the rest of the netapps we have write to /etc/.broken_disks when a disk fails but they are also running a more up to date version of ONTAP. Is it because of the older version?

1 0

F540 + Spares available
by Chuck Tomasi 06 Nov '02

06 Nov '02

I saw someone mention they had some old equipment (F630) on here. I was wondering if anyone was interested in picking up some "spare parts" for a NetApp. We have an F540 with two sets of diff SCSI 4GB shelves and two sets of diff SCSI 9GB shelves plus lots of spares (minus the motherboard.) If anyone is interested I can provide more details one-on-one. --Chuck Tomasi --Corp. Systems Administrator --Plexus Corp.

2 1

Re: Crossroads Problems
by Rune Bakken 06 Nov '02

06 Nov '02

Paul Caron <caron(a)sig.com> writes: > The problem we are experiencing is that the devices on our filers which > represent the SAN attached tape drives (shown by sysconfig -t) get randomly > recreated every time the Crossroads reboots. This was a problem that I encountered early in ONTAP 6.0.x (and 6.1.x to?) although sporadic, often enough to write a perl script to reset the tape aliases a few times a week. The LUN did not change, but the filers decided to rename the the aliases after the fc-card was reset or unplugged from the Brocade. (The last was a precautionary action to prevent the filer from panic'ing from a SCSI reset when the bridge or library was rebooted) > It appears as though the Crossroads is not presenting the tape > drives available on the ATL P7000 in the same order every time it > reboots. Although I am using the STK (Crossroad) 3250, I would believe that the menus/commands are similiar. Have you set any values in the "Fibre Channel to SCSI mapping"/ "Mapping Table# ?? Does the values change after reboot? What about "Display Attached SCSI Devices", does this change between reboots? > Has anyone else run into this situation? Is there any way of compensating > for this on the Netapp filers? Without the Crossroads not keeping the LUN values stable, you are out of luck. As far as I know there is no way of keeping track of a changing LUN. > > BTW, we have received suggestions regarding using the Netapp "storage > alias" and "storage unalias" commands. However, since the Galaxy backup > software relies on the actual device names (i.e. rst0l, nrst0l, urst0l, > etc.) this hasn't helped us so far. The Filer actually sees the real LUN value, but you may assign an alias, such as st01 st02 ... the device names rst02,nrst02,urst02 etc gives the device functionality. To sum up: If the Crossroads keep changing the LUN values, I would suggest you bring your vendor to bring this case directly to Crossroads. >>>>>>>>>>>>>>>>>>>.rune -- Rune Bakken Senior System Administrator Telenor Business Solutions (Nextra), ManagedServices/*/IP-Services Ph: +47 992 86 474

3 2

RE: Storagetek l80
by James Beal 06 Nov '02

06 Nov '02

Hello, We just became the proud owners of an L80. Its a bit of a big beast, and has baffled me a bit! I was wondering if anyone out there has one of these attached directly to the netapp, and also attached to a backup server such as an E250? During the selection process the company we engaged told me that each drive could be connected directly to a machine via SCSI. Looking at the back of the library, I think this is do-able, as each drive has SCSI connections, but I am not sure if these are intended to be connected to the library itself, then daisy chained together, or if the drive can be attached to the filer... I am waiting on a colleague to chase the supplier, but thought I put out request to you guys too... Okay, I don't have a toaster at present but I have looked after them in the past. I do have a L80 which is a great tape library. Each of the tape drives can be connected to a different system and storage tek will say if you have LTO drives in it then each drive should really be on a separate bus for performance/reliablity issues. What software are you using to drive this, netback from veritas can handle one having a robotic with the tape drives attached to different machines, for a toaster you would need to have a NDMP license as well, the robotic being controlled by the E250.

1 0

Re: disk_erase_label
by Chris Blackmor 06 Nov '02

06 Nov '02

Under priv set diag you can us the disk unfail command to make a broken disk a spare again but this is (as you said) used at your own risk. Is that what you are looking for? I have not had to use this command myself so I don't know what the real-world implications are. C- m5*> disk usage: disk <options> Options are: fail <disk_name> - fail a file system disk remove <disk_name> - remove a spare disk swap - prepare (quiet) bus for swap unswap - undo disk swap and resume service scrub { start | stop } - start or stop disk scrubbing unfail <disk_name> - make a failed disk a spare again shm_stats [<disk_name>] - Storage Health Monitor stats for a disk On Mon, Nov 04, 2002 at 04:55:35PM -0000, Edward Hibbert wrote: > I powered off a NetApp rather abruptly. Oops. > > Since then, one of my disks reckons it's broken. > > nacolt1> sysconfig -r > Volume vol0 (root) > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys > (MB/blks) > --------- ----- ------------ ---- -------------- > -------------- > parity 8.3 8 0 3 FC:A 34500/70656000 > 35003/71687368 (scrubbing RAID group, 20% done) > data 8.4 8 0 4 FC:A 34500/70656000 > 35003/71687368 > data 8.1 8 0 1 FC:A 34500/70656000 > 35003/71687368 > data 8.0 8 0 0 FC:A 34500/70656000 > 35003/71687368 > > Volume vol1 > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys > (MB/blks) > --------- ----- ------------ ---- -------------- > -------------- > parity FAILED N/A 34500/70656000 > data 8.6 8 0 6 FC:A 34500/70656000 > 35003/71687368 > data 8.5 8 0 5 FC:A 34500/70656000 > 35003/71687368 > > > I believe there's a command disk_erase_label which I can use to (at my own > risk) try to recover this disk. But it needs a disk id parameter. I'm > guessing that the disk id is 8.2 (the missing one from the info above) - but > that doesn't work. > > nacolt1*> disk_erase_label 8.2 > bad disk_name: 8.2 > > Is there some other disk id I need to find out - or is this just an > indication that the disk really is broken? > > This is an old ONTAP. version says: > > NetApp Release /n/snapon/dnoveck/537: Tue May 29 08:30:47 PDT 2001 > > Thanks for any help, > > Edward Hibbert > Internet Applications Group > Data Connection Ltd > Tel: +44 131 662 1212 Fax: +44 131 662 1345 > Email: eh(a)dataconnection.com Web: http://www.dataconnection.com > -- ----------------------------------------------------------------------- * Chris Blackmor _______ | * * Advanced Micro Devices \____ | | My comments are * * Phone: (512) 602-1608 /| | | | mine, and mine * * Fax: (512) 602-5155 | |___| | | alone. * * Email: chris.blackmor(a)amd.com |____/ \| | * ----------------------------------------------------------------------- * "Forty-two!" he said with a malicious grin. * * "No, doesn't work. Nevermind." * * Restaurant at the End of the Universe * * Hitchhikers Guide to the Universe * -----------------------------------------------------------------------

1 0

nfs file size limits
by Daniel Finn 05 Nov '02

05 Nov '02

what are they? I came across some posts while searching groups.google.com and some people mentioned that it's 4G for nfs v2 and higher for v3. Does anyone on here know for sure? Thanks Dan

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 November 2002