toasters November 2015

toasters@lists.teaparty.net

28 participants
13 discussions

FDMI reporting with qla2xxx driver on Linux
by Momonth 09 Dec '16

09 Dec '16

Hi, I recently noticed that qla2xxx (Qlogic HBAs) driver on Linux is capable of reporting FDMI. By default it sends "Linux-default", and I'm failing to see how to change it to actual host name as it becomes way more handy then =) Any ideas? Cheers, Vladimir

2 3

NetApp API authentication
by Edward Rolison 01 Mar '16

01 Mar '16

Having started to review some of our filer automation scripts, I'm starting to look in a bit more detail at the API. My first conclusion is - the perl SDK doesn't actually seem to do anything much - it seems to be a reimplementation of LWP and and XML Parser. Given I have LWP and XML::Twig installed, and am making API calls just fine, is there anything I'm missing here? Aside from that though - authentication types. I currently use ssh public-private key pairs, in a trusted account on a management station to enable 'doing stuff' with filers. It _looks_ like my only option with the API is to create a designated service account, and assign permissions... and then embed a username and password in a script somewhere. That just doesn't sit well with me - I like what ssh-agent will do in 'unlocking' key files, and I don't like embedding (potentially privileged) usernames and passwords ... anywhere. Does anyone have a better solution than a couple of designated API users (privileged and read only) with a file somewhere embedding their username and password? Does anyone have a better approach?

5 5

CentOS 6.7 + cDOT 8.3.1: kernel: scsi: host X channel Y id Z lun4194304 has a LUN larger than allowed by the host adapter
by Momonth 04 Jan '16

04 Jan '16

Hi, Before I take a long journey with NetApp support, let me ask you guys. I have CentOS 6.7 server and I'm trying to attach a cDOT LUN to it as path discovery fails with: kernel: scsi: host 0 channel 3 id 0 lun4194304 has a LUN larger than allowed by the host adapter However it only fails with the message above for one HBA out of two installed into the server. The HBAs (drivers, firmware etc) are identical. The HBA are Qlogic relabeled as HP. So RedHat has a KB article for it https://access.redhat.com/solutions/67157 and it's advised to contact storage appliance vendor. I've seen that once, it was due to some FW files being absent under /lib/firmware, it's not the same this time. Has anyone seen that before? Cheers, Vladimir

3 20

NETAPP TOASTERS FACEBOOK GROUP HAS BEEN CREATED
by Milazzo Giacomo 24 Nov '15

24 Nov '15

Hi everybody, don't you think that time for mail newsgroup have passed? I think so. https://www.facebook.com/groups/netapptoasters/ I've just created a new group on Facebook and named it "NetApp Toasters". I've also mutuated from the LinkedIn logo I've designed years ago a new one. And I please NetApp to let me use their own as header. I know that this could be another YAST where s stands for support :) ... but considering that NetApp mailing list is active since years maybe this group could be. Many advantages can be useful on using a FB group to share infos and comments and, moreover, to enclose same discussions in just one thread. I'm alone with a few guys managing a group that I hope will grow on a daily base, so please be patient if your admission request could take one hour such one day. Of course we all are professionals and any kind of content unpolite or inappropriate will be removed by the incontestable judgement of administrators. Thank you in advance if you'll appreciate it. My best regards, PS) netapptoasters(a)groups.facebook.com<mailto:netapptoasters@groups.facebook.com> mail sent to this address will be addressed as post...but not sure about this Dott. Giacomo Milazzo Senior Consultant & Technical Account Manager mobile: +39 340.6001045 @-mail: g.milazzo(a)sinergy.it<mailto:g.milazzo@sinergy.it> Web: http://www.sinergy.it<http://www.sinergy.it/> [cid:4DB1B876-8A76-4829-9B40-9B136E344F73@fastwebnet.it] SINERGY SpA Viale dei Santi Pietro e Paolo 50 00144 - Roma RM Tel. +39 06 44243674 Fax +39 06 44245272

9 11

Re: R: NETAPP TOASTERS FACEBOOK GROUP HAS BEEN CREATED
by Mark Flint 24 Nov '15

24 Nov '15

No thanks, I prefer direct mail. Mark From: <toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net>> on behalf of Milazzo Giacomo <G.Milazzo(a)sinergy.it<mailto:G.Milazzo@sinergy.it>> Date: Tuesday, 24 November 2015 at 10:47 To: Toasters <toasters(a)teaparty.net<mailto:toasters@teaparty.net>> Subject: R: NETAPP TOASTERS FACEBOOK GROUP HAS BEEN CREATED As answer (to the few until now) that have expressed their opinions about that FB page I want to clarify that this does not want to substitute at all the mailing list. I can understand some of the reasons and this would be just a kind of experimental startup. On the other hands, if not with a free and quite easy to setup FB page, WHO should take the weight to create some “forum” page that could be better that a mailing list? In all these years I’ve not seen a forum page and, after all, NetApp community pages do their job well. Until now FC page has been joined by roughly 40 members, some of them from NetApp too. We’ll see it. In the main time everybody is free to open new threads wherever he/she wants. Regards. Da: toasters-bounces(a)teaparty.net<mailto:toasters-bounces@teaparty.net> [mailto:toasters-bounces@teaparty.net] Per conto di Milazzo Giacomo Inviato: martedì 24 novembre 2015 01:10 A: Toasters <toasters(a)teaparty.net<mailto:toasters@teaparty.net>> Oggetto: NETAPP TOASTERS FACEBOOK GROUP HAS BEEN CREATED Hi everybody, don’t you think that time for mail newsgroup have passed? I think so. https://www.facebook.com/groups/netapptoasters/ I’ve just created a new group on Facebook and named it “NetApp Toasters”. I’ve also mutuated from the LinkedIn logo I’ve designed years ago a new one. And I please NetApp to let me use their own as header. I know that this could be another YAST where s stands for support ☺ … but considering that NetApp mailing list is active since years maybe this group could be. Many advantages can be useful on using a FB group to share infos and comments and, moreover, to enclose same discussions in just one thread. I’m alone with a few guys managing a group that I hope will grow on a daily base, so please be patient if your admission request could take one hour such one day. Of course we all are professionals and any kind of content unpolite or inappropriate will be removed by the incontestable judgement of administrators. Thank you in advance if you’ll appreciate it. My best regards, PS) netapptoasters(a)groups.facebook.com<mailto:netapptoasters@groups.facebook.com> mail sent to this address will be addressed as post…but not sure about this Dott. Giacomo Milazzo Senior Consultant & Technical Account Manager mobile: +39 340.6001045 @-mail: g.milazzo(a)sinergy.it<mailto:g.milazzo@sinergy.it> Web: http://www.sinergy.it<http://www.sinergy.it/> [cid:4DB1B876-8A76-4829-9B40-9B136E344F73@fastwebnet.it] SINERGY SpA Viale dei Santi Pietro e Paolo 50 00144 - Roma RM Tel. +39 06 44243674 Fax +39 06 44245272

1 0

teamctr volume
by Paul Letta 19 Nov '15

19 Nov '15

teamctn_vols is the name of the volume on cfs1a that holds your volume. \\cfs1a\tcvols maps to this area. Current usage is 286GB out of 450GB. So plenty of space. There are no quotas turned on for this volume. Paul

1 0

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

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 November 2015