toasters

toasters@lists.teaparty.net

13514 discussions

Solaris Jumpstart against a filer..
by kevin graham 15 Mar '02

15 Mar '02

Getting entirely too excited about tftp.server, I've convererted a rather hefty Jumpstart setup over to using dhcp and doing tftp/root nfs/install nfs all off the filer. Its working beautifully, and just generally rocks. The one problem I'm having though is going booting from a snapmirrored volume. The client is always denied write access via mount options, so write operations always fail. .... However, when the volume is in ro snapmirrored state, the boot will hang after physical device probes. If I break the mirror, things work perfectly (w/o changes export options, etc). I was going to take this up w/ Sun and did in further myself, but I thought I'd run it by the list to see if anyone knew how filesystem semantics change when a volume is snapmirrored. ..kg..

2 2

Is the "New Bug Alerts Profiler" working?
by Chris Thompson 15 Mar '02

15 Mar '02

Has anyone received an alert yet from this new mechanism, which has replaced the old weekly New Bugs mailing list (which certainly did stop after 25 February as announced)? I set up a fairly inclusive profile (with the intention of pruning it a bit later if necessary), but have received absolutely nothing, and I'm getting a little suspicious ... Chris Thompson Email: cet1(a)cam.ac.uk

1 0

RE: SQL I/O error
by Lella Bennett 14 Mar '02

14 Mar '02

We've seen it quite a bit, actually. In fact, this error is the reason we ended up removing our production databases from netapp filers. We've gone round and round with both NetApp and Microsoft on this issue and the bottom line is this: this error is due to the fact that the SQL traffic is going through the TCP/IP stack. Evidently, there is some latency that SQL server experiences while trying to communicate with the data file and the SQL server thinks that it's lost the connection and throws this error, marks the database suspect, etc... The other reason why this error may occur is that you've reached the maximum number of threads available. If this is the case, you will see an error in the NT event log referring to this. You can increase the number of available threads using a reg hack. If it's not caused by the threads issue, then I can't help ya. Like I said we experienced A LOT of pain due to this error and never could find a solution to it. Lella Bennett Systems Engineer NAREX Inc. 303.526.4000 ext 714 303.526.5130 fax 720.333.8175 cell www.narex.com -----Original Message----- From: Maglinger, Paul [mailto:PMAGLINGER@scvl.com] Sent: Thursday, March 14, 2002 3:55 PM To: 'NetApps list server' Subject: SQL I/O error Anyone seen an SQL Server Error Log message saying : I/O error 59(An unexpected network error occurred.) detected during read of BUF pointer = 0x14685900, page ptr = 0x64c78000, pageid = (0x1:0x378), dbid = 7, status = 0x801, file = e:\sqldevices\dynamics\dyn\gpsdyn1dat.mdf.. where the e drive is mapped to our 740 filer running 6.1.1R2P1. We were looking at sysstat and CPU was at 95-100%, cache age fell from 35 to 0. Paul Maglinger, A+, CA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com

1 0

SQL I/O error
by Maglinger, Paul 14 Mar '02

14 Mar '02

Anyone seen an SQL Server Error Log message saying : I/O error 59(An unexpected network error occurred.) detected during read of BUF pointer = 0x14685900, page ptr = 0x64c78000, pageid = (0x1:0x378), dbid = 7, status = 0x801, file = e:\sqldevices\dynamics\dyn\gpsdyn1dat.mdf.. where the e drive is mapped to our 740 filer running 6.1.1R2P1. We were looking at sysstat and CPU was at 95-100%, cache age fell from 35 to 0. Paul Maglinger, A+, CA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com

1 0

ndmp incremental did full
by neil lehrer 14 Mar '02

14 Mar '02

hi, my ndmp incremental backup did a full backup. this was on the day after i converted the homedir qtree from unix style to ntfs and wrote acls for every dir and file. would this have caused dump to backup everything? ontap 6.1.1r2p1d17 --

2 1

Adding memory to NetApp 740
by Maglinger, Paul 14 Mar '02

14 Mar '02

Has anyone ever tried adding more memory to a 740? We have 512MB in ours now, but would like to increase it to 1GB. Remember, you are unique... just like everyone else! Paul Maglinger, A+, CA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com

1 0

RE: SYSTEM_ID?
by Reger, Brad 13 Mar '02

13 Mar '02

[I've added a few notes on F85 and F87 to Guy's text below.] Guy Harris wrote: On Fri, Mar 08, 2002 at 02:46:25PM -0800, Jay Soffian wrote: > - Where does DOT grab the SYSTEM_ID from? The NVRAM card? The > motherboard? There are, for various historical reasons, several different system identification numbers for NetApp systems. I will give details on all of them, but will assume that by "SYSTEM_ID" you mean what is reported as "SYSTEM_ID=XXX" in autosupport mail; that comes from the NVRAM card. The original one, which is what is reported as "SYSTEM_ID=XXX" in autosupport mail, comes, on any NetApp system with an NVRAM card, *purely* from the NVRAM card - *none* of it comes from the motherboard or the chassis. On NetApp systems *without* NVRAM cards - i.e., C1100 and C1105 NetCache appliances - the "SYSTEM_ID" value is generated from the system serial number. That is not the case on any other platforms. That serial number, obviously, is not guaranteed to remain the same throughout the life of the system, as the NVRAM card can be replaced if it fails. With the F7xx/C7xx series, a serial number was put on the motherboard. Unfortunately, that's subject to change over the life of the system as well, as the motherboard is also replaceable. The C1100 and C1105 also have a serial "number" on the motherboard (I put "number" in quotes as it's not numeric - it includes letters); however, as the only replaceable unit on a C1100 or C1105 is the entire system, that number won't change for a system. (That's the number used to generate the "SYSTEM_ID" value.) The F85 and F87 do not have motherboard serial numbers that are reported. The motherboard serial number shows up in "sysconfig -v" output under "slot 0: System Board" as "Serial Number" on those platforms, at least in ONTAP 6.0/6.1 and NetCache 5.0/5.1/5.2 (I haven't checked what earlier releases do). With the F8xx/C3xxx/C6xxx series, a serial number was also put on the chassis. If you replace the chassis, you've replaced the system, so that number doesn't change over the life of the system. (Those machines also have a motherboard serial number.) On the C1100/C1105, I no longer remember whether separate motherboard and system serial numbers exist (not that it matters in the grander scheme of things, given that the motherboard isn't replaceable). The F85 and F87 have system serial numbers that are actually stored on the motherboard. If you swap motherboards on an F85, the system serial number will change so we provide a utility you can use to set it back to the sticker that's on the back of the chassis. Note that this serial number is alphanumeric. We don't support motherboard swaps on F87 so no matter where the number is actually stored, it should always match the sticker on the back of the chassis. This is a numeric-only serial number. At least in ONTAP 6.1 and NetCache 5.0/5.1/5.2, if a system has a chassis (system) serial number, it'll be reported by "sysconfig" (with or without "-v") as "System Serial Number". In autosupport mail in ONTAP 6.0/6.1 and NetCache 5.0/5.1/5.2: on systems with a chassis serial number, that number will be reported after the ===== SYSTEM SERIAL NUMBER ===== line as system serial number = XXX on systems *without* a chassis serial number, but with an "/etc/serialnum" file, the text in the first line of that file will be reported after the ===== SYSTEM SERIAL NUMBER ===== line as system serial number = XXX on systems with neither a chassis serial number nor an "/etc/serialnum" file, there will be no ===== SYSTEM SERIAL NUMBER ===== or system serial number = XXX line in the autosupport mail. ("/etc/serialnum" will *not* override the chassis serial number.) > - Is the SYSTEM_ID burned electronically into the system at NetApp, or > can it be reset in the field? The NVRAM serial number is burned electronically into the NVRAM card, and isn't reset in the field. > - Are the duplicate SYSTEM_ID's an accident? Yes. It's not supposed to happen.

1 0

SYSTEM_ID?
by Jay Soffian 13 Mar '02

13 Mar '02

We've got a situation where our company (Loudcloud, Inc.) has a filer reporting the same SYSTEM_ID as a filer from another company (Toshiba). Recently, Toshiba's filer threw a disk and sent in an autosupport mail. Netapp was kind enough to open a ticket, and assign it to Loudcloud, Inc. Oops. Apparently, whatever parses the autosupport mail at NetApp uses the SYSTEM_ID to map the NetApp to an account (service contract). So, my questions are: - Where does DOT grab the SYSTEM_ID from? The NVRAM card? The motherboard? - Is the SYSTEM_ID burned electronically into the system at NetApp, or can it be reset in the field? - Are the duplicate SYSTEM_ID's an accident? Thanks. j. -- Jay Soffian System Administrator 408 744 7584 Loudcloud, Inc.

3 3

How do I know if ACLs have been set on a file?
by Öberg Mats 12 Mar '02

12 Mar '02

Hi, I have kind of a problem on one of our filers, we have a directory structure that consists of around 500000 directories. We run this filer in mixed mode, which means that a number of directories and files have NT-acls and others have unix-rights. Now, how can I find out what files/directories have ACL-s set? I know I could use the SecureShare-Tab from the Nt-side, but I don't think I will live for another 100years, so is there another way? ---- Mats

2 1

Re: Use for bad drives
by ScottUCE＠aol.com 12 Mar '02

12 Mar '02

Hello, John: There is a possibility that your "expired" NetApp drives can be repaired. Go to: http://www.seagate.com/support/service/warranty_validation.html Surprisingly, some NetApp disk drives -- but not all -- can actually be returned by the end user directly to Seagate for warranty repair! To extract the drive from the NetApp cannister, you simply have to remove the four Phillips head screws on top and gently slide it out. (If you don't get lucky on the Seagate warranty, we'd be happy to quote you an inexpensive replacement drive!) Scott Fischmann Union Computer Exchange, Inc. 6233 Idylwood Lane Minneapolis, MN 55436 Phone: 952 935 7282 FAX: 952 935 5056 scott(a)unioncomputer.com In a message dated 3/8/2002 4:10:04 PM Central Standard Time, jcoke(a)ibeam.com writes: > I have a couple of expired 18GB FC drives and am wondering what to do with > the bodies. I do not want to throw them away because electronics are not > good for the environment. Does NetApp take them back for "recycling." I > don't really care about getting any money for them though I would like a > prepaid shipping container :-) > > John Coke > Information Security Specialist, Senior Hostmaster - RHCE, CCNA > Williams Communications > ph: 405.717.4895 > cell: 405.209.8519 > PGP fingerprint: 272F C31D 82C5 2C23 531F 65FF F56E 3951 C3B9 DB51 > PGP key ID 0xC3B9DB51 (pgp.mit.edu) > For your safety, this email has been encoded in double ROT13. > >

3 2

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