toasters

toasters@lists.teaparty.net

1 participants
13518 discussions

RE: NFS issue after upgrading filers to 9.2P2
by Steiner, Jeffrey 24 Jan '18

24 Jan '18

It takes a lot for an ONTAP system to flat-out be unable to respond. Unless the timeout parameters are exceedingly short, you shouldn't reach that point, especially with anything capable of running ONTAP 9.2. I'd open a support case on this one. In addition, if you want to trigger an autosupport and send me the serial numbers directly I can take a glance at a few stats to see if anything looks odd. From: Fenn, Michael [mailto:fennm@DEShawResearch.com] Sent: Tuesday, January 23, 2018 6:23 PM To: Steiner, Jeffrey <Jeffrey.Steiner(a)netapp.com>; Mark Saunders <Mark.Saunders(a)pcmsgroup.com>; toasters(a)teaparty.net Subject: Re: NFS issue after upgrading filers to 9.2P2 The messages are not necessarily indicative of a network problem. The kernel prints "nfs: server … not responding, still trying" when an operation times out (timeo deciseconds) for the configured (retrans) number of tries. Once the server responds, then it prints "nfs: server … OK". Networking problems are certainly one reason that an operation would time out, but not the only reason. An overloaded or down file server will cause the same effect. Thanks, Michael From: <toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net>> on behalf of "Steiner, Jeffrey" <Jeffrey.Steiner(a)netapp.com<mailto:Jeffrey.Steiner@netapp.com>> Date: Tuesday, January 23, 2018 at 10:38 AM To: Mark Saunders <Mark.Saunders(a)pcmsgroup.com<mailto:Mark.Saunders@pcmsgroup.com>>, "toasters(a)teaparty.net<mailto:toasters@teaparty.net>" <toasters(a)teaparty.net<mailto:toasters@teaparty.net>> Subject: RE: NFS issue after upgrading filers to 9.2P2 Those messages are indicative of a network problem. The packets are going through, then they succeed when the NFS client retries, then they pause again. I can't think why an ONTAP upgrade of this type would cause such a problem. If it was working before, it should be working now. If you had any kind of a locking, firewall, or general configuration problem you should have no access whatsoever. I've seen some weird NFS bug sin SUSE, but that RHEL version should be fine. What are the mount options used, and are you using DNFS? From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Mark Saunders Sent: Tuesday, January 23, 2018 4:29 PM To: toasters(a)teaparty.net<mailto:toasters@teaparty.net> Subject: NFS issue after upgrading filers to 9.2P2 Hi gents today we have upgraded our Coventry cluster from 9.1P6 to 9.2P2 and we are about 99% working we just have a strange issue with SAP database servers NFS mounts. When the server is bounced the mounts are attached with no problems but after a few minutes a df –h starts to be very slow reporting the NFS mounted directories and if the databases are started up they hang and a df –h then also hangs. This sometimes recovers enough to then allow a df –h to work again but the databases are a lost cause right now. In the server messages we get lots of entries for the SVM Jan 23 07:01:27 jwukccsbci kernel: nfs: server JWUKCSVM01 not responding, still trying Jan 23 07:01:47 jwukccsbci last message repeated 5 times Jan 23 07:02:07 jwukccsbci kernel: nfs: server JWUKCSVM01 OK Jan 23 07:02:07 jwukccsbci last message repeated 5 times Jan 23 07:02:27 jwukccsbci kernel: nfs: server JWUKCSVM01 not responding, still trying Jan 23 07:02:47 jwukccsbci last message repeated 5 times Jan 23 07:02:48 jwukccsbci kernel: nfs: server JWUKCSVM01 OK Is there anything that would of changed in the upgrade to lock down NFS or changes options that we might need to change back. The redhat servers are an old kernel version 2.6.18-371.el5 that has some bugs but this was working fine before the filer upgrade was carried out. Regards Mark Data Centre Sysadmin Team Managed Services Phone:- 02476 694455 Ext 2567 The Sysadmin Team promoting PCMS Values ~Integrity~Respect~Commitment~ ~Continuous Improvement~ The information contained in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this e-mail, the use of this information or any disclosure, copying or distribution is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. The views expressed in this e-mail may not necessarily be the views of the PCMS Group plc and should not be taken as authority to carry out any instruction contained. The PCMS Group reserves the right to monitor and examine the content of all e-mails. The PCMS Group plc is a company registered in England and Wales with company number 1459419 whose registered office is at PCMS House, Torwood Close, Westwood Business Park, Coventry CV4 8HX, United Kingdom. VAT No: GB 705338743

7 20

NFS issue after upgrading filers to 9.2P2
by Mark Saunders 23 Jan '18

23 Jan '18

Hi gents today we have upgraded our Coventry cluster from 9.1P6 to 9.2P2 and we are about 99% working we just have a strange issue with SAP database servers NFS mounts. When the server is bounced the mounts are attached with no problems but after a few minutes a df -h starts to be very slow reporting the NFS mounted directories and if the databases are started up they hang and a df -h then also hangs. This sometimes recovers enough to then allow a df -h to work again but the databases are a lost cause right now. In the server messages we get lots of entries for the SVM Jan 23 07:01:27 jwukccsbci kernel: nfs: server JWUKCSVM01 not responding, still trying Jan 23 07:01:47 jwukccsbci last message repeated 5 times Jan 23 07:02:07 jwukccsbci kernel: nfs: server JWUKCSVM01 OK Jan 23 07:02:07 jwukccsbci last message repeated 5 times Jan 23 07:02:27 jwukccsbci kernel: nfs: server JWUKCSVM01 not responding, still trying Jan 23 07:02:47 jwukccsbci last message repeated 5 times Jan 23 07:02:48 jwukccsbci kernel: nfs: server JWUKCSVM01 OK Is there anything that would of changed in the upgrade to lock down NFS or changes options that we might need to change back. The redhat servers are an old kernel version 2.6.18-371.el5 that has some bugs but this was working fine before the filer upgrade was carried out. Regards Mark Data Centre Sysadmin Team Managed Services Phone:- 02476 694455 Ext 2567 The Sysadmin Team promoting PCMS Values ~Integrity~Respect~Commitment~ ~Continuous Improvement~ The information contained in this e-mail is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient of this e-mail, the use of this information or any disclosure, copying or distribution is prohibited and may be unlawful. If you received this in error, please contact the sender and delete the material from any computer. The views expressed in this e-mail may not necessarily be the views of the PCMS Group plc and should not be taken as authority to carry out any instruction contained. The PCMS Group reserves the right to monitor and examine the content of all e-mails. The PCMS Group plc is a company registered in England and Wales with company number 1459419 whose registered office is at PCMS House, Torwood Close, Westwood Business Park, Coventry CV4 8HX, United Kingdom. VAT No: GB 705338743

2 1

Implementing NSE FDE on an existing system
by jordan slingerland 10 Jan '18

10 Jan '18

I have an 8040 currently running CM 9.1P1. All disks are SED but currently in protection-mode open mode. Is there a method to convert the existing disks/aggregates to protection-mode full? Is enabling encryption on spare disks and preforming a disk replace 1 or 2 disks at a time a viable option? That sounds time consuming but I don't have 100TB of swing space.

1 0

Node(s) Out of Quorum During Takeover
by Philbert Rupkins 06 Jan '18

06 Jan '18

Hello, Just inherited a new 4-node ONTAP 9.1P9 cluster. First order of business - testing manual failover functionality. # CLUSTER INITIAL STATE HA PAIR 1: node1 - epsilon, master node2 - secondary HA PAIR 2: node3 - secondary node4 - secondary The node I intended to takeover (node1) was both the master and held the Epsilon. I moved Epsilon to a node in an HA pair that would remain up (node4). However, per the "cluster ring" output, the node I planned to takeover (node1) was still the master. # CLUSTER NODE1 PRE-TAKEOVER STATE HA PAIR 1: node1 - master node2 - secondary HA PAIR 2: node3 - secondary node4 - epsilon, secondary I initiated the takeover of node1 and received "Node(s) Out of Quorum" alerts from the three other members of the cluster. The cluster seemed to be happy after the takeover/giveback was complete. The "cluster ring" output showed the master role had been assumed by another node. # CLUSTER POST NODE1 TAKEOVER/GIVEBACK STATE HA PAIR 1: node1 - secondary node2 - master HA PAIR 2: node3 - secondary node4 - epsilon, secondary Is it normal to receive "Node(s) Out of Quorum" alerts when performing a manual takeover of the master node? Are these alerts the result of an election being forced? Thanks, Phil

1 0

VMware SRM + NetApp SRA + NetApp WFA?
by Ehrenwald, Ian 04 Jan '18

04 Jan '18

This isn't 100% NetApp related, more like 60%, but I think it's still a relevant topic of discussion that others may eventually benefit from too. I've been tasked with setting up DR for a set of VMware VMs at our primary data center by replicating them via SnapMirror to our secondary data center. Normally I'd just use VMware SRM with the NetApp SRA, set up Array Based Replication within SRM, and be done with it. Let SRM and the SRA take care of test, failover, reprotect, etc. However, the sticking point is that a lot of the protected VMs use in-guest NFS mounts for things like database volumes or application binaries and SRM doesn't know what to do with those SnapMirror pair volumes because they're not VMware datastores. My initial thought was to use some PowerShell with the NetApp PowerShell Toolkit in the SRM Recovery Plan for each individual VM pre-boot to connect to the SnapMirror destination filer, break the SnapMirror(s) that the VM uses, mount the volume(s), set export policies, etc. Then figure out how to correctly do resync and reprotect without blowing things up. I got as far as the first part in PowerShell (connect to the destination filer, break the mirror) and thought to myself that this was stupid.. I'm re-inventing the wheel. Surely someone else out there must have done this before and there is a pre-existing solution? I spoke with a NetApp tech support engineer that I happened to have a case open with already regarding the NetApp SRA and he was able to come up with a suggestion from another engineer: Call WFA from SRM in each VMs recovery plan to break the SnapMirror for the volumes required for the VM to work, then also use WFA in the cleanup and reprotect plan to do that work. Has anyone else done something like this? I have a feeling that I'm not breaking new ground with this task. Implementing it wrong has pretty severe implications, though, so I'm not eager to mess it up. Ian Ehrenwald Senior Infrastructure Engineer Hachette Book Group, Inc. 1.617.263.1948 / ian.ehrenwald(a)hbgusa.com This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.

4 7

Panic on bootup (page fault supervisor read, page not present)
by Alexander Griesser 27 Dec '17

27 Dec '17

Hey toasters, I’m trying to repurpose one of my old FAS3240 systems and have booted it up today just to be greeted with the following panic on one of the two controllers: Starting AUTOBOOT press Ctrl-C to abort... Loading X86_64/freebsd/image2/kernel:0x100000/8450504 0x90f1c8/1278720 Entry at 0x80158900 Loading X86_64/freebsd/image2/platform.ko:0xa48000/655232 0xb8ea20/694680 0xae7f80/39656 0xc383b8/43152 0xaf1a68/86316 0xb06b94/63845 0xb16500/140640 0xc42c48/159120 0xb38a60/2024 0xc699d8/6072 0xb39248/304 0xc6b190/912 0xb39378/1680 0xc6b520/5040 0xb39a08/960 0xc6c8d0/2880 0xb39dc8/184 0xc6d410/552 0xb39e80/448 0xb65de0/12918 0xb8e933/237 0xb69058/84120 0xb7d8f0/69699 Starting program at 0x80158900 NetApp Data ONTAP 8.1.3P1 7-Mode Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 04 fault virtual address = 0x28 fault code = supervisor read data, page not present instruction pointer = 0x8:0xffffffff80315571 stack pointer = 0x10:0xffffffff80c73c90 frame pointer = 0x10:0xffffffff80c73cc0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 PANIC : page fault (supervisor read, page not present) on VA 0x28 cs:rip = 0x8:0xffffffff80315571 rflags = 0x10246 version: 8.1.3P1: Wed Jul 10 20:17:14 PDT 2013 conf : x86_64 cpuid = 0 Uptime: 1s coredump: primary dumper unavailable. coredump: trying secondary dumper... no tftp server ip specified netdump: no targets available to dump coredump: secondary dumper failed -1. The operating system has halted. Please press any key to reboot. System halting... cpu_reset called on cpu#0 Any insights on what might be the issue here? Needless to say, there’s no maintenance anymore on this system so opening a support case is not possible 😊 Thanks, Alexander Griesser Head of Systems Operations ANEXIA Internetdienstleistungs GmbH E-Mail: AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com> Web: http://www.anexia-it.com<http://www.anexia-it.com/> Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

4 8

Chicken/egg dillema doing a hardware upgrade on a FAS3250
by Jan-Pieter Cornet 20 Dec '17

20 Dec '17

We have a FAS3250 that's primarily backup storage. It hosts a lot of snapmirror targets, and a few mounted filesystems with backup data. As the hardware is getting old, we've purchased a shiny new FAS8200 with a couple of 8TB drive shelves. We assume that the FAS8200 can be initialized on 9.2 and above using the ADP on external drives feature, to partition those 8T disks, so we don't have to throw away about 50T of storage just on the root aggregates. However... the FAS3250 hardware can only run ontap 9.1. Newer versions of ontap are not available on that hardware. And to make the 8200 nodes join the existing cluster, it has to run the same sofware version (9.1), so... it cannot be initialized with ADP. And you can't initialize first and partition later, because repartitioning wipes all existing data. That's our dilemma. I've actually tried to "manually" partition the disks, by going into maintenance mode and using "disk partition" to force the 8200 nodes to see only partitioned disks, and then re-initializing them using boot menu "4 - clean config and reinitialize disks". That fails, and 9.1 doesn't want to write a root FS to partitioned disks (it does wipe them, though). Besides, it would likely be unsupported. I did learn some interesting things about the "disk partition" command, by the way, like the "-b" blocksize is in 4k blocks, and the '-i' option that numbers partitions starts at 1, which is a data partition, and number 2 is the root partition, at least in the 2-partition root/data setup. So we either have the option to throw away a large chunk of storage for root aggregates, initialize the new nodes on 9.1, join in cluster, and move the existing data using 'vol move' and all the cDOT goodness that comes with it. ... or build the new 8200 as a separate cluster, initialize it with 9.3, partition the disks via the boot menu, and then move the data over using snapmirror, and remounting the clients. That's doable because most of the data is snapmirror target anyway, and there's a limited number of mounted filesystems that would need a remount. It's a shame that cDOT doesn't have "snapmirror migrate" like 7mode did. Does anyone have any other options? All I could think is get swing gear and basically do the migration twice, first to hardware that supports ontap >= 9.2, then to our new 8200. But I'm not willing to spend a lot of money renting the swing gear and getting a lot of extra setup work basically because of a flaw in netapp software. Thanks, -- Jan-Pieter Cornet <johnpc(a)xs4all.nl> "Any sufficiently advanced incompetence is indistinguishable from malice." - Grey's Law

7 10

Windows access issues on cifs for a both linux adn windows qtree.
by Martin Sandell 20 Dec '17

20 Dec '17

Hello all smart people. Hopefully someone has the answer on how to solve this, because I’m out of ideas…. We have a volume with on qtree that our customer is mounting on both Linux and Windows. Qtree sec. style is unix, and the unix parts work without issue, the problems are on windows. After implementing a vserver name mapping and creating a few unix users and groups they can now access things based on the unix owner. But it seems no matter what I try so far, I can’t seem to solve how to fix so they can access based on group membership. All I get during my tests are “Access Denied”. I have: · Added the group to the Netapp as a local unix group · Added a name mapping I the veserver from the windows group to the unix group. That is direction unix-win and the windows domain group some_group to some (the same name minus _group) · Added the group on the cifs share with its correct windows name and the permission full control If someone knows how to solve this or has seen it before, please help! The Netapp system is a clustred ONTAP 9.1P2. Martin Sandell Storage Systems Consultant Basefarm BASEFARM | Sveavägen 159 | 113 46 Stockholm | Sweden Phone: +46 8 5011 26 82 | Mobile: +46 735 260 082 Martin.sandell(a)basefarm.com | www.basefarm.com <http://www.basefarm.com/> Blog<http://blog.basefarm.com/> | Twitter<http://twitter.com/basefarmsweden> | Facebook<https://www.facebook.com/basefarmab?fref=ts> | LinkedIn<https://www.linkedin.com/company/24492?trk=tyah&trkInfo=tarId:1399882283968…> [id:3F974EAF-DCAE-4FB1-BE97-BEEBF3511725]

2 1

CIFS Access Based Enumeration for Volume in Namespace
by Stephen Stocke 07 Dec '17

07 Dec '17

Hello I have a need to use access-based enumeration within a CIFS share that contains volumes mounted as junction paths within the share volume. ABE is working for normal files and folders but volumes mounted as junction paths are visible even if the user does not have permissions to see the folder representing the junction. Has anyone done this? Or can anyone point to any documentation on whether this is possible? ONTAP 9.1p5, ntfs security style on all volumes. Many thanks Steve

1 0

Re-cable existing shelf into new loop
by TAYLOR DANIEL 29 Nov '17

29 Nov '17

Hello, We need to re-cable a shelf out of its current loop into a new one, just interested to know if anyone had done this without issue? We want to do this non disruptively so keen to hear other peoples comments and thoughts on this and if possible without causing a panic. Running 9.1P8. Thanks Dan

2 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