toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

ufsrestore
by chris＠cecil.muscat.com 30 Jun '99

30 Jun '99

Yesterday I dumped a load of data from our filer to a DLT7000 using: dump 0lfbn nrst0a 63 spong / then typing the directories to backup. Tape started rolling and after dumping the right amount of data stopped. Took the tape down to a 3rd party to do some benchmarking on our data and tried to restore it on a solaris 2.6 box but whatever we tried we couldn't get the data off. At one point we managed to get a directory structure but no files off. As far as I can remember we decided that the correct options were: ufsrestore -xfb /dev/rmt/1u 126 does that seem plausible? I'm now a little concerned that I wouldn't be able to restore my data via a sun box should the worst happen. -- Chris Good - Muscat Ltd. The Westbrook Centre, Milton Rd, Cambridge UK Phone: 01223 715006 Mobile: 07801 788997 http://www.muscat.com

1 0

Re: Disk Controller Failures
by Brian Tao 30 Jun '99

30 Jun '99

On Mon, 28 Jun 1999, Shaun T. Erickson wrote: > > My experience with NetApp has not been very good, yet I know that > many others have few if any troubles with them. While it didn't > leave me with a particularly good first impression, I'm hoping that > this F740 will meet our needs and improve our experience with > NetApp. We have a couple of clustered F740's in pre-production testing, and immediately after reading your original message about FC-AL controller failure, I found this on one of them: Sun Jun 20 01:00:02 EDT [nfs3: raid_scrub_admin]: Beginning disk scrubbing... Sun Jun 20 01:18:50 EDT [nfs3: isp2100_timeout]: 0a.2 (0xfffffc0000abf258,0x28:00155d88:0040,0/0,1189063/0/0,9156358/0): command timeout, aborting request Sun Jun 20 01:18:55 EDT [nfs3: isp2100_timeout]: 0a.4 (0xfffffc0000b8a118,0x28:00155dc8:0040,0/0,1186670/0/0,9156358/0): command timeout, aborting request Sun Jun 20 01:19:00 EDT [nfs3: isp2100_timeout]: 0a.5 (0xfffffc0000aea4f8,0x2a:0000a3f8:0008,0/0,2129956/0/0,9156358/0): command timeout, aborting request Sun Jun 20 01:19:06 EDT [nfs3: isp2100_timeout]: 0a.6 (0xfffffc0000adf3d8,0x28:0000a3f0:0008,0/0,2131151/0/0,9156358/0): command timeout, aborting request Sun Jun 20 01:19:14 EDT [nfs3: isp2100_timeout]: Resetting ISP2100 in slot 0a Sun Jun 20 05:34:04 GMT [nfs3: cf_main]: Cluster monitor: takeover of partner enabled Sun Jun 20 05:34:08 GMT [nfs3: rc]: de_main: e0 : Link up. Sun Jun 20 01:34:08 EDT [nfs3: rc]: saving 165M to /etc/crash/core.0.nz ("WAFL hung.") Sun Jun 20 01:34:34 EDT [nfs3: rc]: relog syslog Sun Jun 20 01:19:14 EDT [nfs3: isp2100_timeout]: Resetting ISP2100 in slot 0a Sun Jun 20 01:34:34 EDT [nfs3: rc]: NetApp Release 5.2.2 boot complete. Last disk update written at Sun Jun 20 01:00:07 EDT 1999 I then tried forcing a disk failure to see if my disk reconstruction would produce the same results yours did. It did, except mine never went beyond 4%. It didn't crash either... it just sort of stayed "stuck". I was able to force a cluster takeover from the other filer, and it continued the reconstruction, but something else messed up which caused the takeover filer not to assume the IP address of it's twin: Tue Jun 29 22:16:49 EDT [nfs3: raid_disk_admin]: Unload of disk 0a.5 (S/N LK95551800002941HH3U) has completed successfully. Tue Jun 29 22:17:10 EDT [nfs3: rshd_0]: Option raid.reconstruct_speed changed on one cluster node Tue Jun 29 22:21:46 EDT [nfs3: isp2100_timeout]: 0a.3 (0xfffffc0000b514b8,0x28:00155cc0:0040,0/0,52562/0/0,521771/0): command timeout, aborting request Tue Jun 29 22:21:51 EDT [nfs3: isp2100_timeout]: 0a.4 (0xfffffc0000b49ad8,0x28:00155c40:0040,1/0,28029/0/0,521771/0): command timeout, aborting request Tue Jun 29 22:21:56 EDT [nfs3: isp2100_timeout]: 0a.6 (0xfffffc0000b50618,0x28:00155cc0:0040,0/0,193448/0/0,521771/0): command timeout, aborting request Tue Jun 29 22:22:04 EDT [nfs3: isp2100_timeout]: Resetting ISP2100 in slot 0a And then on the partner filer: Tue Jun 29 22:27:49 EDT [nfs4: rc]: Cluster monitor: takeover initiated by operator Tue Jun 29 22:27:49 EDT [nfs4: cf_main]: Cluster monitor: UP --> TAKEOVER Tue Jun 29 22:27:49 EDT [nfs4: cf_takeover]: Cluster monitor: takeover started Tue Jun 29 22:27:50 EDT [nfs4: de0]: de_main: e3 : Link down. Check cable. Tue Jun 29 22:28:02 EDT [nfs4: disk_admin]: Resetting all devices on ISP2100 in slot 1 Tue Jun 29 22:28:09 EDT [nfs4: raid_disk_admin]: Label write on 1.5 (S/N LK95551800002941HH3U) failed. Tue Jun 29 22:28:09 EDT [nfs4: raid_disk_admin]: One disk is missing from volume partner:vol0, RAID group 0. A "hot spare" disk is available and the missing disk will be reconstructed on the spare disk. Tue Jun 29 22:28:10 EDT [nfs3/nfs4: cf_takeover]: ifconfig: 'e0' cannot be configured: no partner. Tue Jun 29 22:28:10 EDT [nfs3/nfs4: cf_takeover]: relog syslog Tue Jun 29 22:21:56 EDT [nfs3: isp2100_timeout]: 0a.6 (0xfffffc0000b50618,0x28:00155cc0:0040,0/0,193448/0/0,521771/0): Tue Jun 29 22:28:10 EDT [nfs3/nfs4: cf_takeover]: relog syslog Tue Jun 29 22:22:04 EDT [nfs3: isp2100_timeout]: Resetting ISP2100 in slot 0a Tue Jun 29 22:28:10 EDT [nfs4: cf_takeover]: WARNING: 1 error detected during network takeover processing Tue Jun 29 22:28:10 EDT [nfs4: cf_takeover]: WARNING: Some network clients may not be able to access the cluster during takeover Tue Jun 29 22:28:10 EDT [nfs4: cf_takeover]: Cluster monitor: takeover during ifconfig_2 failed; takeover continuing... Tue Jun 29 22:28:10 EDT [nfs4: cf_takeover]: Cluster monitor: takeover completed Anyway, this sounds and tastes like a FibreChannel controller failure too. -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

1 0

Re: Disk Controller Failures
by Brian Tao 30 Jun '99

30 Jun '99

On Sun, 27 Jun 1999 sirbruce(a)ix.netcom.com wrote: > > When I think about all the pieces of hardware and software that have > to work correctly just for a system to boot, let alone transmit this > message over a modem out to the world, I am sometimes amazed any of > it works at all. Sadly, most customers do not share this sense of wonder, perhaps precisely because it is an "appliance" that is supposed to "just work" like your toaster or your telephone. Not that we haven't had our problems with filers, but for the most part, Netapp maintenance is effortless, amazing considering the amount of stuff that has to happen in behind the scenes. -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

1 0

RE: Help with Network Appliance configuration ???
by Benn, Paul 29 Jun '99

29 Jun '99

Sr. Alexandre, You appear to have the tape library connected to the wrong SCSI bus (the card in slot 9). It should be connected to the onboard SCSI which is bus 0. Boa Sorte, Paul Benn Network Appliance -----Original Message----- From: Alexandre Gomes (r7043c) [mailto:r7043c@email.sps.mot.com] Sent: Tuesday, June 29, 1999 5:53 AM To: lista de discussao Subject: Help with Network Appliance configuration ??? Hi, I'm installing budtool( version 4.5) on a Solaris machine to operate a jukebox robotics connected to the Network Appliance ( F230) to do backups. On the installation he gaves the following message ( I will use NDMP protocol) : The spt and sjb drivers are capable of communicating with devices on any SCSI bus attached to this host. These drivers need to know on which bus the jukebox is attached. The first bus (e.g. esp0) is number 0, the second bus is number 1, and so on. Only a number between 0 and 7 will be accepted. Please enter the number of the SCSI bus for the jukebox: Could someone help me, How I discover the SCSI bus where my jukebox is connected on Net App.I execute the sysconfig on the NDMS and it says : paje> sysconfig -v NetApp Release 4.3.4: Wed Apr 22 16:25:06 PDT 1998 System ID: 0016785098 slot 0: System Board 90 MHz (NetApp System Board Ia rev-b) Firmware release: 1.9_i Memory Size: 192 MB slot 0: SCSI Host Adapter 0 (QLogic ISP 1040B) Firmware Version 2.26 Clock Rate 40MHz. In-Band Enclosure Services 0 Swap Events, 0 Enclosure Events slot 0: Ethernet Controller e0 MAC Address: 00:a0:98:00:0d:59 (100tx) slot 6: NVRAM (NetApp NVRAM I) Revision: D2 Serial Number: 7882 Memory Size: 8 MB Battery 1 Status: 100% (3.26v) Battery 2 Status: 100% (3.24v) slot 9: Dual SCSI Host Adapter (NetApp SCSI Adapter II) SCSI Host Adapter 9a (Qlogic ISP 1040B) Firmware Version 2.26 Clock Rate 40MHz. 0: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) 1: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) 2: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) 3: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) 4: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) 5: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) 6: SEAGATE ST39173WC 4218 Size=8.3GB (17783240 blocks) In-Band Enclosure Services 0 Swap Events, 0 Enclosure Events SCSI Host Adapter 9b (Qlogic ISP 1040B) Firmware Version 2.26 Clock Rate 40MHz. 3: Quantum DLT4000 CD5A 4: Quantum DLT4000 CD5A In-Band Enclosure Services 0 Swap Events, 0 Enclosure Events Please, help to answers this question !!! Thanks, Alexandre Gomes

1 0

Quite nice; Cure Autism Now Foundation
by Philip Thomas 29 Jun '99

29 Jun '99

http://biz.yahoo.com/bw/990628/ca_network_3.html It's quite commendable of NetApp's "good citizen" gesture. ---philip thomas

1 0

administrivia
by fubar＠mathworks.com 29 Jun '99

29 Jun '99

FYI, posts made to the list between Sunday evening and just now (10am EDT) will not be appearing in the toasters archive. I seem to recall there being a few posts, but not many. This past weekend was spent moving our servers to our new office building. In the move a few changes were made, and a few things broken. :-) K.

1 0

Re: Disk Controller Failures
by sirbruce＠ix.netcom.com 27 Jun '99

27 Jun '99

On 06/25/99 12:50:17 you wrote: > >Hi there, > > We recently encountered a disk controller failure on one of our >data servers (not on our Netapp). The problem was that this failure was >not a complete failure of the drive itself, but rather the controller >started to >die slowly. (i.e. handles some request sometimes and other times who >knows?) >As a result, this caused our entire filesystem to become corrupt and we lost >some >of our data as a result. Although this filesystem was mirrored, this did >not help us >at all, as it was considered a logical error in the filesystem and not a >hardware problem. > > My question is that should this occur on a Netapps (this may even >apply to >any other Enterprise server) would it cause the entire filesystem to go >corrupt and >cause partial or complete data loss as in this case? I would have to say yes, it's *possible*, but the controller would have to fail in a very odd way; not simply not responding the some requests (that would be caught), but executing some and not others (but claiming it did) or misordering commands or something like that. I would think this kind of error would be very rare. Perhaps the controller you had is particularly prone to those sorts of errors; one advantage of Netapp is you're using controllers they themselves have partially designed and tested. Bruce

2 1

Re: Increasing "maxfiles" and its effect on performance
by sirbruce＠ix.netcom.com 26 Jun '99

26 Jun '99

On 06/25/99 16:40:20 you wrote: > >What affect will increasing the "maxfiles" have on the read/write >performance on a volume? We are currently running Data Ontap ver 5.2.2P1 on >a F740. Very little, unless you set it to an extremely high value that is far, far more than you need. (Like, I dunno, 1 billion?) Even then I doubt it would be very noticeable unless the filer were heavily loaded. If you are running out of files on the filer (which is not unusual if the default setting was conservative and you've added a lot of space), you shouldn't think twice about upping the maxfiles value. I would guess (one of the Netapp WAFL experts could correct me on this) that since maxfiles reserves some space in the filesystem for metdata, that slowly increasing maxfiles over time (rather than in large increases at once) might "fragment" the metadata file across the filesystem, thus hurting performance somewhat. But then I seem to recall that even when you increase maxfiles, this space is not necessarily allocated right away, so maybe it doesn't matter and they'll only grow in a fragmentary fashion anyway. (Fragmentation is not really much of a problem on Netapp's anyway and is only really noticeable on very large files.) Bruce

1 0

Increasing "maxfiles" and its effect on performance
by Mike Ball 25 Jun '99

25 Jun '99

What affect will increasing the "maxfiles" have on the read/write performance on a volume? We are currently running Data Ontap ver 5.2.2P1 on a F740.

1 0

Disk Controller Failures
by Mingway Huang 25 Jun '99

25 Jun '99

Hi there, We recently encountered a disk controller failure on one of our data servers (not on our Netapp). The problem was that this failure was not a complete failure of the drive itself, but rather the controller started to die slowly. (i.e. handles some request sometimes and other times who knows?) As a result, this caused our entire filesystem to become corrupt and we lost some of our data as a result. Although this filesystem was mirrored, this did not help us at all, as it was considered a logical error in the filesystem and not a hardware problem. My question is that should this occur on a Netapps (this may even apply to any other Enterprise server) would it cause the entire filesystem to go corrupt and cause partial or complete data loss as in this case? Mingway Huang Nortel Networks

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