toasters February 2013

toasters@lists.teaparty.net

44 participants
30 discussions

NetApp 8.0.2, raiddp, 2 failed disks - performance problem.
by Rafał Radecki 08 Feb '13

08 Feb '13

Hi All. I am new to this forum and quite new to NetApp. I work on FAS3210 with 8.0.2 7-Mode. We have 22 SAS disks in our appliance. The aggregate is: >aggr status Aggr State Status Options aggrX online raid_dp, aggr root degraded redirect 32-bit because we have lost 2 disks 2 days ago (one spare and one data disk, NetApp has sent new disks to us). The problem is that the appliance is performing bad in this situation. NFS latency in file operations changed from for example 0,04ms to 0,4ms. I know that the aggregate is now using parity disks in place of one of the failed disks but is this performance drop common? Are there any known ways/howtos to cut down this problem? Best regards, Rafal Radecki.

3 2

RE: Nifty ONTAP option nfs.max_num_aux_groups
by Touretsky, Gregory 08 Feb '13

08 Feb '13

NFSv3 supports both auth_sys (traditional) and rpcsec_gss (Kerberos) authentication. The latter has no 16 gids limit, but might require multiple changes in your environment to support cron jobs, unattended batch, etc. -----Original Message----- From: Steve Losen [scl(a)virginia.edu<mailto:scl@virginia.edu>] Sent: Friday, February 08, 2013 01:47 PM GMT Standard Time To: toasters(a)teaparty.net Subject: Nifty ONTAP option nfs.max_num_aux_groups Hi folks, We tend to use unix style security on shares that are accessed via both NFS and CIFS. Being a university we have a large number of users and groups, and some folks belong to numerous groups. (We use group permissions for shared projects and some folks are members of many unix groups.) We use NFS v3 exclusively and the auxiliary group list is passed by the NFS client in each NFS packet, and it is limited to 16 groups. This is rather inconvenient for some NFS users. Does anyone know if this is a hard NFS v3 limit? For CIFS we authenticate via a Windows domain and the CIFS credentials are mapped to Unix credentials for unix style security. We noticed with "cifs shares -s username" that folks were being limited to 32 unix groups. I have discovered that you can do this: options nfs.max_num_aux_groups 256 (the only legal values are 32 and 256, we have DOT 8.0.1 7-Mode.) and now our CIFS users who belong to over 32 unix groups are getting all their groups. No help for NFS v3 but this will make several of our CIFS users happy. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support _______________________________________________ Toasters mailing list Toasters(a)teaparty.net http://www.teaparty.net/mailman/listinfo/toasters --------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Max fiber run length from 3250 to MK14
by Mr Fletcher Cocquyt 08 Feb '13

08 Feb '13

We have rack space constraints. Can our 3250 heads be 6 racks away from our MK14 trays? Thanks, Fletcher

3 2

Minimum PSUs required for DS4243 with 24x SAS
by Alexander Griesser 07 Feb '13

07 Feb '13

Hey there, we were just re-cabling some of the power cords on our DS4243 shelfs with 4 PSUs and 24x 15k 600GB SAS. When I power down one of the 4 available PSUs in the DS4243, I get the following messages in system log and autosupports are generated: Wed Feb 6 19:28:15 CET [barricade:ses.status.psError:CRITICAL]: DS4243 (S/N SHJHU000000055F) shelf 2 on channel 0a power error for Power supply 4: critical status; power supply failed. This module is on the rear side of the shelf, at the bottom right. Wed Feb 6 19:28:15 CET [barricade:ses.status.volError:CRITICAL]: DS4243 (S/N SHJHU000000055F) shelf 2 on channel 0a voltage error for Voltage sensor 8: unrecoverable error. This module is on the rear side of the shelf, at the lower right, on the power supply. Wed Feb 6 19:28:15 CET [barricade:ses.psu.powerReqError:CRITICAL]: Not enough power supplies are present in channel 0a disk shelf 2 to satisfy disk drive and shelf power requirements. Wed Feb 6 19:28:15 CET [barricade:monitor.shelf.fault:CRITICAL]: Fault reported on disk storage shelf attached to channel 0a. Please check fans, power supplies, disks, and temperature sensors. Wed Feb 6 19:28:15 CET [barricade:callhome.shlf.fault:error]: Call home for SHELF_FAULT Wed Feb 6 19:28:15 CET [barricade:monitor.shelf.configError:CRITICAL]: Enclosure services has detected an error in access to shelves or shelf configuration 0a. Wed Feb 6 19:28:15 CET [barricade:callhome.config:warning]: Call home for CONFIGURATION_ERROR Wed Feb 6 19:29:00 CET [barricade:monitor.globalStatus.critical:CRITICAL]: Disk shelf fault. Disk shelf configuration error. Wed Feb 6 19:29:11 CET [barricade:ses.status.psInfo:info]: DS4243 (S/N SHJHU000000055F) shelf 2 on channel 0a power supply information for Power supply 4: normal status. Wed Feb 6 19:29:11 CET [barricade:ses.status.volInfo:info]: DS4243 (S/N SHJHU000000055F) shelf 2 on channel 0a voltage information for Voltage sensor 8: normal status. Wed Feb 6 19:29:11 CET [barricade:monitor.shelf.fault.ok:info]: Fault previously reported on disk storage shelf attached to channel 0a has been corrected. Wed Feb 6 19:29:11 CET [barricade:monitor.shelf.configError.ok:info]: Enclosure services-detected configuration error has been corrected on channel 0a. Wed Feb 6 19:30:00 CET [barricade:monitor.globalStatus.ok:info]: The system's global status is normal. Why exactly does it think that there are not enough power supplies present if I just shut down one of them? I was under the assumption that a full SAS shelf can work with 2 PSUs and a full SATA shelf can work with 1 PSU without problems. Am I wrong? Nothing happend to the filers, no takeover, no errors, etc., but the message in the logs puzzles me. Thanks && bye, Alexander Griesser System-Administrator ANEXIA Internetdienstleistungs GmbH Telefon: +43-463-208501-320 Telefax: +43-463-208501-500 E-Mail: ag(a)anexia.at <mailto:ag@anexia.at> Web: http://www.anexia.at <http://www.anexia.at> Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

3 3

NetApp 8.0.2 7-mode - update to 8.1.2.
by Rafał Radecki 06 Feb '13

06 Feb '13

Hi All. I have a FAS3210 appliance with NetApp 8.0.2. I would like to update it to 8.1.2. In http://support.netapp.com/ (My AutoSupport) I see there is a "Upgrade Advisor" section. There is a step-by-step howto. But are there any good documents about updating this software? I would like to make as few mistakes as possible, I will do it for the first time ;) Best regards, Rafal Radecki.

3 3

Authentication Issues w/ SCCM talking to filer via CIFS w/ Computer Account
by Ray Van Dolson 05 Feb '13

05 Feb '13

We're having authentication issues with SCCM pointed at a CIFS share on a filer running ONTAP 8.0.x. SCCM uses a domain computer account to authenticate (our filer is also joined to our domain). We've added the computer account at the share level (as well as "Domain Computers") with full permissions, but continue to get authentication denied errors back from the filer. Speficially: Fri Feb 1 16:28:27 PST [red-str-napc2-p2: auth.trace.authenticateUser.loginTraceIP:info]: AUTH: Login attempt by user red-inf-cm-p01$ of domain DOMAIN from client machine 1.1.1.1 (RED-INF-CM-P01). Fri Feb 1 16:28:27 PST [red-str-napc2-p2: auth.dc.trace.DCConnection.statusMsg:info]: AUTH: TraceDC- attempting authentication with domain controller \\REDDC1. Fri Feb 1 16:28:27 PST [red-str-napc2-p2: auth.trace.authenticateUser.loginRejected:info]: AUTH: Login attempt by user rejected by the domain controller with error 0xc0000199: STATUS_NOLOGON_WORKSTATION_TRUST_ACCOUNT. Fri Feb 1 16:28:28 PST [red-str-napc2-p2: auth.trace.authenticateUser.loginTraceIP:info]: AUTH: Login attempt by user red-inf-cm-p01$ of domain DOMAIN from client machine 1.1.1.1 (RED-INF-CM-P01). This reads like the problem is with AD rejecting the login, but when we point to another CIFS share on a real Windows box we don't get the same problem, so we don't think that's the case. We came across this KB article[1] which seems to disable the use of the computer account for authentication. However, this seems to send *no* authentication information at all (anonymous?) which of course is rejected as well. Help? We'll be reaching out to support as well. Thanks, Ray [1] https://kb.netapp.com/support/index?page=content&id=2013374

3 6

NT_STATUS_NO_MEMORY
by Ray Van Dolson 05 Feb '13

05 Feb '13

Anyone ever encountered this error when attempting to access a CIFS share on an ONTAP 8.0.x system? ("NT_STATUS_NO_MEMORY"). We encountered reports from users of intermittent failures to connect to CIFS shares. From Windows hosts, things would just time out. From Samba clients, the above NT_STATUS_NO_MEMORY error was the result. The "fix" ended up being to restart the CIFS service on the system, but wondering what the true root cause here might be. I'm unsure how accurate the error returned by the Samba client is -- in any case there doesn't appear to be a way to query memory utilization on the NetApp. Thanks, Ray

2 2

VSC 4.1 & Online alignments
by Scott Eno 05 Feb '13

05 Feb '13

Hi, We're trying to get some VM's aligned in our NFS-based VMware environment using the "online" alignment tool packaged in VSC. Since we are NFS, the tool needs a VMFS datastore to use to align the VM. When we run the tool and it moves the VM to the VMFS datastore, the VM no longer shows up as misaligned. However, if we move the VM back to an NFS datastore, it shows up as misaligned again. So, is this a one-way trip? NFS --> VMFS, but that VM can never go back?

4 10

RE: nasty virus
by Klise, Steve 04 Feb '13

04 Feb '13

To fast on the trigger.. I don't want to start up the thread about AV on or not on the filers (I run it on my filer), but we got hit with a nasty variant of this. Not sure why Trend didn't block it, but basically a bunch of my CIF folders were set to read only/hidden.. Not fun. There are some other reasons that need to be mitigated that I wont go into, but this is the virus. http://about-threats.trendmicro.com/Malware.aspx?id=47409&name=WORM_VOBFUS.… To unhide the share, we were mapped to the share location, and ran this.. It unhides the shares lick-ity split. >From an XP box.. Cmd "usebackq delims=#" %i in (`dir *. /ah /s /b`) do attrib -s -h "%i" Just share because I care..

2 1

instantaneous snap restore ?
by Avi Ben Emanuel (Wollman) 04 Feb '13

04 Feb '13

marketing continuously claim that snap restore is instantaneous. yet I have yet to succeeded doing so. "snap restore" of files to a location quite a while and is "copying the files" nothing close to instantaneous. i would be happy to understand what i am missing. the following is a example of a virtual disk that was restored, it took quite a while to "restore"=copy this 80gb file. snap restore -t file -s nightly.0 /vol/vmsata/vmfs1/lms-client/lms-clinet-flat.vmdk Avi -- ------------ Avi Ben Emanuel (Wollman) (אבי בן עמנואל (וולמן Systems Engineer | Unix Microsoft Vmware Jerusalem College of Technology מחלקת תקשוב בית הספר הגבוה לטכנולוגיה - מכון לב POB 16031 Jerusalem 91160 Israel הועד הלאומי 21 ירושלים Email: avi(a)jct.ac.il | Office: +972-2-6751036 | Mobile: +972-52-3809107 ------------

4 3

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 February 2013