toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

avg rtt is okay but maximum is high
by Willeke, Jochen 15 Mar '07

15 Mar '07

Hi Toasters, we have a database on nfs space and i wonder about the output of nfs_hist. v3 read: 35280016 (blocking requests) - millisecond units 0 1 2 3 4 5 6 7 17347681 2028005 655821 757932 1061542 1463375 1943351 1721450 <16 <24 <32 <40 <48 <56 <64 UNUSED 6417253 1334072 338371 111465 43542 18991 10063 0 <128 <192 <256 <320 <384 <448 <512 UNUSED 20806 2364 1282 617 526 280 266 0 <1024 <1536 <2048 <2560 <3072 <3584 <4096 UNUSED 723 158 77 3 0 0 0 0 <8192 <12288 <16384 <20480 <24576 <28672 <32768 UNUSED 0 0 0 0 0 0 0 0 <65536 <98304 <131072 <163840 <196608 <229376 <262144 >262144 0 0 0 0 0 0 0 0 Is the amount of read-calls with a RTT greater than 7ms ok, or is it something i have to wonder about?? I mean, the calls between 7-16ms are about 18%. But on the other hand nfs_hist shows only the blocking requests so the percentage of total calls will be even less than 18%. Does my nfs_hist look like a healthy system or do i have a problem? Regards and thanks for every answer :D Jochen

2 4

Block vs Zoned checksum disks
by Ronan Mullally 14 Mar '07

14 Mar '07

Hi, I've got an old lab filer with a shelf of X231 disks. I've got my hands on a couple of extra 36GB disks to act as spares, but it turns out they're X225s rather than X231s - ie a 512 byte sector size rather than a 520 byte sector size. The /etc/qual_devices file lists the following: D NETAPP X225_ST336704FC NA42 512 D NETAPP X231_ST336704FC NA42 520 The two disks are obviously identical seagate drives, but AFAIR (I could be wrong, it's been a long day) I can't use a 512 byte drive in a volume of 520 byte drives. Is this correct? If so, is there any way around this? I can re-format the drives with a 520 byte sector size - and add an X225 line with a 520 byte sector size, would that do the trick? If not, is there any way of changing the disk label from X225 to X231? Thanks in advance, -Ronan

3 2

SnapDrive for Linux
by Holloway, Chris 14 Mar '07

14 Mar '07

All Can anyone help me with SnapDrive for Linux? I'm using CentOS 4.4 kernel 2.6.9-42.0.10, iSCSI initiator 4.0.3.0-4, latest Host Utilities Kit and latest SnapDrive for Linux. Filer is running ONTAP 7.2. I can connect to the filer with no problems and mount drives on my Linux server provided I don't use LVM. When I try to create LUNs using LVM I get a weird error. This is the command I'm using: [root@vader ~]# snapdrive storage create -fs /filerlun2 -dg netappdg2 -lun fas250:/vol/linuxlun/lun1 lun2 lun3 -lunsize 1g 0001-417 Command error: The following names are already in use: netappdg2. Please specify other names. There are absolutely no disk group names called this already: [root@vader ~]# lvscan ACTIVE '/dev/VolGroup00/LogVol00' [4.34 GB] inherit ACTIVE '/dev/VolGroup00/LogVol01' [512.00 MB] inherit I've used SnapDrive for HPUX before with no problems using LVM. I'm aware that CentOS isn't officially supported, but I was hoping it would work since RHEL is supported (and it's only a test environment anyway). Is there something I'm missing here? Thanks very much Chris -------------------------------------------------------- Christopher Holloway Consultant Professional Services Main: +44 (0)1423 519000 Direct: +44 (0)1423 519099 Fax: +44 (0)1423 519251 Mobile: DNS Arrow Nidderdale House Beckwith Knowle Harrogate HG3 1SA www.DNSarrow.co.uk Email Confidentiality Notice: This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. "DNS Arrow" means Digital Network Services (UK) Limited, a company registered in England. Company Registration Number 3952678. Registered Office: Squire, Sanders & Dempsey, Level 28 Tower 42, 25 Old Broad Street, London EC2N 1HQ, UK.

1 0

RE: Upgrading Data OnTap
by George, Andrew 12 Mar '07

12 Mar '07

Sorry...As I understand the documentation I've read I think disk firmware updates are always disruptive unless you don't do more that what parity allows (1 disk per RG in raid4 or 2 disks in raid_DP) or unless your on 7.(Forgot the version - 0 or 1)) or later and your upgrading firmware as part of a reboot (the background upgrade option) - I've been thinking of raising a case asking for an enhancement about that as I couldn't see a way to drop new firmware on a box and let the nondisruptive upgrade process spin down and spin up one disk at a time (which is what it does if it sees new firmware after a reboot) Happy to be proven I'm doing it wrong :) _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Leeds, Daniel Sent: Saturday, 10 March 2007 2:58 AM To: Nils Vogels; tmac Cc: toasters(a)mathworks.com Subject: RE: Upgrading Data OnTap on the fibre channel drive shelves it updates the firmware on both the a/b loop. if you run the shelf firmware updater on one side of the cluster you do not need to do it on the other side. it is also non disruptive and does not interfere with data access. on the SATA shelves it is disruptive, the download command will tell you if it is disruptive or not before you proceed. -- Daniel Leeds Senior Systems Administrator Edmunds.com -----Original Message----- From: owner-toasters(a)mathworks.com on behalf of Nils Vogels Sent: Fri 3/9/2007 12:45 AM To: tmac Cc: toasters(a)mathworks.com Subject: Re: Upgrading Data OnTap On 3/8/07, tmac <tmacmd(a)gmail.com> wrote: > Personally, I would: > > copy the 7.1.2_setup_x.exe file to the /etc/software directory on each filer. > > Then from the console of each filer: > > options raid.background_disk_fw_update.enable off > (turns off auto updating of disk firmware) > software install filename (the filename from above) > > While at it, get and extract the latest all.zip and all_fw.zip files > (disk and shelf FW) into the /etc dir on each filer. > > Optionally, with cluster still enabled, run > disk_fw_update > to update all disk firmware (lessens downtime at reboot) > usually only needed on one head. When complete, run on > other head to be sure. > storage download shelf > to update shelf firmware (lessens downtime at reboot) > usually only needed on one head. When complete, run on > other head to be sure. > options raid.background_disk_fw_update.enable on > (turns the auto updating of disk firmware back on) > I'm preparing to do a NDU 7.0 -> 7.1 and was wondering: When you do the storage download shelf on one head, will it update the firmware on both the A-loop and B-loop ? I would expect not, since one head is only connected to one loop in a plain cluster config. AFAIK, downloading shelf firmware takes a quiesce of a loop and a controller reboot, and my customer really would like to have a functional system during this NDU. Greets, Nils -- Simple guidelines to happiness: Work like you don't need the money, Love like your heart has never been broken and Dance like no one can see you. "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."

3 2

RE: Upgrading Data OnTap
by George, Andrew 10 Mar '07

10 Mar '07

Oops...sorry..thats right...Shelf firmware isn't disruptive for FC shelves from what I've seen My Mistake (answering emails while I'm doing a filer move) _____ From: Leeds, Daniel [mailto:dleeds@edmunds.com] Sent: Saturday, 10 March 2007 11:10 AM To: George, Andrew; Nils Vogels; tmac Cc: toasters(a)mathworks.com Subject: RE: Upgrading Data OnTap i think two things got merged in this one, i was responding to the guy asking about storage shelf download updates not individual disk updates. storage download shelf is non disruptive on FC loops but on SATA/ATA loops it is disruptive from my experience. -- Daniel Leeds Senior Systems Administrator Edmunds.com -----Original Message----- From: George, Andrew [mailto:georgea@anz.com] Sent: Fri 3/9/2007 4:08 PM To: Leeds, Daniel; Nils Vogels; tmac Cc: toasters(a)mathworks.com Subject: RE: Upgrading Data OnTap Sorry...As I understand the documentation I've read I think disk firmware updates are always disruptive unless you don't do more that what parity allows (1 disk per RG in raid4 or 2 disks in raid_DP) or unless your on 7.(Forgot the version - 0 or 1)) or later and your upgrading firmware as part of a reboot (the background upgrade option) - I've been thinking of raising a case asking for an enhancement about that as I couldn't see a way to drop new firmware on a box and let the nondisruptive upgrade process spin down and spin up one disk at a time (which is what it does if it sees new firmware after a reboot) Happy to be proven I'm doing it wrong :) _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Leeds, Daniel Sent: Saturday, 10 March 2007 2:58 AM To: Nils Vogels; tmac Cc: toasters(a)mathworks.com Subject: RE: Upgrading Data OnTap on the fibre channel drive shelves it updates the firmware on both the a/b loop. if you run the shelf firmware updater on one side of the cluster you do not need to do it on the other side. it is also non disruptive and does not interfere with data access. on the SATA shelves it is disruptive, the download command will tell you if it is disruptive or not before you proceed. -- Daniel Leeds Senior Systems Administrator Edmunds.com -----Original Message----- From: owner-toasters(a)mathworks.com on behalf of Nils Vogels Sent: Fri 3/9/2007 12:45 AM To: tmac Cc: toasters(a)mathworks.com Subject: Re: Upgrading Data OnTap On 3/8/07, tmac <tmacmd(a)gmail.com> wrote: > Personally, I would: > > copy the 7.1.2_setup_x.exe file to the /etc/software directory on each filer. > > Then from the console of each filer: > > options raid.background_disk_fw_update.enable off > (turns off auto updating of disk firmware) > software install filename (the filename from above) > > While at it, get and extract the latest all.zip and all_fw.zip files > (disk and shelf FW) into the /etc dir on each filer. > > Optionally, with cluster still enabled, run > disk_fw_update > to update all disk firmware (lessens downtime at reboot) > usually only needed on one head. When complete, run on > other head to be sure. > storage download shelf > to update shelf firmware (lessens downtime at reboot) > usually only needed on one head. When complete, run on > other head to be sure. > options raid.background_disk_fw_update.enable on > (turns the auto updating of disk firmware back on) > I'm preparing to do a NDU 7.0 -> 7.1 and was wondering: When you do the storage download shelf on one head, will it update the firmware on both the A-loop and B-loop ? I would expect not, since one head is only connected to one loop in a plain cluster config. AFAIK, downloading shelf firmware takes a quiesce of a loop and a controller reboot, and my customer really would like to have a functional system during this NDU. Greets, Nils -- Simple guidelines to happiness: Work like you don't need the money, Love like your heart has never been broken and Dance like no one can see you. "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication." "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."

1 0

Upgrading Data OnTap
by Brent Ellis 09 Mar '07

09 Mar '07

I would like to upgrade my filer from data ontap 7.1p1 to 7.1.2 and I just want to make sure I am doing it write. I plan on doing the following: 1. disable the cluster 2. mount the c$ share as a drive 3. run the 7.1.2 installer 4. reboot 5. repeat with the other cluster partner 6. enable the cluster. Does that sound right? It seems a little to easy to me Brent Ellis Computing Services Group Boston University 617-358-2486 interi(a)bu.edu cashelp(a)bu.edu

9 10

mounting snapshots
by Steven Mandrake 09 Mar '07

09 Mar '07

Hello, I am having the hardest time understanding fractional space reservations for volumes and lun space reservations. If I reduce fractional space reservations to a volume that contain luns, what happens to lun space reservations? Is there a way to throttle lun space reservations -- as far as I can tell it's just a check box in Filerview.... The main question I have is --- does setting fractional space reservation affect my ability to mount snapshots. I assume that mounting snapshots does not take any space since it's all read-only.... or am i wrong in assuming this? My assumption right now is that fractional space reserve is there if I ever need to mount a snapshot to be read/write --- am I dead wrong? Thanks, Steve

3 5

Re: autosupport stops functioning
by Davies,Matt 08 Mar '07

08 Mar '07

We had to reboot the filer after deleting the queued autosupports. Not a great solution, but it worked. Cheers Matt -----Original Message----- From: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com> To: Leeds, Daniel <dleeds(a)edmunds.com> CC: toasters(a)mathworks.com <toasters(a)mathworks.com> Sent: Thu Mar 08 18:58:34 2007 Subject: Re: autosupport stops functioning Hi there, Did you get a resolution to your problem? Looks like we got hit by the same bug. One of our filer (running 7.0.2) suddenly stopped working. Its partner works fine. One thing I noticed is this: On the filer where it stopped working: options autosupport.doit autosupport.doit WEEKLY_LOG On other filers where it works: options autosupport.doit autosupport.doit DONT Even if I change it to DONT, it doesn't seem to stick. Anyways I too have opened a case with Support to see what they advise. -G On 2/27/07, Leeds, Daniel <dleeds(a)edmunds.com> wrote: > > > > > fyi, > > netapp support is advising us to perform a software install of the same > release but without doing a download or reboot. ill post back the results > once i get clearance to muck with a production filer :) > > > -- > Daniel Leeds > Senior Systems Administrator > Edmunds.com > > > > -----Original Message----- > From: owner-toasters(a)mathworks.com on behalf of Leeds, Daniel > Sent: Tue 2/27/2007 6:32 AM > To: Kießl Walter; Oliver Bassett; toasters(a)mathworks.com > Subject: RE: autosupport stops functioning > > > it sounds like we have the same problem and i too cannot reboot this filer > because it houses at least 8 production oracle databases :( > > -- > Daniel Leeds > Senior Systems Administrator > Edmunds.com > > > > -----Original Message----- > From: Kießl Walter [mailto:kiessl@heidenhain.de] > Sent: Mon 2/26/2007 11:45 PM > To: Leeds, Daniel; Oliver Bassett; toasters(a)mathworks.com > Subject: AW: autosupport stops functioning > > Hi Daniel, > > I have the same problem with DOT 7.2.1. To me it seems that the autosupport > process has gone stuck. NetApp has no idea what the cause could be. They > asked me to reboot the filer, but as it is a productional database storage > provider I'm not able to boot it yet. > > Have you tried to boot the filer? Anything changed after rebooting? > > Regards > Walter > > ________________________________ > > Von: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com] Im Auftrag von Leeds, > Daniel > Gesendet: Dienstag, 27. Februar 2007 05:41 > An: Oliver Bassett; toasters(a)mathworks.com > Betreff: RE: autosupport stops functioning > > > > we are actually past 7.1.x on this filer > > > -- > Daniel Leeds > Senior Systems Administrator > Edmunds.com > > > > -----Original Message----- > From: Oliver Bassett > [mailto:Oliver.Bassett@infinity.co.nz] > Sent: Mon 2/26/2007 7:36 PM > To: Leeds, Daniel; toasters(a)mathworks.com > Subject: RE: autosupport stops functioning > > Did this start happening after an upgrade to ONTAP 7.0.5? > > > > They added throttling functionality to the autosupport options. > > > > Thanks > > > > Oliver Bassett > Senior Systems Engineer > > Infinity Solutions Ltd > P O Box 3323, Auckland > Ph: +64 9 921 8123, Mob: +64 21 574 994 > Fax: +64 9 309 4142 > www.infinitysolutions.co.nz > <http://www.infinitysolutions.co.nz> > > > > From: owner-toasters(a)mathworks.com > [mailto:owner-toasters@mathworks.com] > On Behalf Of Leeds, Daniel > Sent: Tuesday, 27 February 2007 3:37 p.m. > To: toasters(a)mathworks.com > Subject: autosupport stops functioning > > > > > > anyone else have this happen? > > suddenly one of our filers stops generating autosupport messages. both > autosupport.enable and autosupport.support.enable are on. if i generate > a test email with the autosupport.doit option nothing happens. not even > a failed message, the console just sits there as if i never generated > one. > > needless to say neither netapp or our email server gets anything from > this filer and nothing hits the console about generating any autosupport > emails. > > > The information contained in this email is privileged and confidential and > intended for the addressee only. If you are not the intended recipient, you > are asked to respect that confidentiality and not disclose, copy or make > use > of its contents. If received in error you are asked to destroy this email > and contact the sender immediately. Your assistance is appreciated. > > > > > > _____________________________________________________________ This e-mail (including all attachments) is confidential and may be privileged. It is for the exclusive use of the addressee only. If you are not the addressee, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately at help(a)generalatlantic.com <mailto:help@generalatlantic.com>. Thank You.

1 0

Dirty Parity
by Carl Howell 08 Mar '07

08 Mar '07

*This is my second attempt to send this to the list. If it shows up twice, I apologize. We had a situation last year in which one of the aggregates on our R100 suffered dirty parity in one of its raid groups which forced us to take the filer down for several hours while we ran WAFL_Check on that aggregate. Given this, I have a few questions: 1. What is the likelihood of getting dirty parity? I assume the likelihood goes up dramatically on a box like the R100 given that the weekly RAID scrubs seldom if ever complete. 2. If this had occurred on a cluster, could we take one node down to run the WAFL_Check, while the other node continues to serve data from the other aggregates? 3. How many of you have encountered something like this and decided to go with SyncMirror to protect against such a thing? Thanks, --Carl

3 4

RE: usermap problem
by Glenn Walker 07 Mar '07

07 Mar '07

No one is stating that you cannot map users with LDAP - however, if the user names are not alike between unix and windows is the key. Reading the ONTAP documentation, you must specify the windowsaccount attribute and the unixaccount attribute. So long as these attributes match, then you should map - if they do not match, then there is no way to map. To enable LDAP-based user-mapping, complete the following steps. 1 From the Data ONTAP command line, specify a value for the option ldap.usermap.attribute.windowsaccount. options ldap.usermap.attribute.windowsaccount account_name account_name is the user object attribute Data ONTAP will use for Windows account lookups. 2 Extend your LDAP schema to include the user object attribute you entered in Step 1. 3 From the Data ONTAP command line, specify a value for the option ldap.usermap.attribute.unixaccount. options ldap.usermap.attribute.unixaccount account_name account_name is the user object attribute Data ONTAP will use for UNIX account lookups. 4 Extend your LDAP schema to include the values you entered in Step 2 and Step 3. 5 Enter the following command: options ldap.usermap.enable on If you have a significant load on your LDAP server, you might want to improve performance by setting a separate search base or search base and scope for user-mapping, as described in the following section. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Åke Beckman Sent: Tuesday, March 06, 2007 4:50 AM To: toasters(a)mathworks.com Subject: RE: usermap problem It IS possible, as Tom states, to do the usermapping through ldap, it's been around for quite some time.. Check options cifs.trace_dc_connection to see if the connection to the ldap server is working. (Don't know if this is valid only for AD ldap services...?) Maybe the password for ldap access got screwed up after the upgrade? options ldap.name user_name options ldap.passwd password I couldn't find any open bugs for ldap on 7.2.1.1 Regards / Åke ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Glenn Walker Sent: den 1 mars 2007 14:47 To: Langborg Tom; Parisi, Justin; toasters(a)mathworks.com Subject: RE: usermap problem For like usernames, it will work. You stated that the usernames that were not alike did not function, but the like user names did. How exactly is the filer going to map two users with unlike names together without usermap.cfg? Are you sure that the users aren't mapping to 'pcuser'? wcc -s <username> would show for sure. Glenn ________________________________ From: Langborg Tom [mailto:Tom.Langborg@smhi.se] Sent: Thursday, March 01, 2007 7:44 AM To: Glenn Walker; Parisi, Justin; toasters(a)mathworks.com Subject: SV: usermap problem No I have two other netapp's with 7.0.4, which is working. No usermap.cfg is needed. /tom ________________________________ Från: Glenn Walker [mailto:ggwalker@mindspring.com] Skickat: den 1 mars 2007 13:13 Till: Langborg Tom; Parisi, Justin; toasters(a)mathworks.com Ämne: RE: usermap problem If the unix names and windows names are not the same, you must always use usermap.cfg file. This has not changed since around ONTAP 5.2 to my knowledge. Glenn ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Langborg Tom Sent: Thursday, March 01, 2007 3:55 AM To: Parisi, Justin; toasters(a)mathworks.com Subject: SV: usermap problem Yes I use usermap.cfg now But the old version could I use the ldap.usermap config. I don't want to manage a usermap.cfg when I have all information in ldap. I didn't need that in the Ontap 7.0.4. Regards tom ________________________________ Från: Parisi, Justin [mailto:Justin.Parisi@netapp.com] Skickat: den 28 februari 2007 20:33 Till: Langborg Tom; toasters(a)mathworks.com Ämne: RE: usermap problem You need to do your user mapping through the /etc/usermap.cfg file on the filer. http://now.netapp.com/NOW/knowledge/docs/olio/guides/ontap_troubleshooting/… ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Langborg Tom Sent: Wednesday, February 28, 2007 10:07 AM To: toasters(a)mathworks.com Subject: usermap problem Watch out. I got usermap problem after uppgrade to 7.2.1.1. I use ldap.usermap for usermapping. The unix name are not the same as windows name. With unix name same as windows name it still works. If there are someone who now any fix for this problem, Please send me a letter. Regards tom

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