toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

RE: upgrade to 6.1R1
by Traitel, Eyal 28 May '01

28 May '01

This is probably as of revert process which is a one time event. Please open a case and we will follow up to verify my answer. Eyal. ---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Filer Escalation Engineer CNA, MCSE, CSA, LCA, NetApp CA Network Appliance BV Hoofddorp, The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ---------------------------------------------------------------------- -----Original Message----- From: Reinoud Reynders [mailto:Reinoud.Reynders@uz.kuleuven.ac.be] Sent: Sun, May 27, 2001 22:53 To: Steven.Boyer(a)GD-WTS-CENTCOM.COM; toasters(a)mathworks.com Subject: Re: upgrade to 6.1R1 Dear Steven, Last week, i have upgraded my F740 (14 x 72 GB disks) from 5.3.7R1 to 6.1R1 without any problems. On this moment i have discovered just one problem: All my disks are in one volume (vol0). On my F820, (also running 6.1R1), I snapmirror the vol0 of the F740. After the ONTAP update from the F740, the sheduled snapmirror takes a lot of time (serveral houres, while with the version 5.3.7 just a few minutes). I think that it is the difference in disks and the extra parity check in 6.1 that causes the problem. My F740 has "old disks" (zone parity checking thanks 6.1R1) and my F820 has new disks with blok parity checking. Maybe he's confused in what is changed between de snapmirror. I will open a call by netapp for this tomorrow. Maybe it's just a stupid mistake of me, because snapmirror is new for me. Reinoud UZ-Leuven Belgium ----- Original Message ----- From: "Steven.Boyer Steven.Boyer" <Steven.Boyer(a)GD-WTS-CENTCOM.COM> To: <toasters(a)mathworks.com> Sent: Saturday, May 26, 2001 3:57 PM Subject: upgrade to 6.1R1 > I currently have three filers in a mixed environment, NT and SOLARIS, two at 1.4TB the other is 2.5TB. I plan on using them in a cascading mirror configuration. Does anyone have experience with upgrading to 6.1R1 and its operation? Since 6.1R1 is still in "First Customer Shipment Releases" I was wondering if anyone has experienced operational problems with 6.1R1?? > > > Steven > UNIX/NetApp Support > General Dynamics > >

1 0

upgrade to 6.1R1
by Steven.Boyer Steven.Boyer 27 May '01

27 May '01

I currently have three filers in a mixed environment, NT and SOLARIS, two at 1.4TB the other is 2.5TB. I plan on using them in a cascading mirror configuration. Does anyone have experience with upgrading to 6.1R1 and its operation? Since 6.1R1 is still in "First Customer Shipment Releases" I was wondering if anyone has experienced operational problems with 6.1R1?? Steven UNIX/NetApp Support General Dynamics

2 1

RE: Why is root not root?
by Knight, Graham 27 May '01

27 May '01

Probably because the file has an NT ACL that has been set so tightly that the root user cannot access it without taking ownership first, which cannot be done very easily from the command line. Setting this (hidden) option will make this type of problem a thing of the past: options cifs.nfs_root_ignore_acl on I used this extensively at my last position with very good results. Graham -----Original Message----- From: Chuck Ross [mailto:chuck.ross@signiant.com] Sent: Thursday, May 24, 2001 3:06 PM To: Net App List (E-mail) Subject: Why is root not root? Hi all, Why is root on a Unix admin host for a filer in a mixed env not really root? By that I mean why is it possible to create directories on the NetApp via a Cifs share that root has no access to? Chuck Ross SIGNIANT - A Nortel Networks Venture 1550 Carling Avenue, Suite 101 Ottawa, ON K1Z 8S8 email: Chuck.Ross(a)signiant.com tel: (613) 761-3605 fax: (613) 761-3629

2 1

RE: bogus LCD messages ...
by Haynes, Tom 26 May '01

26 May '01

At some point the disks were broken and there is a piece of code in some releases that does not properly update the status of the disk once a new one is inserted. This has since been fixed. The real fix is to upgrade to a newer version of OnTap, but a temporary fix is to reboot your filer. While the message is annoying, there is nothing wrong with your system. I have seen filers sit in this state for over a month. -----Original Message----- From: Waters, G Scott DSTI [SMTP:scott.waters@SBCCOM.APGEA.ARMY.MIL] Sent: Saturday, May 26, 2001 12:52 PM To: 'toasters(a)mathworks.com' Subject: bogus LCD messages ... Hi! I've been following this list for about a month now ... I heard about it while at NetApp Admin training. I needed to ask a question about some strange behavior coming from my 760 filer. My filer has some bogus "disk broken" messages flashing on it. The messages are there because some of the disks were inserted and removed ... but they were never brought online. The OS recognizes the disks and they have been added to a volume ... but the messages still continue to cycle on the LCD display. I hope I explained this thoroughly ... if you don't understand what I am saying or need more info, please let me know. Any ideas??

1 0

bogus LCD messages ...
by Waters, G Scott DSTI 26 May '01

26 May '01

Hi! I've been following this list for about a month now ... I heard about it while at NetApp Admin training. I needed to ask a question about some strange behavior coming from my 760 filer. My filer has some bogus "disk broken" messages flashing on it. The messages are there because some of the disks were inserted and removed ... but they were never brought online. The OS recognizes the disks and they have been added to a volume ... but the messages still continue to cycle on the LCD display. I hope I explained this thoroughly ... if you don't understand what I am saying or need more info, please let me know. Any ideas??

1 0

display _all_ options?
by Marion Hakanson 26 May '01

26 May '01

Folks, Is there some secret way to display _all_ available options and their settings? The documentation I've been able to find doesn't list all options which show up in the "options" command's output, and some options which _are_ documented don't always show up in that output either. For example, on both our new (v6.1R1) and old (v5.3.6R2) filers, cifs.save_case (which _is_ documented) won't show up in the complete listing, although you can query its value specifically. The recently discussed "cifs.nfs_root_ignore_acl" option doesn't seem show up in the show-all listing until you change it from "off" to "on" (and the latter doesn't even show up in a search of NOW). So how the heck can I be sure that my new filer has all the same option settings as my old one, if I can't even get a listing of all the old option settings? Suggestions are welcome.... Regards, -- Marion Hakanson <hakanson(a)cse.ogi.edu> CSE Computing Facilities

4 3

RE: upgrade to 6.1R1
by Sam Schorr 26 May '01

26 May '01

Steven, I have upgraded 4 of our F760's from 5.3.7 to 6.1R1. These 4 have 8 shelves of 18 gb drives in 2 volumes each (1 online, 1 snapmirror). The only issue is that older disks are VERY sensitive under 6.1. There is a specific reference to possible problems spinning up older drives in the docs for 6.1 - definitely read it. We had a number of disks refuse to spin up after the disk firmware upgrade step - almost lost a volume. Be prepared to power cycle the entire filer and disk shelves - this helped us get past a multi-disk failure that almost lost a volume. We ended up with a couple of drives in a broken state, but sparing took care of those. Also, there are annoying messages about configuration issues that do not show under earlier versions. In our case, 6.1 complains about the placement of our gigE NICs in certain slots. We've known about this "issue" for some time, but did not choose to take downtime to optimize it. Haven't figured out how to shut them up yet. --sam -----Original Message----- From: Steven.Boyer Steven.Boyer [mailto:Steven.Boyer@GD-WTS-CENTCOM.COM] Sent: Saturday, May 26, 2001 6:57 AM To: toasters(a)mathworks.com Subject: upgrade to 6.1R1 I currently have three filers in a mixed environment, NT and SOLARIS, two at 1.4TB the other is 2.5TB. I plan on using them in a cascading mirror configuration. Does anyone have experience with upgrading to 6.1R1 and its operation? Since 6.1R1 is still in "First Customer Shipment Releases" I was wondering if anyone has experienced operational problems with 6.1R1?? Steven UNIX/NetApp Support General Dynamics

1 0

None
by Steven.Boyer Steven.Boyer 26 May '01

26 May '01

We are looking to put Sybase data on a filer. We have several servers running different versions of Sybase, but only wish to put the data on the filer leaving the engine on the server. Has anyone been successful with such a configuration? -- Steven N. Boyer UNIX/NT/NetApp Support General Dynamics --

1 0

incremental ndmpcopy doesn't work
by Reinoud Reynders 25 May '01

25 May '01

Hello, I try to copy 150 GB from F740:vol0 to F820:vol1. The level0 frma ndmpcopy works fine. No errors. When i start the level 1, i get the following error: DstFiler: mei 25 09:51:02 [ndmpd:0]: RESTORE IS ABORTED mei 25 09:51:02 [ndmpd:0]: DstFiler just halted. mei 25 09:51:02 [ndmpd:0]: Reason: ndmp_data_halted_internal_error : Dump aborted I have also used the level i, but the same result: 1 time ok, incremental no go. The filers run both 6.1R1 Have someone a good idea? Reinoud Reynders UZ Kuleuven Herestraat 49 B- 3000 Leuven Belgium The complete log-file: S:\Informatiesystemen\nas>ndmpcopy toaster1:/vol/vol0/groepen/WebTeam mixer1:/vol/vol1/groepen/WebTeam -sa root:XXX -da root:XXX -level 1 setting everything to version 3 mei 25 09:45:38 [ndmpd:0]: Now waiting for source and destination to finish. SrcFiler: mei 25 09:45:39 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:45:39 [ndmpd:0]: creating "/vol/vol0/../snapshot_for_backup. 19" snapshot. SrcFiler: mei 25 09:46:01 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:46:01 [ndmpd:0]: Using subtree dump SrcFiler: mei 25 09:46:49 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:46:49 [ndmpd:0]: Date of this level 1 dump: Fri May 25 09:44 :58 2001. SrcFiler: mei 25 09:46:49 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:46:49 [ndmpd:0]: Date of last level 0 dump: Fri May 25 09:35 :38 2001. SrcFiler: mei 25 09:46:49 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:46:49 [ndmpd:0]: Dumping /vol/vol0/groepen/WebTeam to NDMP c onnection SrcFiler: mei 25 09:46:49 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:46:49 [ndmpd:0]: mapping (Pass I)[regular files] SrcFiler: mei 25 09:46:49 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:46:49 [ndmpd:0]: mapping (Pass II)[directories] SrcFiler: mei 25 09:50:23 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:50:23 [ndmpd:0]: estimated 12 KB. SrcFiler: mei 25 09:50:23 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:50:23 [ndmpd:0]: dumping (Pass III) [directories] DstFiler: mei 25 09:50:45 [ndmpd:0]: RESTORE: DstFiler: mei 25 09:50:45 [ndmpd:0]: Fri May 25 09:50:05 2001: Begin incremental restore SrcFiler: mei 25 09:50:59 [ndmpd:0]: DUMP: SrcFiler: mei 25 09:50:59 [ndmpd:0]: dumping (Pass IV) [regular files] DstFiler: mei 25 09:51:02 [ndmpd:0]: RESTORE: DstFiler: mei 25 09:51:02 [ndmpd:0]: Cannot run an incremental backup because th e previous restore did not complete. DstFiler: mei 25 09:51:02 [ndmpd:0]: RESTORE: DstFiler: mei 25 09:51:02 [ndmpd:0]: RESTORE IS ABORTED mei 25 09:51:02 [ndmpd:0]: DstFiler just halted. mei 25 09:51:02 [ndmpd:0]: Reason: ndmp_data_halted_internal_error : Dump aborte d mei 25 09:51:02 [ndmpd:0]: jndmpcopy finished

4 5

RE: Locking of Files and server clusters
by Basiji, Maryam 25 May '01

25 May '01

Just saw Lance's response. Lance elaborates on how to implement the solution that is discussed in the paper I just sent over. Thanks, Maryam -----Original Message----- From: White, Lance [mailto:Lance.White@netapp.com] Sent: Friday, May 25, 2001 8:16 AM To: 'Morgan, Joshua'; 'toasters(a)mathworks.com' Subject: RE: Locking of Files and server clusters One of the steps required to ensure proper failover of SQL Server via Legato Cluster is the creation of a Resource Group (RG)connecting the application to the two nodes. The RG must include a script that gets executed as one of the first steps in bringing up the RG. The script was designed to be a workaround for the filer's normally necessary CIFS file-locking behavior. When an Legato Cluster node first fails, as far as the filer is concerned, the session between the filer and that node is still alive (the disconnect could be temporary). Because of this, it initially maintains the file locks originally established for that session. Without our script, these locks would prevent the other "takeover" node from accessing the required files during takeover. However, when our script is implemented, the file locks are terminated and the "takeover" node can access the files as necessary. In our case, the files the "takeover" node needs access to are the SQL Server database data and! log files. If the "takeover" node does not have access to these files, once the takeover is completed and the SQL Server is done recovering, the databases on the filer are declared "suspect". Following is the generic syntax for the script that must reside on each node: rsh filer_name -l cluster_admin_name cifs terminate -t 0 failed_node_name You can pass the name of the failed node via a &ft' environment variable (refer to the LCE docs for details), or you can create a nested if...then...else loop to determine which node you are starting up on, and how to terminate the CIFS session on the Filer. An example would be: if &ft'currentnode == 'failednode' then rsh Filer -l ClusterAdmin cifs terminate -t 0 failednode else rsh Filer -l ClusterAdmin cifs terminate -t 0 othernode end; Likely will be a little more coding than this, but you get the drift. Lance White Systems Engineer Network Appliance -----Original Message----- From: Morgan, Joshua [mailto:JMorgan@Trivergent.com] Sent: Friday, May 25, 2001 7:29 AM To: 'toasters(a)mathworks.com' Subject: Locking of Files and server clusters Here is the Scenario: We have SQL7 Server running with its Databases on an F760 We are using Legato Clustering Software If the main SQL Server dies and the cluster software tries to bring up the backup server, we get a message saying that the Database files are still locked by the downed server. Does anyone know of a way to script unlocking the files? We can manually do it through server manager but that is no good for Disater Recovery. Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

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