toasters

toasters@lists.teaparty.net

3 participants
13513 discussions

Re: Read errors on a spare disk?
by sirbruce＠ix.netcom.com 12 Aug '97

12 Aug '97

On 08/11/97 14:37:07 you wrote: > >On Mon, 11 Aug 1997, Kenneth Whittaker wrote: >> >> Disk 9a.3 can only mean trouble in the future. I recommend getting >> disk 9a.3 out of your system, but before you pull a drive, call >> technical support. > > That's odd... as I mentioned, the error appeared on two of our >filers, both on the hour immediately following a spare disk >replacement. Are you saying the new drives I plugged in both happen >to be bad too? I've already got two sitting on my desk to be >returned, and I sure hope I don't need two more going back. I don't understand Ken's response either. He should be well aware that there is a bug on this, where most of the time a disk will report a Unit Attention error on the hourly check after being swapped in... I filed the bug myself a year or two ago. Bruce

3 3

Backing up multiple Netapps
by Brian Tao 12 Aug '97

12 Aug '97

What do people do for enterprise-wide Netapp backups? It's nice to plug in a big tape drive into the dedicated SCSI port on each filer, but management becomes a hassle, and the hardware itself gets pretty expensive. If you centralize everything to a backup server and do dumps over the network, what do you use to manage the scheduling and auditing of the tapes? Is there a way to get Amanda to work with a bunch of Netapps? Anyone using NDMP-based tools? -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

2 1

Read errors on a spare disk?
by Brian Tao 11 Aug '97

11 Aug '97

Why am I seeing problems with a disk that isn't even active? Does the Netapp do periodic media checks on the spare drives? I had just added this drive in a couple hours earlier that day, and I've only seen this one occurrence so far. Fri Aug 8 13:00:00 EDT [isp_main]: Disk 9a.3(0x004e6290): READ sector 0 unit attention (6 29, 0) Fri Aug 8 13:00:00 EDT [isp_main]: Disk 9a.3(0x004e6290): request succeeded after retry #1 RAID Disk DISK_ID# HA.SCSI# Used (MB/blks) Phys (MB/blks) --------- -------- -------- -------------- -------------- parity 5 9a.1 4000/8192000 4095/8388312 data 1 4 9a.2 4000/8192000 4095/8388312 data 2 0 9b.0 4000/8192000 4095/8388312 data 3 1 9b.1 4000/8192000 4095/8388312 data 4 2 9b.2 4000/8192000 4095/8388312 data 5 3 9b.3 4000/8192000 4095/8388312 data 6 8 9a.4 4000/8192000 4095/8388312 data 7 9 9a.0 4000/8192000 4095/8388312 data 8 6 9b.5 4000/8192000 4095/8388312 data 9 7 9b.4 4000/8192000 4095/8388312 spare 10 9a.3 0 4095/8388312 spare 11 9a.5 0 4095/8388312 -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

2 3

Re: Read errors on a spare disk?
by sthaug＠nethelp.no 11 Aug '97

11 Aug '97

> Why am I seeing problems with a disk that isn't even active? Does > the Netapp do periodic media checks on the spare drives? I had just > added this drive in a couple hours earlier that day, and I've only > seen this one occurrence so far. I heard rumors that NetApp was going to add disk scrubbing for spare disks in a later release. What release are you running? Steinar Haug, Nethelp consulting, sthaug(a)nethelp.no

3 2

Filer stops serving NFS over FDDI?
by alexei＠deepthroat.cimedia.com 09 Aug '97

09 Aug '97

I have a f540 which has (on more than one occasion) stopped serving NFS over its FDDI interface. At first this was because of the nfs over tcp bug. But I have had that turned off for a while. Tonight it occured again. Nothing in the logs. Clients over the ethernet side could get to the filer fine. The fddi interface was up. (while I should have spent more time debugging, I needed the filer back in action; I rebooted and all is well again) Has anyone seen anything like this before? My f540 has 24 4GB drives, 256MB read cache, 8MB nvram, fddi and ethernet. I run 4.0.1c (haven't had a chance to upgrade). Thanks. Alexei

1 0

Re: Quotas
by Dave Heiland 08 Aug '97

08 Aug '97

>I call a guaranteed space allocation a "reservation". Reservations are >possible, but they do impose more complexity and more processing >overhead. We've had little if any strong pressure for reservations. ... >Applying quotas to an arbitrary subtree is tricky... I agree with keeping things simple. If setting up reservations, or applying quotas to arbitrary trees adds to the complexity of the software too much relative to the number of people requiring it, then the current design of quotas is fine. >I don't know whether this level of detail in our design process is >interesting to people or not, but hopefully it helps explain why quotas >work they way they do. I'd have to say that knowing why things are designed the way they are make a big difference, and its not often that users get the reasons behind decisions that can seem arbitrary from the outside. -- Dave Heiland

1 0

Mixing narrow and wide drives...
by Brian Tao 08 Aug '97

08 Aug '97

Stupid question time... does an F230 allow mixing narrow and wide 4GB drives in one shelf? One drive on our F230 (which uses wide drives) was freaking out the rest of the system, and I replaced it with a spare from our F220 (which uses narrow drives). The F230 didn't like that at all. ;-) I was under the impression that you were allowed to mix narrow and wide drives on a wide bus (as long as the narrow drives were within ID 0 to 7). -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

1 0

Amanda and network appliance machines (fwd)
by Tom Yates 07 Aug '97

07 Aug '97

this one just cropped up on the AMANDA mailing list. any amanda-toaster experts have any light to shed? we use amanda, but not for the toasters. Tom Yates - Unix Chap - The Mathworks, Inc. - +1 (508) 647 7561 MAG#65061 DoD#0135 AMA#461546 1024/CFDFDE39 0C E7 46 60 BB 96 87 05 04 BD FB F8 BB 20 C1 8C "Microsoft (tm) is a single-sofa supplier" ---------- Forwarded message ---------- Date: Thu, 07 Aug 1997 15:24:24 -0400 From: Ernie Oporto <ernie_oporto(a)MENTORG.COM> To: amanda-users(a)cs.umd.edu Subject: Amanda and network appliance machines Resent-Date: Thu, 7 Aug 1997 15:24:41 -0400 (EDT) Resent-From: amanda-users(a)cs.umd.edu Has anyone attempted to do anything with AMANDA and Network Appliance's machines? They're one of the companies we were thinking of buying a server from, but without good AMANDA support, we would probably stick with Auspex. -Ernie -- http://www.geocities.com/SiliconValley/Park/9276 _____/ ____ / /Ernie "Shokk" Oporto-SysAdmin _____ ____ / \ __ / __ Mentor Graphics Corporation \______/ __ __ \______/ __ \___ __ \___

1 0

Quotas
by dheiland＠lucent.com 07 Aug '97

07 Aug '97

With 4.1c quotas have improved by allowing restrictions on users in a specific tree - which makes me wonder how people are using quotas. One use is clearly limiting space users can use to force them to use space wisely. A more important use seems to be restricting certain areas from growing too large and preventing other areas from running out of space. For instance, you don't want a user directory preventing incoming mail from being written. In this case, what could be useful in addition to an upper limit on directory sizes is having a guaranteed minimum space for a directory. For example, reserving 1 GB for incoming mail regardless of the constraints on other areas. This would add extra complexity and might not even be possible - has anyone else considered this to be possibly useful? Quotas also seem to be a bit confusing in that the /etc/quotas file defines all the quotas, and 'quota on' or 'quota resize' activates the quotas, but you have to create a quota directory via 'quota qtree'. This means you can't just add an existing directory to /etc/quotas and run quota off/on to enforce quotas on it, and that qtrees and entries in /etc/quotas can be out of sync. It seems more sensible just to have the /etc/quotas file and quota on/off/resize. Dave Heiland dheiland(a)lucent.com

3 2

Inconsistent drive ID labels
by Brian Tao 05 Aug '97

05 Aug '97

Does anyone else find the wording of syslog messages confusing? I almost had a small heart attack when I saw this after failing out a marginal drive, thinking that two drives had just died. "Disk 8" and "Data disk 7" are the same thing, and I wish the filer would use one or the either. Mon Aug 4 15:45:27 EDT [raid_disk_admin]: Unload of disk 8 has completed successfully. Mon Aug 4 15:45:27 EDT [raid_stripe_owner]: Read on data disk 7 failed, reverting to degraded mode. -- Brian Tao (BT300, taob(a)netcom.ca) "Though this be madness, yet there is method in't"

5 6

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