toasters

toasters@lists.teaparty.net

13520 discussions

Re: netgroups not being applied 7.3
by Nicholas Bernstein 06 Feb '09

06 Feb '09

Ed Wilts wrote: > On Thu, Feb 5, 2009 at 11:53 PM, Nicholas Bernstein > <nick(a)nicholasbernstein.com <mailto:nick@nicholasbernstein.com>> wrote: > :: snip:: > > There are some pretty serious bugs with netgroups in 7.3. It's a lot > better with 7.3.1 but still not 100% right yet. We had a high > priority case open with NetApp on this because we couldn't even start > to get a new filer into production on 7.3 because of the multiple issues. > > It was another guy in my group that worked the specific issue but I'll > dig up his notes when I get to the office (he doesn't work Fridays). > > Is upgrading to 7.3.1 an option for you? Yeah, this is in a lab environment, so 7.3.1 is a definite option. Thank you for confirming this, I appreciate it. I had started to thing I was loosing it a little bit. :) -Nick

1 0

read_align_histo.XX/write_align_histo.XX output from stats command
by Filip Sneppe 06 Feb '09

06 Feb '09

Hi, This article: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb24492 talks about troublshooting LUN alignment issues. It mentions some statistics one can get from the stats command. Does anyone know how to interpret these, eg.: lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.0:5% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.1:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.2:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.3:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.4:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.5:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.6:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.7:81% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.0:2% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.1:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.2:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.3:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.4:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.5:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.6:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.7:70% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_partial_blocks:13% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_partial_blocks:24% How does one interpret the various *_align_histo.* counters ? Regards, Filip

3 5

netgroups not being applied 7.3
by Nicholas Bernstein 06 Feb '09

06 Feb '09

Hi all, I'm doing a very basic local /etc/netgroups to give out access via the /etc/exports file. (eg rw=trustedhosts (also @trustedhosts was tried)). If I give out access via the hostname/ip everything works fine. Add netgroups and it stops working. This is the fist time I've seen issues with a local netgroups file, and it's on 7.3 ontap. Has anyone else tried using netgroups on 7.3? Is anyone aware of any issues? netgroups: ---------------------------- trustedhosts (adminhost,,) untrusted_hosts (,,) all_hosts trusted_hosts untrusted_hosts ---------------------------- exports: ---------------------------- /vol/vol2/netgroupsq rw=trustedhosts,rw=trustedhosts Thanks in advance, Nick

1 0

MEC (Multichassis EtherChannel)
by David Lee 05 Feb '09

05 Feb '09

(I'm a little out of my depth here, so there may be some bits needing lateral interpretation...) We already use bonded/trunked ethernet from the NetApp to a switch. That's fine. We are planning a network upgrade, which gives us a chance to do this bonding/trunking to a logically linked pair of switches (Cisco 3750E) that operate as a single virtual switch, using "MEC". (The theory is that if a switch in the MEC-pair fails, the bond/trunk link continues working through the other switch, albeit with degraded throughput.) Does anyone know whether MEC does/doesn't (will/won't) work? Is there anything MEC-specific that needs to be done in NetApp? Issues? (Other questions I should be asking? Etc.) Pointers to existing information would probably be fine. Thanks in advance. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

6 6

Trouble with wrong quota report numbers
by Paul Letta 04 Feb '09

04 Feb '09

Hi Everyone. I am having a quota issue on qtrees that are in flexvols. I've been noticing one particular qtree growing over the past several weeks. It grows until it hits the quota, users scream, I increase the quota and so on... It got to the point where I just didn't believe that much space was being consumed. I started doing du commands all over the place, but could not find where that qtree was growing. A du at the root of that qtree did not show it growing either. Here's some output from quota reports for a particular qtree: Yesterday morning: tree 45 group ideas 535695812 576716800 432819 Yesterday at 5pm: tree 45 group ideas 550047436 576716800 432915 A du of that qtree actually went down between those times. So I did a quota off/on and let it re-initialize. This morning: tree 45 group ideas 414589436 576716800 432904 I know that area did not fall by over 100GB overnight. And a few hours later: tree 45 group ideas 418067772 576716800 433545 The quota report usage shows it has grown by several GB. The du of the qtree is about flat. I thought maybe the snapshot space is being counted against the quotas. I didn't think that was the way it was supposed to work. I maintain 8 hourly, 5 nightly, and 3 weekly snapshots of this flexvol. So yesterday I deleted the weekly.2 early, waited a while, and then ran the quota report. It went up. I don't know where to go from here. I opened a case with NetApp. They were going to look at it in the lab. Does anyone have any suggestions ? FAS3040. OnTap 7.2.6.1 Last month after all the talk about this release and quotas and panics, I opened a case with NetApp. They had me change setflag wafl_enable_allocation_size from a 1 to a 0. Thanks, Paul

2 2

Re: read_align_histo.XX/write_align_histo.XX output from stats command
by Barlow, Richard 04 Feb '09

04 Feb '09

This looks like it needs to be plotted into a histogram so you can see the regular distribution of the values. Richard Barlow Senior Systems Engineer NetApp 804.929.2500 ----- Original Message ----- From: Filip Sneppe <filip.sneppe(a)gmail.com> To: NetApp list <toasters(a)mathworks.com> Sent: Wed Feb 04 10:52:01 2009 Subject: read_align_histo.XX/write_align_histo.XX output from stats command Hi, This article: https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb24492 talks about troublshooting LUN alignment issues. It mentions some statistics one can get from the stats command. Does anyone know how to interpret these, eg.: lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.0:5% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.1:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.2:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.3:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.4:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.5:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.6:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_align_histo.7:81% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.0:2% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.1:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.2:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.3:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.4:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.5:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.6:0% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_align_histo.7:70% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:read_partial_blocks:13% lun:/vol/esx_lun_data1/luns/esx_lun1.lun-P3NsiJNHOSbN:write_partial_blocks:24% How does one interpret the various *_align_histo.* counters ? Regards, Filip

1 0

Strange SnapVault error
by Karlsson Ulf Ibrahim :ULK 02 Feb '09

02 Feb '09

Hello everybody! I have a SnapVault relationsip that's starting to give me gray hairs.. On the primary there's a flexvol with 4 qtrees, being backed up by SnapVault to a corresponding qtrees on the secondary. Three out of four works without problems, but one of the qtrees stopped working 3 days ago. The error as seen in Operations Manager is : replication destination could not set permissions on a file or directory This is strange, SnapVault is a block level copy of the primary file system... Any suggestions?

3 2

SV: Strange SnapVault error
by Karlsson Ulf Ibrahim :ULK 02 Feb '09

02 Feb '09

Hello1 > > What do the "messages" logfiles on both the filers tell you? > Sun Feb 1 02:09:06 CET [replication.dst.waflErr:error]: SnapVault: destination transfer from 192.168.10.10:/vol/linux/home to /vol/sv_pnap1h1_linux/pnap1h1_linux_home : replication destination could not set permissions on a file or directory:Invalid argument. /Uffe

1 0

Re: Local FCP nodename does not match the cluster partner's FCP nodename.
by Linux Admin 01 Feb '09

01 Feb '09

What would be the impact of running in this state? Is this just an issue for cluster takeovers/failover? On Sat, Jan 31, 2009 at 11:18 PM, Webster, Stetson < Stetson.Webster(a)netapp.com> wrote: > I personally went through this problem about a year ago. At the time > when I remedied it, I was not serving data. Luckily, it was in the > beginning stages of my implementation. Though I don't remember if both > controllers were brought down, my circumstances were such that it didn't > matter. > > > > *Stetson M. Webster** > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Sunday, February 01, 2009 12:09 AM > > *To:* Webster, Stetson > *Cc:* NetApp Toasters List > *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Thanks again Stetson, great help!!! > > Did anyone in the group ever remedy this bug manually: > Do I need to run "fcp stop/start" on both nodes? > > On Sat, Jan 31, 2009 at 10:58 PM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > You can change either to the other. The idea is to get them to match, so > it doesn't matter which one. I believe there will be an outage. I would > not recommend trying it while serving live data. I cannot comfortably tell > you to do a failover to change it either. > > > > *Stetson M. Webster > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:53 PM > *To:* Webster, Stetson > *Cc:* NetApp Toasters List > *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Stetson, > > Thanks!!!! > > Quick follow up to you and the group: > > It says: > > > > In such a case, the user must run an "fcp nodename" command on the partner and > > obtain the partner's nodename. Update the local head's nodename (WWN) with the > > > > partner's nodename using the "fcp set nodename WWN". Then, verify that it is > > set with "fcp nodename" on the local head. Then run "fcp start" to start the fcp > > service. > > > > > > > > netapp01> fcp nodename > > Fibre Channel nodename: 50:xx:xx:xx:xx:xx:xx:xx > > netapp02> fcp nodename > Fibre Channel nodename: 50:yy:yy:yy:yy:yy:yy:yy > > Which one do I set with "fcp set" command: netapp1 and netapp2. Does it > cause outage? > (fcp start?) > > On Sat, Jan 31, 2009 at 10:42 PM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > Try this: > > http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=202390 > > > > > > *Stetson M. Webster > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:23 PM > *To:* NetApp Toasters List > *Subject:* Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Ho folks > > What does this error means and how do I remedy it? > > > > >

1 0

Re: Local FCP nodename does not match the cluster partner's FCP nodename.
by Linux Admin 01 Feb '09

01 Feb '09

Thanks again Stetson, great help!!! Did anyone in the group ever remedy this bug manually: Do I need to run "fcp stop/start" on both nodes? On Sat, Jan 31, 2009 at 10:58 PM, Webster, Stetson < Stetson.Webster(a)netapp.com> wrote: > You can change either to the other. The idea is to get them to match, so > it doesn't matter which one. I believe there will be an outage. I would > not recommend trying it while serving live data. I cannot comfortably > tell you to do a failover to change it either. > > > > *Stetson M. Webster** > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:53 PM > *To:* Webster, Stetson > *Cc:* NetApp Toasters List > *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Stetson, > > Thanks!!!! > > Quick follow up to you and the group: > > It says: > > > In such a case, the user must run an "fcp nodename" command on the partner and > obtain the partner's nodename. Update the local head's nodename (WWN) with the > > partner's nodename using the "fcp set nodename WWN". Then, verify that it is > set with "fcp nodename" on the local head. Then run "fcp start" to start the fcp > service. > > > > netapp01> fcp nodename > > Fibre Channel nodename: 50:xx:xx:xx:xx:xx:xx:xx > > netapp02> fcp nodename > Fibre Channel nodename: 50:yy:yy:yy:yy:yy:yy:yy > > Which one do I set with "fcp set" command: netapp1 and netapp2. Does it > cause outage? > (fcp start?) > > > On Sat, Jan 31, 2009 at 10:42 PM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > Try this: > > http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=202390 > > > > > > *Stetson M. Webster > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:23 PM > *To:* NetApp Toasters List > *Subject:* Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Ho folks > > What does this error means and how do I remedy it? > > >

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