toasters

toasters@lists.teaparty.net

13531 discussions

RE: disappearing disks
by Sam Schorr 23 Apr '02

23 Apr '02

We are running 6.1R1 and we have seen a frequent number of disks suddenly disappear without "failing" in the sense that the filer marks the disk as "failed". What we see is the disk is noticed as missing, there is a message to that effect in /etc/messages, but the disk does not show as failed in sysconfig -r nor does it show in sysconfig -d. If the disk is pulled and a new disk inserted, a "failed" message appears first, then the new disk is added as a spare. The original disk that went missing did have its data spared out. We have had to write our own monitoring scripts to pull disk counts from the MIB's so that this condition can be noticed right away. Netapp support says that this "never happens" but we have the /etc/messages files to show the problem. It may be fixed in 6.2? -----Original Message----- From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] Sent: Monday, April 22, 2002 6:50 AM To: toasters Subject: disappearing disks Fellow toasters; I have an F760 cluster running NetApp Release 6.1R1P1. In the past week, we have "lost" two disks on separate shelves. The disks seem to disappear from the filer and do not show up. All the disks are Seagate ST318203FC 18GB drives with firmware NA10. I've seen this happen before on spare disks, and the first disk we lost this week was a spare. Typically, the spare fails and just stops reporting; if you slip it into a different slot the disk reports as failed. No big deal, just a spare failing and the filer doesn't know what to do with it immediately. But yesterday, we lost a data disk; it actually didn't show up in the weekly cluster notification log that runs at midnight. Around 2pm we received a disk fail alert for the drive and a disk/shelf miscount error. While checking on this, I noticed a third disk, another spare, had "disappeared"; however, once the volume rebuild completed, this disk "reappeared." I was wondering if anyone else had seen similar behavior on their filers? Like I said, this is a cluster, and it's partner was still able to see the third disk that "disappeared", which leads me to believe I have an FC-AL adapter failing. All three disks have been on separate shelves, which also leads me away from suspecting an LRC (that would be too easy). Before I go tearing into the filer though, I wanted to see if anyone else had experience with this problem. Thanks, Geoff Hardin geoff.hardin(a)dalsemi.com "A one-question geek test: Seen on a California license plate on a VW Beetle: 'FEATURE'..." - Joshua D. Wachs

2 1

Remove
by masahiro sato 23 Apr '02

23 Apr '02

Pls remove, Thanks!!

1 0

Ms Exchange 2000 on Netapp
by Kumar, Rahul 23 Apr '02

23 Apr '02

Fellow toasters; I need help from you all in planning a deployment of Microsoft Exchange 2000 on netapp filer F820. Any help relating to this will be welcome. Regards Rahul

1 0

RE: disappearing disks
by Kumar, Rahul 23 Apr '02

23 Apr '02

Fellow toasters; I need help from you all in planning a deployment of Microsoft Exchange 2000 on netapp filer F820. Any help relating to this will be welcome. Regards Rahul

1 0

Kick yourself off the list.
by Andrew Yee 23 Apr '02

23 Apr '02

-- Welcome to the toasters mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to <lists(a)mathworks.com> with the following command in the body of your email message: unsubscribe toasters If you ever need to get in contact with the owner of the list, (if you have trouble unsubscribing, or have questions about the list itself) send email to <owner-toasters(a)mathworks.com> . This is the general rule for most mailing lists when you need to contact a human. Here's the general information for the list you've subscribed to, in case you don't already have it: This is a totally unofficial mailing list for people who have Network Appliance toasters. It is not blessed by Network Appliance; it is, in true Internet spirit, a pure resource and grapevine for toaster administrators. There is an archive of postings to the list available on the web, which is updated regularly. You can find this, and browse the collected wisdom and net.witterings of other toaster admins and netapp chaps / chappesses at http://teaparty.mathworks.com:1999/toasters/ . It's searchable through http://teaparty.mathworks.com:1999/toasters/Search.html . It's presently administered by Kendall Libby, <fubar(a)mathworks.com>. He has two F330s and an F760, in case you were wondering. Disclaimy bit: I hate reading bounced email. I'll remove people who start to bounce.

1 0

Remove
by Rob C. Tien 22 Apr '02

22 Apr '02

Pls remove, Thanks!!

1 0

Sense data errors
by orh＠satec.es 22 Apr '02

22 Apr '02

Hi, Toasters We have one disk experiencing the following error: Mon Apr 22 11:57:14 CES [ispfc_main:error]: Disk 0a.33: op 0x28:00ab0ae8:0008 sector 0 recovered error - (1 5d, 0) Mon Apr 22 11:57:14 CES [scsi.cmd.checkCondition:error]: Device 0a.33: Check Condition: CDB 0x28:00ab0ae8:0008: Sense Data recovered error - (0x1 - 0x5d 0x0 0x43). Does anyone have any idea of what causes this error? Is it a harware error or just an error produced because a 'missmatch' in the data stored in the data and the parity disk? Usually, a media recovered error is reported by ontap as the following (usually, during disk scrub): Sun Apr 14 01:24:11 CES [correonfs2: ispfc_main:error]: Disk 8a.18: op 0x28:01c67000:0080 sector 29782108 medium error - Unrecovered read error (3 11, 0) Sun Apr 14 01:24:11 CES [correonfs2: ispfc_main:notice]: Disk 8a.18: sector 29782108 will be reassigned Sun Apr 14 01:24:11 CES [correonfs2: ispfc_main:error]: Medium err for disk 8a.18 (serial no. 3EK0PAKS00007216RQAM). Sun Apr 14 01:24:11 CES [correonfs2: scsi.cmd.checkCondition:error]: Device 8a.18: Check Condition: CDB 0x28:01c67000:0080: Sense Data medium error - Unrecovered read error (0x3 - 0x11 0x0 0xe4). Sun Apr 14 01:24:11 CES [correonfs2: ispfc_main:error]: Disk 8a.18: op 0x28:01c67058:0008 sector 29782108 medium error - Unrecovered read error (3 11, 0) Sun Apr 14 01:24:11 CES [correonfs2: ispfc_main:notice]: Disk 8a.18: sector 29782108 will be reassigned Sun Apr 14 01:24:11 CES [correonfs2: ispfc_main:error]: Medium err for disk 8a.18 (serial no. 3EK0PAKS00007216RQAM). Sun Apr 14 01:24:11 CES [correonfs2: scsi.cmd.checkCondition:error]: Device 8a.18: Check Condition: CDB 0x28:01c67058:0008: Sense Data medium error - Unrecovered read error (0x3 - 0x11 0x0 0xe4). Sun Apr 14 01:24:11 CES [correonfs2: raid_stripe_owner:info]: read error from disk 8a.18 (S/N 3EK0PAKS00007216RQAM) block 3722763 Sun Apr 14 01:24:11 CES [correonfs2: raid_stripe_owner:notice]: Rewriting bad block from parity on disk 8a.18, block #3722763 Sun Apr 14 01:24:12 CES [correonfs2: ispfc_main:notice]: Disk 8a.18: sector 29782108 was reassigned In the case below, it seems like sector 29782108 has been reassigned (by the internal hardware of the disk, I guess). In the first case (disk 0a.33), it has been recovered (I don't know how, it does not say anything about the parity disk). What is a 'Sense Data error'? How is it produced? Just willing to know a little more about how ontap manages its disks ... Thanks in advantage. Kind Regards. _____________________________________________________ Oscar Rodríguez Hernández Dpto. HelpDesk de Sistemas email: orh(a)satec.es SATEC/CONVEX Avda. Europa 34 A 28023 Aravaca MADRID (SPAIN) Tlf.: +34 91 708 90 00 | +34 91 211 03 00 - Extensión 319 Fax.: +34 91 708 90 90 | +34 91 211 03 90 http://www.satec.es ____________________________________________________

2 1

disappearing disks
by Geoff Hardin 22 Apr '02

22 Apr '02

Fellow toasters; I have an F760 cluster running NetApp Release 6.1R1P1. In the past week, we have "lost" two disks on separate shelves. The disks seem to disappear from the filer and do not show up. All the disks are Seagate ST318203FC 18GB drives with firmware NA10. I've seen this happen before on spare disks, and the first disk we lost this week was a spare. Typically, the spare fails and just stops reporting; if you slip it into a different slot the disk reports as failed. No big deal, just a spare failing and the filer doesn't know what to do with it immediately. But yesterday, we lost a data disk; it actually didn't show up in the weekly cluster notification log that runs at midnight. Around 2pm we received a disk fail alert for the drive and a disk/shelf miscount error. While checking on this, I noticed a third disk, another spare, had "disappeared"; however, once the volume rebuild completed, this disk "reappeared." I was wondering if anyone else had seen similar behavior on their filers? Like I said, this is a cluster, and it's partner was still able to see the third disk that "disappeared", which leads me to believe I have an FC-AL adapter failing. All three disks have been on separate shelves, which also leads me away from suspecting an LRC (that would be too easy). Before I go tearing into the filer though, I wanted to see if anyone else had experience with this problem. Thanks, Geoff Hardin geoff.hardin(a)dalsemi.com "A one-question geek test: Seen on a California license plate on a VW Beetle: 'FEATURE'..." - Joshua D. Wachs

1 0

Backup done on Remote Mirror Filer
by Alfred Lim 22 Apr '02

22 Apr '02

Hi Toasters, Just wondering, have anyone ever perform backup on Remote Mirror Filer? Using Vertias Netbackup NDMP or Legato Networker NDMP?? Or amyone have any experience deploying this configuration. :) Share ur experience Cheers, Alf

2 1

RE: Backup done on Remote Mirror Filer
by Chetrit Marc 22 Apr '02

22 Apr '02

Hi, We are using NETWORKER NDMP (NETWORKER UNIX 6.1.1, DATAONTAP 6.1.2R1) to backup mirrored volume, and it works with some limitation : Backup must be done on a snapshot for the mirrored volume, so you need to plan mirroring and backup to have an understandable backup process. Our configuration is made of 2 main filers mirroring one each other. By this backup method we get very good performance, and we need only one license (only one filer has a tape library connected). Restore process is a little bit complex, because you need to use relocate option of NETWORKER, but it works. There is also a limitation/bug in NETWORKER restore that make browse time difficult to use (in NDMP context). We choosed NDMP because it is the only way to reduce backup time. _____________________________________________ SIEMENS V D O Siemens VDO Automotive SAS A u t o m o t i v e BP 1149 1 Avenue Paul Ourliac 31036 Toulouse cedex 1 (France) Marc Chetrit OI ITS Back Office Phone : 33 (5) 6119 8421 Fax : 33 (5) 6119 2515 mailto:marc.chetrit@siemens.com <mailto:marc.chetrit@siemens.com> -----Original Message----- From: Alfred Lim [mailto:alfred@ptc.net] Sent: samedi 20 avril 2002 03:14 To: toasters(a)mathworks.com Subject: Backup done on Remote Mirror Filer Hi Toasters, Just wondering, have anyone ever perform backup on Remote Mirror Filer? Using Vertias Netbackup NDMP or Legato Networker NDMP?? Or amyone have any experience deploying this configuration. :) Share ur experience Cheers, Alf

1 0

Jump to page:

2026

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