toasters

toasters@lists.teaparty.net

3 participants
13534 discussions

AW: How to verify the health of all disks?
by Alexander Griesser 13 Nov '15

13 Nov '15

Hi, I've now updated qual_devices and installed the most recent disk firmware files; hammer did not find any issue, disk maint found two failed disk, the others seem to be good. Also, for whatever reason, running `disk_fw_update` with the latest files installed succeeded in installing the firmware on all of the 4321 disks, so it looks good now. Thanks! Alexander Griesser Head of Systems Operations ANEXIA Internetdienstleistungs GmbH E-Mail: AGriesser(a)anexia-it.com Web: 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 -----Ursprüngliche Nachricht----- Von: John Clear [mailto:jac@panix.com] Gesendet: Donnerstag, 12. November 2015 00:32 An: Alexander Griesser <AGriesser(a)anexia-it.com> Betreff: Re: How to verify the health of all disks? Since it is an empty filer, you might be able to use qual_devices to fake out the system enough to let you update the firmware. I've never run into the 4321 bug, but qual_devices is what tells the filer about what kind of disks it has. I've seen issues before where the qual_devices files weren't updated and that caused new disks to not be recognized. John On Wed, Nov 11, 2015 at 10:42:48AM +0000, Alexander Griesser wrote: > Hi, > > the disks which are showing 4321 as revision won't update, all other disks got updated perfectly fine. I've upgraded the HA pair to 8.1.4P9 (which is the latest support on this platform, AFAIK). > Any idea how I can force the disk firmware update on those disks? Maybe in maintenance mode? > > 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 > > Von: andrei.borzenkov(a)ts.fujitsu.com > [mailto:andrei.borzenkov@ts.fujitsu.com] > Gesendet: Mittwoch, 11. November 2015 11:41 > An: Alexander Griesser <AGriesser(a)anexia-it.com>; > toasters(a)teaparty.net > Betreff: RE: How to verify the health of all disks? > > You need to update drive firmware before continuing (probably in conjunction with DOT upgrade). See http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=853138. > > --- > With best regards > > Andrei Borzenkov > Senior system engineer > FTS WEMEAI RUC RU SC TMS FOS > [cid:image001.gif@01CBF835.B3FEDA90] > FUJITSU > Zemlyanoy Val Street, 9, 105 064 Moscow, Russian Federation > Tel.: +7 495 730 62 20 ( reception) > Mob.: +7 916 678 7208 > Fax: +7 495 730 62 14 > E-mail: > Andrei.Borzenkov(a)ts.fujitsu.com<mailto:Andrei.Borzenkov@ts.fujitsu.com > > > Web: ru.fujitsu.com<http://ts.fujitsu.com/> > Company details: > ts.fujitsu.com/imprint<http://ts.fujitsu.com/imprint.html> > This communication contains information that is confidential, proprietary in nature and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation. > Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission. > > From: > toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> > [mailto:toasters-bounces@teaparty.net] On Behalf Of Alexander Griesser > Sent: Wednesday, November 11, 2015 11:19 AM > To: toasters(a)teaparty.net<mailto:toasters@teaparty.net> > Subject: How to verify the health of all disks? > > Hi Toasters, > > I had a pretty stunning experience on a customer's used filer installation yesterday, long story short: > FSA2040 with 1xDS4243 24x1TB SATA disks, had to reinitialize the whole system because controller and shelves have been procured from different sources, so there was no root volume, etc. > After I figured the disk reassignment out and have wiped both filers, they both booted up with a 3 disk aggr0 raid_dp and I could start to work on it. > > I then added a bunch of disks to filer #1 and continued with the configuration, until I found out, that some of the disks would not allow the firmware to be updated. The disks in question look like this: > > *> disk_list > DISK CHAN VENDOR PRODUCT ID REV SERIAL# HW (BLOCKS BPS) DQ > ------------ ----- -------- ---------------- ---- -------------------- -- -------------- -- > 0d.11.2 SA:A NETAPP X302_WVULC01TSSM 4321 WD-WCAW30821984 ff 1953525168 512 N > > Working disks look like this: > > *> disk_list > DISK CHAN VENDOR PRODUCT ID REV SERIAL# HW (BLOCKS BPS) DQ > ------------ ----- -------- ---------------- ---- -------------------- -- -------------- -- > 0d.11.0 SA:A NETAPP X302_WVULC01TSSM NA02 WD-WCAW31217461 ff 1953525168 512 N > > I've googled a bit and found out that disks showing up with REV "4321" need to be replaced, there seems to have been a series of disks in the past with this error, so what I did was I pulled one of those disks out of the filer and replaced it with another one. > The system immediately started to reconstruct the now missing filesystem disk from the spare disk, when the log started to fill up about block errors on other disks during reconstruction, then about 10 minutes later, a double reconstruct was running and about 30 minutes later, the filer paniced due to multi disk failure and that's where I ended up then. > > So since there was no data on the filer, I wiped it again and am now back up and running with 3 disks in aggr0 and I'm currently replacing one of the "4321" disks with another one: > > *> disk replace start 0d.11.2 0d.11.3 > aggr status -r > Aggregate aggr0 (online, raid_dp) (block checksums) > Plex /aggr0/plex0 (online, normal, active) > RAID group /aggr0/plex0/rg0 (normal, block checksums) > > RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) > --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- > dparity 0d.11.0 0d 11 0 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 > parity 0d.11.1 0d 11 1 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 > data 0d.11.2 0d 11 2 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 (replacing, copy in progress) > -> copy 0d.11.3 0d 11 3 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 (copy 0% completed) > > The question now is: since the spare disks were all properly zeroed and there were no entries in the logs that would show me block errors on these disks, how can I verify, all my spare disks are really good? I'd love to run an intensive test on all the disks in order to make sure something like that doesn't happen again when I put the filer in production. > > I'm very thankful for any advice in this regard. > Is disk maint used for things like that? > > *> disk maint list > Disk maint tests available > Test index: 0 Test Id: ws Test name: Write Same Test > Test index: 1 Test Id: ndst Test name: NDST Test > Test index: 2 Test Id: endst Test name: Extended NDST Test > Test index: 3 Test Id: vt Test name: Verify Test > Test index: 4 Test Id: ss Test name: Start Stop Test > Test index: 5 Test Id: dt Test name: Data Integrity Test > Test index: 6 Test Id: rdt Test name: Read Test > Test index: 7 Test Id: pc Test name: Power Cycle Test > > 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 > > Anschrift Hauptsitz Klagenfurt: Feldkirchnerstra?e 140, 9020 > Klagenfurt > Gesch?ftsf?hrer: Alexander Windbichler > Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT > U63216601 > > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > http://www.teaparty.net/mailman/listinfo/toasters

1 0

How to verify the health of all disks?
by Alexander Griesser 11 Nov '15

11 Nov '15

Hi Toasters, I had a pretty stunning experience on a customer's used filer installation yesterday, long story short: FSA2040 with 1xDS4243 24x1TB SATA disks, had to reinitialize the whole system because controller and shelves have been procured from different sources, so there was no root volume, etc. After I figured the disk reassignment out and have wiped both filers, they both booted up with a 3 disk aggr0 raid_dp and I could start to work on it. I then added a bunch of disks to filer #1 and continued with the configuration, until I found out, that some of the disks would not allow the firmware to be updated. The disks in question look like this: *> disk_list DISK CHAN VENDOR PRODUCT ID REV SERIAL# HW (BLOCKS BPS) DQ ------------ ----- -------- ---------------- ---- -------------------- -- -------------- -- 0d.11.2 SA:A NETAPP X302_WVULC01TSSM 4321 WD-WCAW30821984 ff 1953525168 512 N Working disks look like this: *> disk_list DISK CHAN VENDOR PRODUCT ID REV SERIAL# HW (BLOCKS BPS) DQ ------------ ----- -------- ---------------- ---- -------------------- -- -------------- -- 0d.11.0 SA:A NETAPP X302_WVULC01TSSM NA02 WD-WCAW31217461 ff 1953525168 512 N I've googled a bit and found out that disks showing up with REV "4321" need to be replaced, there seems to have been a series of disks in the past with this error, so what I did was I pulled one of those disks out of the filer and replaced it with another one. The system immediately started to reconstruct the now missing filesystem disk from the spare disk, when the log started to fill up about block errors on other disks during reconstruction, then about 10 minutes later, a double reconstruct was running and about 30 minutes later, the filer paniced due to multi disk failure and that's where I ended up then. So since there was no data on the filer, I wiped it again and am now back up and running with 3 disks in aggr0 and I'm currently replacing one of the "4321" disks with another one: *> disk replace start 0d.11.2 0d.11.3 aggr status -r Aggregate aggr0 (online, raid_dp) (block checksums) Plex /aggr0/plex0 (online, normal, active) RAID group /aggr0/plex0/rg0 (normal, block checksums) RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- dparity 0d.11.0 0d 11 0 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 parity 0d.11.1 0d 11 1 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 data 0d.11.2 0d 11 2 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 (replacing, copy in progress) -> copy 0d.11.3 0d 11 3 SA:A - BSAS 7200 847555/1735794176 847884/1736466816 (copy 0% completed) The question now is: since the spare disks were all properly zeroed and there were no entries in the logs that would show me block errors on these disks, how can I verify, all my spare disks are really good? I'd love to run an intensive test on all the disks in order to make sure something like that doesn't happen again when I put the filer in production. I'm very thankful for any advice in this regard. Is disk maint used for things like that? *> disk maint list Disk maint tests available Test index: 0 Test Id: ws Test name: Write Same Test Test index: 1 Test Id: ndst Test name: NDST Test Test index: 2 Test Id: endst Test name: Extended NDST Test Test index: 3 Test Id: vt Test name: Verify Test Test index: 4 Test Id: ss Test name: Start Stop Test Test index: 5 Test Id: dt Test name: Data Integrity Test Test index: 6 Test Id: rdt Test name: Read Test Test index: 7 Test Id: pc Test name: Power Cycle Test 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

4 13

WWPNs changing adaptors
by Edward Rolison 09 Nov '15

09 Nov '15

Hello admins. I'm hoping you can help me understand something confusing - I've got some FCOE (FCP) luns presented off a filer. We've been looking at doing some reconfig work, because the cabling wasn't right (we had 4a/5a cabled, and want 4a/5b). Anyway, to cut a long story short - we ran fcp portname show - and got a list of WWPNs and controller ids. We've looked again today, and it's changed - we're absolutely sure we had: 4a, 4b, 5a, 5b before (ascending WWPN order). Now they're 4a, 5b, 5a, 4b. And we can't quite figure out how or when they changed (we've had no outage on this kit). Is anyone able to enlighten me as to what might cause a wwpn swap?

3 2

Completely filling and aggregate
by Fred Grieco 07 Nov '15

07 Nov '15

Has anyone ever completely, completely (like with luns and overallocation) filled an aggregate? Were you able to reuse the aggregate again once you reduced the space (presumably by shrinking or deleting a volume or two)? Assume this is not the root aggregate. Putting aside how bad it is, how all the vols will fill and luns will go offline, how the performance will never be right, fragmentation, etc, this is recoverable, right? I'm testing a competitor's product- known for thin provisioning- and it completely went off the rails after I did this accidentally. I mean... Delete everything, start over, and a big fat "don't do that then" from support. TIA, Fred

7 8

Netbackup 7.6.0.1 backing up via NDMP cDOT 8.2.3 volume(s)
by John Stoffel 03 Nov '15

03 Nov '15

Hi, Anyone using Netbackup 7.6.0.1 to backup via three way NDMP, a CIFS share/volume on cDOT inside a VServer? It just ain't working for me. I suspect I need to upgrade to Netbackup 7.7, but before I go that route... I'm looking for other options. Basically, I want to have the NDMP data flow over the network to the Netbackup server, then from there to Tape. I don't have/want direct attached SAN tape drives at this time on our four node cluster. It's just one single volume I need backed up right now. Thanks, John

3 2

Slow SMB connections from 8.3 to some Mac clients
by Rue, Randy 03 Nov '15

03 Nov '15

You're been hearing from me a lot lately. We're having trouble with a small but distinct number of Mac users connecting via either CIFS or SMB and getting slow connections, an rsync of a test file shows a transfer speed of 500KB/s. Most of the problem children are older versions but at least one is running El Capitan, the latest greatest. On the clients that have the problem, they have it reliably. Sounds like a workstation issue but we're still hoping to give the users a solution. Anybody know of any known issues with Macs and CDOT 8.3? Solutions? Randy

7 7

Re: python API guidance for cluster mode CIFS share reporting/management
by Maarten Lippmann 03 Nov '15

03 Nov '15

Hey Randy and Richard, A quick note: I am in no way a programmer, I just pretend to be one when I need to get stuff done. My code is likely ugly. Covering most of the issues called out in this thread. The doc file error means zedi can't run the small handful of zapis that only exist in 8.3 or later as it does not yet know about them. It's not going to prevent zapis that exist in both zedi and 8.3 from working. Nor will it affect your abilities to run zapis with python or any language by hand. Before I share an example that works, a quick note on the page you linked: http://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discuss… It talks about how when iterating through xml, from a data collection perspective you can either get a list of all children, or get a child object given the name, but there is no clear documentation on how to get the content of an xml element. This is of course a requirement to get stuff done. I struggled with this initially as well, and that page explained it enough to me to get stuff working. It's not really a bug, more a lack of clear documentation on the calls you can do on elements. For example, if you have this: <share> <name>awesomeshare</name> <path>/project/location</path> </share> You can iterate through the share children and get objects for the name and path (the children_get() call), or you can pull the name object specifically with child_get('name'), but you want that 'awesomeshare', or that '/project/location' property value, not just an object for the property/value combination. The documentation (still?) lacks a clear indication on how to get the value inside of an xml element. Zulanch answers it: you do a object.element['content'] to get that inside information. The python sdk code itself has not really changed in years it looks like, as it's a convenient wrapper around builtin xml libraries and is expected to work in the same form for all zapis for the past years (decade?). Here's a basic working python script example that pulls data over zapi to get you going, using that .element call extensively; it at least works against 8.3.1. http://pastebin.com/Kpm6nJmq The example script is very basic and creates a python list of returned elements with a python dictionary of properties for each one, much easier to handle in python than the raw xml returned by the sdk. It's a scraper, it does not push changes. The script is not optimal, especially if elements get really deep, but should work for most queries and can easily be extended. I bet libraries like xmltodict can do this in a more scalable way, I'm doing all the work by hand in this example. At least the raw code should give you a very good idea on how to make zapi calls work in python. I also cover the max records part and do subsequent calls that start where the previous zapi response left off to get that comprehensive table of data. Notes on script: It takes a cluster mgmt ip or hostname, and a zapi call as input strings. It uses NaServer and NaElement to get the xml. It has the default max records of 20 set to keep pressure on the cluster low in maintaining records in memory before returning to clients (management processes do not like to do too much work, imagine them having to keep thousands of objects in memory, each with hundreds of properties before they can return them, while a dozen other management tools are hitting the same cluster against the same node that hosts the cluster mgmt lif. I don't want to be complicit in an api DOS of my own system when pulling inventory if I don't need to be), but will continue pulling 20 items sequentially until all items for a given zapi are pulled (in below example the items are shares, but it can also get volumes, aggregates, ports, disks, lifs etc. with the associated zapi) Below lines pull in the script, invoke the function and print the output. The script depends on a creds file with a username and password. The script expects the relevant user to have ontapi (at least read only) access. (or do things your own way and modify it to use certs instead). Maarten -------------------------- #!/usr/bin/env python from NcPullDictExample import api_dict output_array=api_dict('YOUR CLUSTER IP/HOSTNAME HERE','cifs-share-get-iter') #This iterates over the returned list, and shows each elements' properties, see example output below. for i in output_array: print(i) #Or get the whole list in one go: #printapi_dict('YOUR CLUSTER IP/HOSTNAME HERE','cifs-share-get-iter') -------------------------- creds file needed by the NcPullDictExample would simply contain something like below: -------------------------- user = 'apiuser' pw = 'hunter2' -------------------------- example output for the CIFS query. {'cifs-server': 'TESTVSERVER', 'share-properties': {'cifs-share-properties': 'browsable'}, 'vserver': 'testVserver', 'volume': 'testroot', 'path': '/', 'share-name': 'admin$', 'vscan-fileop-profile': 'standard', 'max-connections-per-share': '4294967295'} {'cifs-server': 'TESTVSERVER', 'share-properties': {'cifs-share-properties': 'changenotify'}, 'acl': {'string': 'BUILTIN\\Administrators / Full Control'}, 'vserver': 'testVserver', 'volume': 'testroot', 'path': '/', 'share-name': 'c$', 'symlink-properties': {'cifs-share-symlink-properties': 'enable'}, 'vscan-fileop-profile': 'standard', 'max-connections-per-share': '4294967295'} {'cifs-server': 'TESTVSERVER', 'share-properties': {'cifs-share-properties': 'browsable'}, 'vserver': 'testVserver', 'volume': 'testroot', 'path': '/', 'share-name': 'ipc$', 'vscan-fileop-profile': 'standard', 'max-connections-per-share': '4294967295'} On 10/29/2015 3:08 PM, Rue, Randy wrote: > No need for any apology, I'm grateful for any guidance at all, especially when you're doing actual work to try to figure this out for me. > > If I do need to specify the vserver that might explain why I get an empty return when I get a return at all. Will noodle with that. Also going to ask our NA representation about the API doc file for 1.30. > > Will keep you posted on any progress... > > Randy > > -----Original Message----- > From: Payne, Richard [mailto:richard.payne@amd.com] > Sent: Monday, October 26, 2015 1:56 PM > To: Rue, Randy; 'toasters(a)teaparty.net' > Subject: RE: python API guidance for cluster mode CIFS share reporting/management > > So I just tried some of this myself and the bad news is we don't have CIFS licenses. I tried running 'cifs-share-get-iter' (from perl) and it ran with success but of course returned nothing. > > " Also, the guidance I'm finding seems to revolve around viewing things on the cluster. At some point I'm also going to need to know how to change them" > > There's a cifs-share-modify, just keep in mind that works at the vserver context so you'll have to run a set_vserver on the NaServer object to change the context to the vserver. > > You may also want to try that for the cifs-share-get-iter call, the DOCs say it works under the cluster vserver context but not sure what it would return in cluster context (I assume all CIFS shares but I could be wrong there). > > Sorry I can't be of more help.... > > --rdp > > -----Original Message----- > From: Rue, Randy [mailto:rrue@fredhutch.org] > Sent: Thursday, October 22, 2015 11:40 AM > To: Payne, Richard; 'toasters(a)teaparty.net' > Subject: RE: python API guidance for cluster mode CIFS share reporting/management > > I'm running the 5.4 SDK, maybe (likely) this is a user (me) problem resulting from contact with a new API, XML. Etc. > > Can I break down a few weird things I'm seeing and hopefully you can point out what newbie thing I'm missing? > > When I first connect to the 8.3 cluster using ZEDI I get a warning "API Version: Ontapi 1.30 Cluster-Mode not listed. Please select the API Document manually." Is the cluster running a newer version than ZEDI? I can see where to select API documents in the ZEDI interface, and that 1.21 is the latest version offered for cluster-mode, and where to import a file for new documents. I can't find any sign online of where to get a file like what they appear to be looking for, or anything resembling it in the zip file I downloaded for the SDK. > > If I drill down to cifs-->cifs-share-get-iter, right-click and Generate, and then Execute, first I get an error in the XML output "<results reason='Invalid integer value for max-records: (null)' errno='13115' status='failed'/>" > > I can take the python from the Develop tab and run it in an IDE (after pasting in the password in text, yee-haw, I'll switch to cert authentication if this ever goes live), I get the same error in my output. > > If I plug in a value for max-records i.e. 10000 to the XML, in the XML tab I get what looks like a healthy return but with 0 records returned. But if I run the python code in my IDE I get "<results status="failed" errno="1" reason="Extra content at the end of the document "></results>" > > Also, the guidance I'm finding seems to revolve around viewing things on the cluster. At some point I'm also going to need to know how to change them. > > So how many glaring green oversights are listed above? > > Hope to hear from you, > > Randy > > > > -----Original Message----- > From: Payne, Richard [mailto:richard.payne@amd.com] > Sent: Thursday, October 22, 2015 5:40 AM > To: Rue, Randy; 'toasters(a)teaparty.net' > Subject: RE: python API guidance for cluster mode CIFS share reporting/management > > Hello, > > I've done a fair amount of work with the SDK though mostly using Perl, just started playing with Python. I guess the first thing is has this been fixed in the latest SDK release (5.4)? That post looks a couple of years old and there haves been a couple of SDK releases since then. I think technically 5.4 is to support 8.3.1 but it might be worth testing it. > > --rdp > > -----Original Message----- > From: toasters-bounces(a)teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Rue, Randy > Sent: Wednesday, October 21, 2015 6:12 PM > To: 'toasters(a)teaparty.net' > Subject: python API guidance for cluster mode CIFS share reporting/management > > Hello All, > > I'm working on automating the synchronizing of CIFS shares on the vservers of one 8.3 cluster to their DR mirrors on another cluster. It occurs to me that this might be useful to other shops so I'm trying to up my game from my usual fairly sloppy code i.e. http://xkcd.com/1513/ with lots of SSH calls to the CLI and parsing text output sequentially, to something portable and standard enough to share. > > Taking a look at the SDK/API with ZEDI as a guide to the objects involved and having a tough time getting started (never used much XML either). To make things muddier, the API I'm looking at "cifs-share-get-iter" apparently has a bug (http://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discuss…) that I don't totally get. Maybe if I could understand the object as it's supposed to work first. > > Any experience with the API? Looks like it's a few years old, is it used with 8.3? > > Hope to hear from you, > > Randy in Seattle > > > > > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > http://www.teaparty.net/mailman/listinfo/toasters > > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > http://www.teaparty.net/mailman/listinfo/toasters

1 0

Anybody using OnCommand Performance Manager (OPM)?
by Rue, Randy 29 Oct '15

29 Oct '15

Our new 8.3 cluster is in production, finished migrating the last vservers to it last weekend, and suddenly we're getting ~6 alerts a day from an OPM server set up by a co-worker who's left the organization. I confess I've barely looked at the thing until now. Whenever I go to investigate the details of the latest "incident" I find that it's not a problem, i.e. latency on a volume "jumped" from <1ms to ~5ms. Looks like the application is looking for deviation from a dynamically determined baseline and I'm not seeing any option for tweaking parameters or limits. Six false alarms a day makes this effectively useless. Anybody else using this app? Got any tips on making it useful? Randy

4 4

python API guidance for cluster mode CIFS share reporting/management
by Rue, Randy 29 Oct '15

29 Oct '15

Hello All, I'm working on automating the synchronizing of CIFS shares on the vservers of one 8.3 cluster to their DR mirrors on another cluster. It occurs to me that this might be useful to other shops so I'm trying to up my game from my usual fairly sloppy code i.e. http://xkcd.com/1513/ with lots of SSH calls to the CLI and parsing text output sequentially, to something portable and standard enough to share. Taking a look at the SDK/API with ZEDI as a guide to the objects involved and having a tough time getting started (never used much XML either). To make things muddier, the API I'm looking at "cifs-share-get-iter" apparently has a bug (http://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discuss…) that I don't totally get. Maybe if I could understand the object as it's supposed to work first. Any experience with the API? Looks like it's a few years old, is it used with 8.3? Hope to hear from you, Randy in Seattle

3 5

AW: AW: Used Replacement disk not recognized
by Alexander Griesser 29 Oct '15

29 Oct '15

Hey, this did work, indeed – at least the disk could be unfailed with `disk unfail –s` here on 8.1.4 in a different filer; I’m currently zeroing them and will then remove_ownership and bring them back to the older filer. Thanks for your help! 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 Von: andrei.borzenkov(a)ts.fujitsu.com [mailto:andrei.borzenkov@ts.fujitsu.com] Gesendet: Samstag, 24. Oktober 2015 10:08 An: Alexander Griesser <AGriesser(a)anexia-it.com> Cc: toasters(a)teaparty.net Betreff: Re: AW: Used Replacement disk not recognized Assuming it is indeed too new label (it does not look exactly as one) your options are - update to 8.0.2 or above and use "disk unfail -s" - put disk in filer with newer version and make it zeroed unowned spare Messing with labels directly is unlikely going to help. https://kb.netapp.com/support/index?page=content&id=2011366&locale=en_US Отправлено с iPhone 23 окт. 2015 г., в 21:45, Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>> написал(а): Alright, but now I do have a label issue I guess ☺ An even older filer (FAS2040, OnTap 8.0.1P2 7-Mode) is writing this to the log when I insert one of the refurbished disks: Fri Oct 23 20:24:52 CEST [megatron: raid.disk.missing:info]: Disk 0d.01.5 Shelf 1 Bay 5 [NETAPP X410_HVIPC288A15 NA00] S/N [JXV0TL2J] is missing from the system Fri Oct 23 20:26:52 CEST [megatron: diskown.changingOwner:info]: changing ownership for disk 0d.01.5 (S/N JXXDSRMJ) from unowned (ID 4294967295) to megatron (ID 142227074) Fri Oct 23 20:26:52 CEST [megatron: raid.assim.disk.nolabels:error]: Disk 0d.01.5 Shelf 1 Bay 5 [NETAPP X410_HVIPC288A15 NA02] S/N [JXXDSRMJ] has no valid labels. It will be taken out of service to prevent possible data loss. Fri Oct 23 20:26:52 CEST [megatron: raid.config.disk.bad.label:error]: Disk 0d.01.5 Shelf 1 Bay 5 [NETAPP X410_HVIPC288A15 NA02] S/N [JXXDSRMJ] has bad label. Fri Oct 23 20:26:52 CEST [megatron: callhome.dsk.label:CRITICAL]: Call home for DISK BAD LABEL Fri Oct 23 20:27:00 CEST [megatron: monitor.globalStatus.nonCritical:warning]: Disk on adapter 0d, shelf 1, bay 5, failed. I guess this means that I will have to erase the label here, correct? aggr status -r Broken disks RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- bad label 0d.01.5 0d 1 5 SA:B 0 SAS 15000 272000/557056000 274845/562884296 Best, 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 Von: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] Im Auftrag von Alexander Griesser Gesendet: Donnerstag, 22. Oktober 2015 16:55 An: andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com>; toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: AW: Used Replacement disk not recognized Many thanks! riddler> vol status -s Pool1 spare disks (empty) Pool0 spare disks RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks) --------- ------ ------------- ---- ---- ---- ----- -------------- -------------- Spare disks for block checksum spare 0d.01.13 0d 1 13 SA:B 0 BSAS 7200 847555/1735794176 847884/1736466816 spare 0d.03.22 0d 3 22 SA:B 0 BSAS 7200 847555/1735794176 847884/1736466816 I’m up and running ☺ Best, 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 Von: andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com> [mailto:andrei.borzenkov@ts.fujitsu.com] Gesendet: Donnerstag, 22. Oktober 2015 16:52 An: Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>>; toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: RE: Used Replacement disk not recognized disk assign 0d.01.13 -f --- With best regards Andrei Borzenkov Senior system engineer FTS WEMEAI RUC RU SC TMS FOS <image001.gif> FUJITSU Zemlyanoy Val Street, 9, 105 064 Moscow, Russian Federation Tel.: +7 495 730 62 20 ( reception) Mob.: +7 916 678 7208 Fax: +7 495 730 62 14 E-mail: Andrei.Borzenkov(a)ts.fujitsu.com<mailto:Andrei.Borzenkov@ts.fujitsu.com> Web: ru.fujitsu.com<http://ts.fujitsu.com/> Company details: ts.fujitsu.com/imprint<http://ts.fujitsu.com/imprint.html> This communication contains information that is confidential, proprietary in nature and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation. Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission. From: Alexander Griesser [mailto:AGriesser@anexia-it.com] Sent: Thursday, October 22, 2015 5:50 PM To: Borzenkov, Andrei; toasters(a)teaparty.net<mailto:toasters@teaparty.net> Subject: AW: Used Replacement disk not recognized Bingo: riddler> disk show -v DISK OWNER POOL SERIAL NUMBER HOME CHKSUM ------------ ------------- ----- ------------- ------------- ------ 0d.01.13 w-nas-04 (142255463) Pool0 J838WSRL w-nas-04 (142255463) Block „w-nas-04“ is none of my filers – so I need to remove the ownership here now, I guess. riddler*> disk remove_ownership 0d.01.13 -f disk remove_ownership: Disk 0d.01.13 is not owned by this node. riddler*> disk reassign -o w-nas-04 -n riddler disk reassign: Can only be run in maintenance mode or during takeover in advanced mode riddler*> So, I guess I have to – again – boot into maintenance mode or is there a trick which would allow me to remove the ownership without having to shut everything down again? Best, 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 Von: andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com> [mailto:andrei.borzenkov@ts.fujitsu.com] Gesendet: Donnerstag, 22. Oktober 2015 16:47 An: Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>>; toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: RE: Used Replacement disk not recognized Does it appear in “disk show -v”? --- With best regards Andrei Borzenkov Senior system engineer FTS WEMEAI RUC RU SC TMS FOS <image001.gif> FUJITSU Zemlyanoy Val Street, 9, 105 064 Moscow, Russian Federation Tel.: +7 495 730 62 20 ( reception) Mob.: +7 916 678 7208 Fax: +7 495 730 62 14 E-mail: Andrei.Borzenkov(a)ts.fujitsu.com<mailto:Andrei.Borzenkov@ts.fujitsu.com> Web: ru.fujitsu.com<http://ts.fujitsu.com/> Company details: ts.fujitsu.com/imprint<http://ts.fujitsu.com/imprint.html> This communication contains information that is confidential, proprietary in nature and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation. Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission. From: Alexander Griesser [mailto:AGriesser@anexia-it.com] Sent: Thursday, October 22, 2015 5:44 PM To: Borzenkov, Andrei; toasters(a)teaparty.net<mailto:toasters@teaparty.net> Subject: AW: Used Replacement disk not recognized Hi Andrei, the last command states „Disk 0d.01.13 does not exist“, I don’t think that this is cool… The problem is that even after the reboot, the disk does not show up anywhere except for sysconfig or storage show disk. Best, 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 Von: andrei.borzenkov(a)ts.fujitsu.com<mailto:andrei.borzenkov@ts.fujitsu.com> [mailto:andrei.borzenkov@ts.fujitsu.com] Gesendet: Donnerstag, 22. Oktober 2015 16:41 An: Alexander Griesser <AGriesser(a)anexia-it.com<mailto:AGriesser@anexia-it.com>>; toasters(a)teaparty.net<mailto:toasters@teaparty.net> Betreff: RE: Used Replacement disk not recognized Firmware is not older or newer – those two disks are from different manufacturers so they have different firmware; both are using the latest versions publically available. KB https://kb.netapp.com/support/index?page=content&id=2010827&locale=en_US&ac… implies that Drive spinning up may be seen with X302 and is otherwise harmless, although there are so many different variants of X302 it is hard to guess whether it applies in your case. I would suggest open the case. Last command you pasted suggests that everything is OK now; or what is remaining problem? --- With best regards Andrei Borzenkov Senior system engineer FTS WEMEAI RUC RU SC TMS FOS <image001.gif> FUJITSU Zemlyanoy Val Street, 9, 105 064 Moscow, Russian Federation Tel.: +7 495 730 62 20 ( reception) Mob.: +7 916 678 7208 Fax: +7 495 730 62 14 E-mail: Andrei.Borzenkov(a)ts.fujitsu.com<mailto:Andrei.Borzenkov@ts.fujitsu.com> Web: ru.fujitsu.com<http://ts.fujitsu.com/> Company details: ts.fujitsu.com/imprint<http://ts.fujitsu.com/imprint.html> This communication contains information that is confidential, proprietary in nature and/or privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) or the person responsible for delivering it to the intended recipient(s), please note that any form of dissemination, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender and delete the original communication. Thank you for your cooperation. Please be advised that neither Fujitsu, its affiliates, its employees or agents accept liability for any errors, omissions or damages caused by delays of receipt or by any virus infection in this message or its attachments, or which may otherwise arise as a result of this e-mail transmission. From: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] On Behalf Of Alexander Griesser Sent: Thursday, October 22, 2015 5:06 PM To: toasters(a)teaparty.net<mailto:toasters@teaparty.net> Subject: Used Replacement disk not recognized Hey everybody, I just had the pleasure to try to replace a faulty disk in a filer which is out-of-service with a „new“ one from after market. Of course, this didn’t work out as easy as it should, so maybe some could help me get this disk going. Here are the facts: FAS2040 NetApp Release 8.1.4P8 7-Mode The disk at 0d.01.13 was broken, so I pulled it a few days ago – now that the replacment disk has arrived, I tried to plug it in and this is what happens: Thu Oct 22 14:30:10 CEST [riddler:scsi.cmd.notReadyCondition:notice]: Disk device 0d.01.13: Device returns not yet ready: CDB 0x1b: Sense Data SCSI:not ready - Drive spinning up (0x2 - 0x4 0x1 0x28)(2). The interesting thing, I can see the disk by using `storage show disk`: riddler> storage show disk DISK SHELF BAY SERIAL VENDOR MODEL REV --------------------- --------- ---------------- -------- ---------- ---- 0d.01.13 1 13 J838WSRL NETAPP X302_HJUPI NA04 But I cannot see it in disk show. riddler> disk show 0d.01.13 DISK OWNER POOL SERIAL NUMBER HOME ------------ ------------- ----- ------------- ------------- Sysconfig –v tells me, that there is a newer firmware on the „new“ disk: 01.13: NETAPP X302_HJUPI01TSSM NA04 847.5GB (1953525168 512B/sect) 01.14: NETAPP X302_WVULC01TSSA NA03 847.5GB (1953525168 512B/sect) So I first tried to downgrade firmware using: disk_fw_update –R 0d.01.13 but that did not really work out, no error message, but just no change on the firmware of the disk – also nothing in the logs. So I read somewhere that this might be due to a bad/incompatible label on the disk and found out that the only way to get rid of the label is to boot into maintenance mode (thus having a downtime of parts of the HA-pair :-/) and recreate the label there. So I booted into maintenance mode and have run the following command: *> label makespare 0d.01.13 ********************************************************* Label editing is highly dangerous and should be attempted ONLY by NetApp Customer Support Engineers. Misuse can cause ALL data to be permanently lost. ********************************************************* 'Label save': Error while trying to save Label 1 on disk 0d.03.22: error 15. Label save: 1 of 35 disks could not save Label 1. 'Label save': Error while trying to save Label 2 on disk 0d.03.22: error 15. Label save: 1 of 35 disks could not save Label 2. The current set of labels on the disks have been saved. You can use the 'label restore' command to revert to these labels, the 'label keep' command to erase these labels, or 'label save' to preserve the current set of labels. ********************************************************* *** Run WAFL recovery tools (wafliron or wafliron_oc) after this. *** Disk 0d.01.13 does not exist. The last line suggests, that the disk still does not get recognized properly – and additionally, it (for whatever reason) claims to not be able to write the label 1 on disk 0d.03.22, although this is there and online: riddler> disk show 0d.03.22 DISK OWNER POOL SERIAL NUMBER HOME ------------ ------------- ----- ------------- ------------- 0d.03.22 riddler (142248200) Pool0 N002XRML riddler (142248200) I’ve stopped my expiriments at this point and am very thankful for fresh ideas ☺ Best, 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 Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 _______________________________________________ Toasters mailing list Toasters(a)teaparty.net<mailto:Toasters@teaparty.net> http://www.teaparty.net/mailman/listinfo/toasters

1 0

Jump to page:

2026

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