toasters

toasters@lists.teaparty.net

13520 discussions

MCA: fatal Processor error. in process raid_xor_server
by courier＠telica.com 09 Nov '02

09 Nov '02

Hello Expert Toasters: We have Filer F820 with 42 disks, OS is Netapp release 6.1R1. It was running good for last two years ( my finger cross here.) Now suddenly I got the error below from the logs. MCA: fatal Processor error. in process raid_xor_server on release NetApp Release 6.1R1 Netapp fix this with replacing System board and its RAM. My question to you all: What is "raid_xor_server mean in this error" means? I am more concern on disks array then Systems Board or RAM. Anyone has this problems before any would like to share. I would appreciated. Thanks, C-

1 0

Fw: DOT Version up 6.1.2R1D4 to 6.2.1R2
by Motoyoshi 09 Nov '02

09 Nov '02

Dear Toasters, Sorry mistake and more information. >So, looks like quota processing but our quotas file as lines. So, looks like quota processing but our quotas file as 6 lines. Console displayed "[filer-name:WAFL_LOPRI:info]: Volume vol0 upgrade og acl tids complete Thank you, -motoyoshi Forwarded by Motoyoshi <k_moto(a)ctc-g.co.jp> ----------------------- Original Message ----------------------- From: Motoyoshi <k_moto(a)ctc-g.co.jp> To: toasters(a)mathworks.com Date: Sat, 09 Nov 2002 19:46:32 +0900 Subject: DOT Version up 6.1.2R1D4 to 6.2.1R2 ---- Hello Toasters, We upgrading DOT 6.1.2R1D4 to 6.2.1R2. The system dose not boot up.(No prompting from console) LCD display "/etc/rc/quota vol1". So, looks like quota processing but our quotas file as lines. And befor upgrade 6.0.3 to 6.1.2R1D4 no problem. Dose any one had same problem ? Thank you, -motoyoshi -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Support 2 Group / System Support Dept. CTC Technology --------------------- Original Message Ends -------------------- -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Support 2 Group / System Support Dept. CTC Technology

1 0

DOT Version up 6.1.2R1D4 to 6.2.1R2
by Motoyoshi 09 Nov '02

09 Nov '02

Hello Toasters, We upgrading DOT 6.1.2R1D4 to 6.2.1R2. The system dose not boot up.(No prompting from console) LCD display "/etc/rc/quota vol1". So, looks like quota processing but our quotas file as lines. And befor upgrade 6.0.3 to 6.1.2R1D4 no problem. Dose any one had same problem ? Thank you, -motoyoshi -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Support 2 Group / System Support Dept. CTC Technology

1 0

ETC Access Problem
by Blake Folgner 09 Nov '02

09 Nov '02

Hello, I'm having a problem accessing the etc folder on the netapp from my linux servers. Below is a copy of my exports file. /vol/vol0/home /vol/vol0/etc /vol/vol0 When I try to mount /vol/vol0 or /vol/vol0/etc on any of my linux servers I get permission denied. Even if I try to mount from the administrative host it gives me this error message. Dose anyone have any idea on what could cause this and how to fix it? This is an F760 filer running 6.1.2R1. Thanks for your help. Blake

1 0

RE: what are the columns in `snap list` ?
by Steve Evans 08 Nov '02

08 Nov '02

I assume you have date and name covered. %/used is the percentage of space the snapshot takes based on the amount of data. %/total is the percentage of space the snapshot takes based on total disk size. So let's say hourly.0 is using 100mb, you have 500mb of data, and your disk is 1000mb. %/used would be 20% (100mb/500mb) and %/total would be 10% (100mb/1000mb). The number on the left not in parentheses is the percentage of that snapshot and all the snapshots newer than it. The number in parentheses is the percentage of that snapshot only. So the number in parentheses could be all over the place. The number not in parentheses will slowly climb. You probably can't find it in the manual because it is in the Data Protection Guide, not the big sucker. Steve Evans SDSU Foundation (619) 594-0653 -----Original Message----- From: Jordan Share [mailto:iso9@jwiz.org] Sent: Friday, November 08, 2002 2:35 PM To: toasters(a)mathworks.com Subject: what are the columns in `snap list` ? I've poked around a bit, and I can't figure out what each column in the output of `snap list` means. Here's a snippet of snap list on my filer: %/used %/total date name ---------- ---------- ------------ -------- 26% ( 0%) 14% ( 0%) Nov 02 00:00 nightly.5 28% ( 3%) 16% ( 1%) Nov 01 00:00 nightly.6 30% ( 3%) 17% ( 1%) Oct 31 00:00 nightly.7 31% ( 3%) 18% ( 1%) Oct 30 00:00 nightly.8 33% ( 3%) 20% ( 1%) Oct 29 00:00 nightly.9 35% ( 5%) 22% ( 2%) Oct 28 00:00 weekly.1 36% ( 2%) 23% ( 1%) Oct 27 00:00 nightly.10 37% ( 2%) 23% ( 1%) Oct 26 00:00 nightly.11 38% ( 3%) 25% ( 1%) Oct 25 00:00 nightly.12 39% ( 3%) 26% ( 1%) Oct 24 00:00 nightly.13 41% ( 4%) 28% ( 2%) Oct 21 00:00 weekly.2 42% ( 4%) 29% ( 2%) Oct 14 00:00 weekly.3 44% ( 6%) 32% ( 3%) Oct 07 00:00 weekly.4 47% ( 9%) 36% ( 4%) Sep 30 00:00 weekly.5 48% ( 3%) 37% ( 1%) Sep 23 00:00 weekly.6 According to the MRTG graphs, I'm using 88% of my snap reserve at this point. How can I tell that from the snap list command? What does "%/used" and "%/total" mean? I'm sure this is very basic, and I would gladly RTFM, if only I knew where to look. Thanks, Jordan

1 0

what are the columns in `snap list` ?
by Jordan Share 08 Nov '02

08 Nov '02

I've poked around a bit, and I can't figure out what each column in the output of `snap list` means. Here's a snippet of snap list on my filer: %/used %/total date name ---------- ---------- ------------ -------- 26% ( 0%) 14% ( 0%) Nov 02 00:00 nightly.5 28% ( 3%) 16% ( 1%) Nov 01 00:00 nightly.6 30% ( 3%) 17% ( 1%) Oct 31 00:00 nightly.7 31% ( 3%) 18% ( 1%) Oct 30 00:00 nightly.8 33% ( 3%) 20% ( 1%) Oct 29 00:00 nightly.9 35% ( 5%) 22% ( 2%) Oct 28 00:00 weekly.1 36% ( 2%) 23% ( 1%) Oct 27 00:00 nightly.10 37% ( 2%) 23% ( 1%) Oct 26 00:00 nightly.11 38% ( 3%) 25% ( 1%) Oct 25 00:00 nightly.12 39% ( 3%) 26% ( 1%) Oct 24 00:00 nightly.13 41% ( 4%) 28% ( 2%) Oct 21 00:00 weekly.2 42% ( 4%) 29% ( 2%) Oct 14 00:00 weekly.3 44% ( 6%) 32% ( 3%) Oct 07 00:00 weekly.4 47% ( 9%) 36% ( 4%) Sep 30 00:00 weekly.5 48% ( 3%) 37% ( 1%) Sep 23 00:00 weekly.6 According to the MRTG graphs, I'm using 88% of my snap reserve at this point. How can I tell that from the snap list command? What does "%/used" and "%/total" mean? I'm sure this is very basic, and I would gladly RTFM, if only I knew where to look. Thanks, Jordan

1 0

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

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