toasters

toasters@lists.teaparty.net

13531 discussions

Re: pNFS
by Michael Bergman 17 Aug '21

17 Aug '21

On 2021-08-17 14:26, Justin Parisi wrote: > NFSv4.1 performance is nearly identical to v3 in ONTAP for sequential > reads/writes. The performance issues mostly come from high metadata > workloads. If you do want to use v4.1, move to ONTAP 9.9.1 and the latest > Linux kernels you can. Yes. And therein lies the problem. Anything which has many files (high inode density), many open() and close() operations and lots of deletes of [small] files will suffer significantly (higher processing util in WAFL and extra latency) from using v4.1 The current performance penalties in v4.1 w.r.t. ONTAP compared to v3, are not easy to fix. Maybe something can be done inside ONTAP to mitigate but it's never going to "go away" easily to become on par overall with v3 performance any day soon. Metadata ops (esp GETATTRv3) is very very optimised in ONTAP in v3, for example I agree 100%: use 9.1.1 (latest stable Px whatever it is) and make sure that you have the latest Linux [kernel] version(s) you possibly can. It will help. (One of the very latest is highly preferable.) If you want to get proper enterprise level support, then use the latest RHEL 8.x, keep it well patched all the time, and you'll at least lower the risk if having issues. If you have a specific application system(s), e.g. one which really depends on v4.1 ACLs (I have yet to hear about such an animal that isn't esoteric) or some other feature v3 doesn't have (there aren't many IMO) then you can probably "contain", and hence control that environment much better including the involved NFS clients. If not... caveat emptor. /M -- Michael Bergman Sr Systems Analyst / Storage Architect michael.bergman(a)ericsson.com BNEW Service Area Networks, Lab Ops Phone +46 10 7152945 Global Network & Tech, Architecture SMS/MMS +46 70 5480835 Ericsson Torshamnsg 36, 16480 Sthlm, Sweden -- This communication is confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer

1 0

Re: pNFS
by Michael Bergman 17 Aug '21

17 Aug '21

On 2021-08-17 14:23, Justin Parisi wrote: > Referrals probably have the same issue. Will need to test when I get back > into the office. Unless you seek to eliminate/avoid, all CI (Cluster Interconnect) traffic at all cost, I don't really see that that fact matters too much [at mount time]. (Good point about FlexGroups though... I don't have a good solid solution for those scenarios) We have since long (years) strived to avoid CI traffic as much as we can, but we're not as diligent anymore. Note: we do *not* use that DNS function ONTAP has in it which is intended to help spreading all the traffic (mount from clients) to various LIFs (based on the "load" on the nblades). Again, this takes place at mount time, once a mounts sits on a LIF it stays there... That DNS function (it is based on an algorithm using various "weights") suffers from serious drawbacks in some situations and we can't take that risk in our environment. Anyone who has seen and experienced a "mount storm" will know what I mean. How important locality is (minimal CI traffic) for you I guess can depend a bit on what model/power of CI switch you have. If there's enough bandwidth for the workload streams going across it, it only induces a little extra latency -- that may matter for some workloads, but I'd argue that for most it won't. Once you're on CI switch with 100 GbE, my take is that most people don't have to bother that much about it. With 100 GbE the latency is lower as well /M Justin Parisi wrote: > But referrals only help with initial mount; after the mount is established, > the connections stay where they were established. If a volume moves to a new > node, that doesn't keep locality. They're also not much help with FlexGroup > volumes. >

1 0

Re:
by Parisi, Justin 17 Aug '21

17 Aug '21

Nconnect can help with some performance issues, provided the performance issues are related to things that nconnect can help with - such as slot table exhaustion or a single TCP connection that has maxed out what it can do bandwidth wise. NFSv4.1 performance is nearly identical to v3 in ONTAP for sequential reads/writes. The performance issues mostly come from high metadata workloads. If you do want to use v4.1, move to ONTAP 9.9.1 and the latest Linux kernels you can. ________________________________ From: Toasters <toasters-bounces(a)teaparty.net> on behalf of Michael Bergman via Toasters <toasters(a)teaparty.net> Sent: Tuesday, August 17, 2021 7:57 AM To: Toasters Subject: NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. _______________________________________________ Toasters mailing list Toasters(a)teaparty.net https://www.teaparty.net/mailman/listinfo/toasters

1 0

Re: pNFS
by Sebastian Goetze 17 Aug '21

17 Aug '21

Hi Justin, I'm wondering: Does that also go for *referrals*? Would the IP returned to the client respect the incoming LIF's Broadcast Domain and return the IP of a LIF in the same BD? Or should you refrain from referrals in that situation, too? I checked TR-4067, but didn't find a mention about that. @Florian: Could be, that NFS4.0/4.1 referrals are the solution to keeping your paths local, especially, if your volumes do not move around... Sebastian On 16.08.2021 18:41, Parisi, Justin via Toasters wrote: FYI TR-4067 calls out this exact issue as well. There’s currently no way to “blacklist” inelegible interfaces for pnfs. If it’s in the SVM, it will be used with pNFS, regardless of if it’s reachable. We have an open RFE to allow you to specify LIFs for pNFS to avoid this problem. In the meantime you can blacklist devices from the client as per page 54 of the tr. > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters

2 1

Re: pNFS not working on vserver when several lifs with different Vlans available
by Florian Schmid 17 Aug '21

17 Aug '21

Hello Michael, may I ask which version of NFS are you using in your environment and what problems have you had with NFSv4.1? Especially the performance ones. Best regards Florian

1 0

Re:
by Tim McCarthy 17 Aug '21

17 Aug '21

Ain’t that the truth! I had a customer using 18 month old red hat kernels (not patch for a long time) They upgraded ontap to something modern and either did not realize (likely) or forgot they were using nfs v4.1/pnfs. As soon as ontap finished the boot of the last node to the latest version, ALL the rhel boxes panicked. Upon review it was due to a bug fixed 15 months ago in the kernel. The fix was simple, Chang the mounts to v3. So sane thought, if you go down the 4.1 path it is best to keep everything current both client and server to avoid nasty bugs Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Toasters <toasters-bounces(a)teaparty.net> on behalf of Michael Bergman via Toasters <toasters(a)teaparty.net> Sent: Tuesday, August 17, 2021 7:52:28 AM To: Toasters <toasters(a)teaparty.net> Subject: _______________________________________________ Toasters mailing list Toasters(a)teaparty.net https://www.teaparty.net/mailman/listinfo/toasters

1 0

Re: pNFS
by Michael Bergman 17 Aug '21

17 Aug '21

On 2021-08-17 12:44, Sebastian Goetze wrote: > @Florian: Could be, that NFS4.0/4.1 referrals are the solution to keeping > your paths local, especially, if your volumes do not move around... I concur, could be. We almost don't use NFSv4.1 at all (yet) for various reasons one main being performance issues due to the nature of our heavy NFS workloads W.r.t. performance in the NFS clients, if that's a worry, nconnect=x available in later kernels (e.g. in RHEL 8.x) can help speed things up. Quite a lot. It depends on the workload patterns you have. pNFS is interesting and can be good for certain applications and their workloads but it's cumbersome to work with and get to work smoothly. The clients running pNFS have been more the problem to get to behave well, in the past years at least. Nowadays w e.g. RHEL 8.x, possibly it's better. I would say it's still a VERY good idea that *all* your pNFS clients are exactly the same Linux kernel and version. I.e. the same distro and version of it. If you can't build such an environment, I'd recommend to refrain from using pNFS and try to mitigate any perceived or proven performance bottlenecks in other ways (e.g. nconnect=x can help, and a better different scale out config of a new ONTAP cluster, large FlexGroup(s) etc) /M

1 0

Re: pNFS not working on vserver when several lifs with different Vlans available
by Florian Schmid 17 Aug '21

17 Aug '21

Good morning, thank you very much for all those replys. I really haven't thought that :) Yes, our network wasn't designed for pNFS at all, because we have never used it. We have started now to use clients, which are using this by default and we have encountered this problem. Our storage network was ever only switched, so no routing is/was possible and we always had to choose the right IP range for the client and node. We also normally don't have huge clusters, so no volume movement either. But I have really thought, that the pNFS implementation is at least broadcast domain aware, but it seems it isn't. This means, that pNFS is not working in our environment. That's ok for us. Thanks a lot for the deeper insight you all have given me. Best regards Florian Schmid

1 0

Re: pNFS not working on vserver when several lifs with different Vlans available
by Michael Bergman 16 Aug '21

16 Aug '21

On 2021-08-16 18:41, Justin Parisi wrote: > I think it was "working as designed." RFE is several years old; filed it > when I was still in support. It is. Working as designed. That's my take on this. Meaning: if you misunderstand things a bit and design your network around the cluster intended to run and leverage pNFS in such a way that doesn't make sense really, you'll have to turn pNFS off and then it'll work again for the clients. Back to the drawing board, re-design the network e.g. move your LIFs around so that they're all in the same VLAN (subnet). We don't run pNFS anywhere, but that's the customary way we do it for our very large clusters (our biggest is a 20-node now, in refresh state b/w 5 y old FAS8080 and new A800) in any case, since many years. And *everything*, all NFS traffic, always goes across at least one L3 hop. Nothing else, no NFS clients!, are allowed in the VLANs where our LIFs sit. That way we "own" that VLAN completely and can control it in a good fashion. BTW: Wow. A several years old RFE from *you* who hasn't been implemented yet. Not much demand for it then I'd say /M -------- Original Message -------- Subject: Re: pNFS not working on vserver when several lifs with different Vlans available Date: Mon, 16 Aug 2021 12:17:45 -0400 From: tmac <tmacmd(a)gmail.com> To: Parisi, Justin <Justin.Parisi(a)netapp.com> CC: Michael Bergman <michael.bergman(a)ericsson.com>, Toasters <toasters(a)teaparty.net> Wow...Thanks Justin. I guess that was possibly an oversight when developed (and hence the RFE)? --tmac *Tim McCarthy, */Principal Consultant/ *Proud Member of the #NetAppATeam *I Blog at TMACsRack

1 0

Re:
by tmac 16 Aug '21

16 Aug '21

Wow...Thanks Justin. I guess that was possibly an oversight when developed (and hence the RFE)? --tmac *Tim McCarthy, **Principal Consultant* *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>* *I Blog at TMACsRack <https://tmacsrack.wordpress.com/>* On Mon, Aug 16, 2021 at 12:09 PM Parisi, Justin via Toasters < toasters(a)teaparty.net> wrote: > > > > ---------- Forwarded message ---------- > From: "Parisi, Justin" <Justin.Parisi(a)netapp.com> > To: Michael Bergman <michael.bergman(a)ericsson.com>, Toasters < > toasters(a)teaparty.net> > Cc: > Bcc: > Date: Mon, 16 Aug 2021 16:06:37 +0000 > Subject: Re: > FYI TR-4067 calls out this exact issue as well. There’s currently no way > to “blacklist” inelegible interfaces for pnfs. If it’s in the SVM, it will > be used with pNFS, regardless of if it’s reachable. > > We have an open RFE to allow you to specify LIFs for pNFS to avoid this > problem. In the meantime you can blacklist devices from the client as per > page 54 of the tr. > > https://www.netapp.com/pdf.html?item=/media/10720-tr-4067.pdf > ------------------------------ > *From:* Toasters <toasters-bounces(a)teaparty.net> on behalf of Michael > Bergman via Toasters <toasters(a)teaparty.net> > *Sent:* Monday, August 16, 2021 11:10:12 AM > *To:* Toasters <toasters(a)teaparty.net> > *Subject:* > > NetApp Security WARNING: This is an external email. Do not click links or > open attachments unless you recognize the sender and know the content is > safe. > > > > > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters > > > > ---------- Forwarded message ---------- > From: "Parisi, Justin via Toasters" <toasters(a)teaparty.net> > To: Michael Bergman <michael.bergman(a)ericsson.com>, Toasters < > toasters(a)teaparty.net> > Cc: > Bcc: > Date: Mon, 16 Aug 2021 17:06:46 +0100 > Subject: > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters

2 1

Re:
by Parisi, Justin 16 Aug '21

16 Aug '21

FYI TR-4067 calls out this exact issue as well. There’s currently no way to “blacklist” inelegible interfaces for pnfs. If it’s in the SVM, it will be used with pNFS, regardless of if it’s reachable. We have an open RFE to allow you to specify LIFs for pNFS to avoid this problem. In the meantime you can blacklist devices from the client as per page 54 of the tr. https://www.netapp.com/pdf.html?item=/media/10720-tr-4067.pdf ________________________________ From: Toasters <toasters-bounces(a)teaparty.net> on behalf of Michael Bergman via Toasters <toasters(a)teaparty.net> Sent: Monday, August 16, 2021 11:10:12 AM To: Toasters <toasters(a)teaparty.net> Subject: NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe. _______________________________________________ Toasters mailing list Toasters(a)teaparty.net https://www.teaparty.net/mailman/listinfo/toasters

1 0

Re: pNFS not working on vserver when several lifs with different Vlans available
by Michael Bergman 16 Aug '21

16 Aug '21

Exactly. I was too terse in my reply. Plus a blurry distinction b/w "striped" and "distributed". Where one can argue (as you did) that striping is a special case of distribution. Which it is, I agree As for the metadata server concept in pNFS see some details here: <https://datatracker.ietf.org/doc/html/rfc8434#section-12> There is, conceptually, one (1) metadata server. It has to keep track of a whole bunch of things, the clients *must* talk NFSv4.1 to it and it has to control the so called layouts that pNFS clients are given. Or revoke layouts when and if applicable. The ONTAP implementation may "stripe" the metadata server (!) ;-) somehow, but still. I really don't know -- pNFS is cumbersome to set up and I have no incentive (or interest) to do it in any strong enough use case we have for our internal Storage Service An excerpt from the above doc: data server (DS): a pNFS server that provides the file's data when the file system object is accessed over a file-based protocol. Note that this usage differs from that in [RFC5661], which applies the term in some cases even when other sorts of protocols are being used. Depending on the layout, there might be one or more data servers over which the data is striped. While the metadata server is strictly accessed over the NFSv4.1 protocol, the data server could be accessed via any file access protocol that meets the pNFS requirements. metadata server (MDS): the pNFS server that provides metadata information for a file system object. It is also responsible for generating, recalling, and revoking layouts for file system objects, for performing directory operations, and for performing I/O operations to regular files when the clients direct these to the metadata server itself. See also <http://www.pnfs.com/> Again: how ONTAP implements the metadata server, I'm not sure. Presumably in a scale-out way, as cleverly as possible with the technology available to NetApp already in ONTAP. There has been (still is..?) ideas on how to in a fully standardised way stripe the metadata server function across many devices as well, but I'm not clear on the current status of this. I only find old references now (really old, 5+ y): <https://datatracker.ietf.org/doc/html/draft-mbenjamin-nfsv4-pnfs-metastripe…> Maybe I'm missing something, comments welcome. I also stumbled across this [URL below], it's 10+ y old but I've never seen this before. It was an interesting read; so many things have taken place and become mature in the past decade of the stuff which is mentioned in this slide pack. Not bad, NetApp :-) It took a wee bit longer than we all wanted, sure, but it works and one can trust it in a VERY BIG system (cluster). <http://www.nfsv4bat.org/Documents/ConnectAThon/2010/wafl-unstriped.pdf> /M On 2021-08-16 16:22, tmac wrote: Just out of curiosity, what is the output of "network interface show -vserver pnfs-svm" The answer might lie there. I doubt it is a VLAN issue and more a network design issue. I found this: https://mysupport.netapp.com/site/article?lang=en&page=%2FAdvice_and_Troubl… Issue * When NFS client attempts to Read/Write to the SVM with pNFS enabled, the operation hangs, with "nfs: [LIF address / hostname] server not responding" in /var/log/messages. Cause * This issue occurs in situations where pNFS is enabled on an SVM and there are LIFs created in different subnets, which are non-routable by the client * Data ONTAP may provide any LIF which belong's to the same SVM as the referral to a client * The Read/Write operation hangs because the data LIF IP is not reachable by the client Solution * Make sure clients can reach all data LIFs of the SVM -or- * Disable support for pNFS on the SVM ::> nfs modify -v4.1-pnfs disabled --tmac Tim McCarthy, Principal Consultant Proud Member of the #NetAppATeam I Blog at TMACsRack

1 0

Re:
by tmac 16 Aug '21

16 Aug '21

Just out of curiosity, what is the output of "network interface show -vserver pnfs-svm" The answer might lie there. I doubt it is a VLAN issue and more a network design issue. I found this: https://mysupport.netapp.com/site/article?lang=en&page=%2FAdvice_and_Troubl… Issue - When NFS client attempts to Read/Write to the SVM with pNFS enabled, the operation hangs, with "nfs: [LIF address / hostname] server not responding" in /var/log/messages. Cause - This issue occurs in situations where pNFS is enabled on an SVM and there are LIFs created in different subnets, which are non-routable by the client - Data ONTAP may provide any LIF which belong's to the same SVM as the referral to a client - The Read/Write operation hangs because the data LIF IP is not reachable by the client Solution - Make sure clients can reach all data LIFs of the SVM -or- - Disable support for pNFS on the SVM ::> nfs modify -v4.1-pnfs disabled --tmac *Tim McCarthy, **Principal Consultant* *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>* *I Blog at TMACsRack <https://tmacsrack.wordpress.com/>* On Mon, Aug 16, 2021 at 9:16 AM Florian Schmid via Toasters < toasters(a)teaparty.net> wrote: > > > > ---------- Forwarded message ---------- > From: Florian Schmid <fschmid(a)ubimet.com> > To: toasters <toasters(a)teaparty.net> > Cc: > Bcc: > Date: Mon, 16 Aug 2021 13:13:15 +0000 (UTC) > Subject: pNFS not working on vserver when several lifs with different > Vlans available > Hi, > > I had a very strange incident some weeks ago. > > We are on 9.7 branch. > > In one of our vServers, where we had NFSv4 and 4.1 enabled, clients with > NFSv4.1 and pNFS where unable to read or write data. > Directory listing was possible. > > On the vServer, we have several different Vlans and each Vlans has an > interface for each node there. Our storage network is completely switched, > so no routing between Vlans possible. > > After creating a NetApp case, they told me, that pNFS doesn't handle Vlans > and the client will get any IP on that node, even when the IP is from a > different Vlan and therefor not accessible from the client. > > Is this really the case? Is the pNFS process really not Vlan aware and > sends any IP from that node where volume is located, even when the IP is in > a different network than the client IP? > > As suggested from NetApp, I have disabled pNFS and now everything is > working. > > What is your experience here? > Is anybody using pNFS with NetApp and if yes, do you only have one network > in your vServer or is the client able to access all IPs there through > different Vlans? > > I'm curious about your answers. > > Best regards > Florian Schmid > > > > > ---------- Forwarded message ---------- > From: Florian Schmid via Toasters <toasters(a)teaparty.net> > To: toasters <toasters(a)teaparty.net> > Cc: > Bcc: > Date: Mon, 16 Aug 2021 14:13:20 +0100 > Subject: > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters

1 0

Re:
by tmac 16 Aug '21

16 Aug '21

I would respectfully disagree. pNFS does not stripe data across controllers. Data is distributed, not striped. Every node is a metadata server and will redirect the client process to the node directly holding the volume. No striping. Maybe you are confusing pNFS with FlexGroups which distributes files across nodes. A very long time ago in ONTAP GX, there >>was<< an ability to stripe data across controllers. That feature was removed upon going to ONTAP 8.0 --tmac *Tim McCarthy, **Principal Consultant* *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>* *I Blog at TMACsRack <https://tmacsrack.wordpress.com/>* On Mon, Aug 16, 2021 at 9:36 AM Michael Bergman via Toasters < toasters(a)teaparty.net> wrote: > > > > ---------- Forwarded message ---------- > From: Michael Bergman <michael.bergman(a)ericsson.com> > To: Toasters <toasters(a)teaparty.net> > Cc: > Bcc: > Date: Mon, 16 Aug 2021 13:34:17 +0000 > Subject: Re: pNFS not working on vserver when several lifs with different > Vlans available > On 2021-08-16 15:13, Florian Schmid wrote: > > Is this really the case? Is the pNFS process really not Vlan aware and > > sends any IP from that node where volume is located, even when the IP is > > in a different network than the client IP? > > Yes. That's how pNFS is supposed to work. That's the whole point one can > say, of pNFS. It's striping of the data traffic (not metadata) across > several nodes, all at once. > > In that respect, the setup you say you have, this: > > "On the vServer, we have several different Vlans and each Vlans has an > interface for each node there. Our storage network is completely switched, > so no routing between Vlans possible." > > is totally wrong for pNFS. In such a set up you definitely do not want > pNFS. > > /M > > > > ---------- Forwarded message ---------- > From: Michael Bergman via Toasters <toasters(a)teaparty.net> > To: Toasters <toasters(a)teaparty.net> > Cc: > Bcc: > Date: Mon, 16 Aug 2021 14:34:25 +0100 > Subject: > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters

1 0

Re: pNFS not working on vserver when several lifs with different Vlans available
by Michael Bergman 16 Aug '21

16 Aug '21

On 2021-08-16 15:13, Florian Schmid wrote: > Is this really the case? Is the pNFS process really not Vlan aware and > sends any IP from that node where volume is located, even when the IP is > in a different network than the client IP? Yes. That's how pNFS is supposed to work. That's the whole point one can say, of pNFS. It's striping of the data traffic (not metadata) across several nodes, all at once. In that respect, the setup you say you have, this: "On the vServer, we have several different Vlans and each Vlans has an interface for each node there. Our storage network is completely switched, so no routing between Vlans possible." is totally wrong for pNFS. In such a set up you definitely do not want pNFS. /M

1 0

pNFS not working on vserver when several lifs with different Vlans available
by Florian Schmid 16 Aug '21

16 Aug '21

Hi, I had a very strange incident some weeks ago. We are on 9.7 branch. In one of our vServers, where we had NFSv4 and 4.1 enabled, clients with NFSv4.1 and pNFS where unable to read or write data. Directory listing was possible. On the vServer, we have several different Vlans and each Vlans has an interface for each node there. Our storage network is completely switched, so no routing between Vlans possible. After creating a NetApp case, they told me, that pNFS doesn't handle Vlans and the client will get any IP on that node, even when the IP is from a different Vlan and therefor not accessible from the client. Is this really the case? Is the pNFS process really not Vlan aware and sends any IP from that node where volume is located, even when the IP is in a different network than the client IP? As suggested from NetApp, I have disabled pNFS and now everything is working. What is your experience here? Is anybody using pNFS with NetApp and if yes, do you only have one network in your vServer or is the client able to access all IPs there through different Vlans? I'm curious about your answers. Best regards Florian Schmid

1 0

Use X382A in DS224C on A200/A220
by Alexander Griesser 16 Aug '21

16 Aug '21

Hey there, Does anyone know if it's safe to use the X382A SSDs from C190 storages in A200/A220 storages in DS224C shelves? HWU is giving me mixed information (or I'm reading it wrong), DS2242C seems to be supported for this SKU but when you check for platform compatibility, only the C190 is listed (for whatever reason). The reason I'm asking is that I could get a few oft hem but they're too small for my use cases, but the SSDs could be useful in other environments. 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

2 2

Removing .snapshot from directory listings?
by Fenn, Michael 04 Aug '21

04 Aug '21

Does anyone know if there's a way to hide .snapshot in directory listings, but have it still be accessible if you know the name? This is how .zfs/snapshot works, and it's an (IMHO) elegant way to make snapshots accessible without having a naïve find, du, etc. at the root of the filesystem descend into deep snapshot hierarchies. Note that I do see the snapdir-access field on volumes, but setting that to false seems to block access to .snapshot completely, which isn't what I want. Thanks, Michael

2 2

adding a shelf to an AFF220
by Rue, Randy 22 Jul '21

22 Jul '21

Hi All, We have an AFF220 with one external shelf and are adding a second shelf. I see clear info in the NetApp docs on how to connect multiple shelves, daisy chaining the shelves and returning the last shelf to the head. But the docs are based on setting up a new system and I haven't found anything on adding a shelf to a new system. Do I just move that return cable to the new shelf? Will there be any interruption to services? What else do I need to know? Thanks, Randy in Seattle

2 1

space reporting on AFF's with compression?
by Rue, Randy 22 Jul '21

22 Jul '21

Hello All, We're migrating from a FAS to a new AFF that has inline compression and a guarantee of 3X compression. I'm trying to convert a graphite/snmp graphing system that reports our overall aggregate space usage to the new system. A straightforward graph of used and free space on the data aggregates/tiers shows the right portion of space used but seems to be reporting pre-compression usage (and we appear to be getting less than 3X). The System Manager webUI says we're getting ~120:1 "Data Reduction" but it also says we're using 1.74PB and have 14TB available. In fact we currently have 48 x 900GB SSDs in two disk groups/tiers and about 40TB of actual unstructured data. Is there a doc somewhere on understanding space reporting with the new system including meaningful reporting of compression returns? Grateful for any help, Randy in Seattle

4 6

Re:
by Joseph Zoda 22 Jul '21

22 Jul '21

looking good on my end now [image: image.png] On Thu, Jul 22, 2021 at 12:54 PM Steiner, Jeffrey via Toasters < toasters(a)teaparty.net> wrote: > > > > ---------- Forwarded message ---------- > From: "Steiner, Jeffrey" <Jeffrey.Steiner(a)netapp.com> > To: Michael Gilbert <gilbert32(a)llnl.gov>, "mkopenski(a)gmail.com" < > mkopenski(a)gmail.com>, "toasters(a)teaparty.net" <toasters(a)teaparty.net> > Cc: > Bcc: > Date: Thu, 22 Jul 2021 16:52:20 +0000 > Subject: RE: support.netapp.com returns DNS error? > > Akamai is having problems. Lots of enterprises are affected. > > > > As of 4 minutes ago, they Tweeted they've implemented a fix and things are > returning to normal. > > > > *From:* Gilbert, Mike <gilbert32(a)llnl.gov> > *Sent:* Thursday, July 22, 2021 11:17 AM > *To:* mkopenski(a)gmail.com; toasters(a)teaparty.net > *Subject:* Re: support.netapp.com returns DNS error? > > > > I’m unable to get there as well. https://isitup.org also says it’s down. > > > > *From: *Toasters <toasters-bounces(a)teaparty.net> on behalf of " > mkopenski(a)gmail.com" <mkopenski(a)gmail.com> > *Date: *Thursday, July 22, 2021 at 9:09 AM > *To: *"toasters(a)teaparty.net" <toasters(a)teaparty.net> > *Subject: *Re: support.netapp.com returns DNS error? > > > > Was working for me earlier today but seems down as well as > mysupport.netapp.com > <https://urldefense.us/v3/__http:/mysupport.netapp.com__;!!G2kpM7uM-TzIFchu!…> > seems down as well > > > > On Thu, Jul 22, 2021 at 12:05 PM Walfherder <toasters(a)tson.de> wrote: > > > Anyone able to access support.netapp.com > <https://urldefense.us/v3/__http:/support.netapp.com__;!!G2kpM7uM-TzIFchu!hp…>? > It seems to down for me, I get > a strange DNS error from the server i.e. > > Service Unavailable - DNS failure > The server is temporarily unable to service your request. Please try > again later. > Reference #11.d7b51002.1626969421.263fbd7 > > This is for the URI I get re-directed to: > https://mysupport.netapp.com/site/ > <https://urldefense.us/v3/__https:/mysupport.netapp.com/site/__;!!G2kpM7uM-T…> > > Cheers, > Robb. > > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters > <https://urldefense.us/v3/__https:/www.teaparty.net/mailman/listinfo/toaster…> > > > > > ---------- Forwarded message ---------- > From: "Steiner, Jeffrey via Toasters" <toasters(a)teaparty.net> > To: Michael Gilbert <gilbert32(a)llnl.gov>, "mkopenski(a)gmail.com" < > mkopenski(a)gmail.com>, "toasters(a)teaparty.net" <toasters(a)teaparty.net> > Cc: > Bcc: > Date: Thu, 22 Jul 2021 17:52:26 +0100 > Subject: > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters -- Joe Zoda Infrastructure & Systems Support Division of Information Technology The School District of Palm Beach County 3300 Forest Hill Blvd., Suite B-332 West Palm Beach, FL 33406 joseph.zoda(a)palmbeachschools.org (561) 649-6810 http://www.PalmBeachSchools.org <http://www.palmbeachschools.org/> -- *Disclaimer: *Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing.

1 0

support.netapp.com returns DNS error?
by Walfherder 22 Jul '21

22 Jul '21

Anyone able to access support.netapp.com? It seems to down for me, I get a strange DNS error from the server i.e. Service Unavailable - DNS failure The server is temporarily unable to service your request. Please try again later. Reference #11.d7b51002.1626969421.263fbd7 This is for the URI I get re-directed to: https://mysupport.netapp.com/site/ Cheers, Robb.

8 8

Re:
by Joseph Zoda 22 Jul '21

22 Jul '21

AMZN: Amazon, UPS, PlayStation Network part of major site outage -- so netapp may be caught up in this as well ? On Thu, Jul 22, 2021 at 12:23 PM Gilbert, Mike via Toasters < toasters(a)teaparty.net> wrote: > > > > ---------- Forwarded message ---------- > From: "Gilbert, Mike" <gilbert32(a)llnl.gov> > To: "mkopenski(a)gmail.com" <mkopenski(a)gmail.com>, "toasters(a)teaparty.net" < > toasters(a)teaparty.net> > Cc: > Bcc: > Date: Thu, 22 Jul 2021 16:17:17 +0000 > Subject: Re: support.netapp.com returns DNS error? > > I’m unable to get there as well. https://isitup.org also says it’s down. > > > > *From: *Toasters <toasters-bounces(a)teaparty.net> on behalf of " > mkopenski(a)gmail.com" <mkopenski(a)gmail.com> > *Date: *Thursday, July 22, 2021 at 9:09 AM > *To: *"toasters(a)teaparty.net" <toasters(a)teaparty.net> > *Subject: *Re: support.netapp.com returns DNS error? > > > > Was working for me earlier today but seems down as well as > mysupport.netapp.com > <https://urldefense.us/v3/__http:/mysupport.netapp.com__;!!G2kpM7uM-TzIFchu!…> > seems down as well > > > > On Thu, Jul 22, 2021 at 12:05 PM Walfherder <toasters(a)tson.de> wrote: > > > Anyone able to access support.netapp.com > <https://urldefense.us/v3/__http:/support.netapp.com__;!!G2kpM7uM-TzIFchu!hp…>? > It seems to down for me, I get > a strange DNS error from the server i.e. > > Service Unavailable - DNS failure > The server is temporarily unable to service your request. Please try > again later. > Reference #11.d7b51002.1626969421.263fbd7 > > This is for the URI I get re-directed to: > https://mysupport.netapp.com/site/ > <https://urldefense.us/v3/__https:/mysupport.netapp.com/site/__;!!G2kpM7uM-T…> > > Cheers, > Robb. > > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters > <https://urldefense.us/v3/__https:/www.teaparty.net/mailman/listinfo/toaster…> > > > > > ---------- Forwarded message ---------- > From: "Gilbert, Mike via Toasters" <toasters(a)teaparty.net> > To: "mkopenski(a)gmail.com" <mkopenski(a)gmail.com>, "toasters(a)teaparty.net" < > toasters(a)teaparty.net> > Cc: > Bcc: > Date: Thu, 22 Jul 2021 17:17:27 +0100 > Subject: > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://www.teaparty.net/mailman/listinfo/toasters -- Joe Zoda Infrastructure & Systems Support Division of Information Technology The School District of Palm Beach County 3300 Forest Hill Blvd., Suite B-332 West Palm Beach, FL 33406 joseph.zoda(a)palmbeachschools.org (561) 649-6810 http://www.PalmBeachSchools.org <http://www.palmbeachschools.org/> -- *Disclaimer: *Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing.

1 0

UNMAP space issue
by Heino Walther 07 Jul '21

07 Jul '21

Hi there We have an old 7-mode NetApp on which we have created several 16TB LUNs and presented them via FC to a Windows host on which we have created one large drive using StoragePools. We now have the issue that space is not unmapped on the NetApp as we delete files from out large drive… SnapDrive does not see the LUNs we have mapped because StoragePools uses them, so we cannot start the Space Reclaimer. We have tried sdelete.exe with the -z option, but it does not seem to work for us… I have read that we should be able to use defrag /L or Optimize-Volume X -ReTrim -SlabConsolidate But I was wondering if anyone has tested this? The StoragePool was created on Windows 2016, but has since been moved to a Windows 2019 platform.. Any suggestions are very welcome 😊 We are talking very large volumes, so I would rather not test that much 😉 /Heino

2 1

10GbE to 40GbE Upgrade
by Carl Howell 15 Jun '21

15 Jun '21

We currently have an A300 cluster, each node has 2x10GbE interfaces in a multimode_lacp ifgrp connected to 2xCisco 9K's. We are upgrading each node with 2x40GbE interfaces. The question is how best to go about doing the upgrade? It would of course be nice if we could just add the 40GbE interfaces to the current port channels and ifgrp's, but I don't think the 9K's will allow us to mix speeds in a port channel. Perhaps it's possible on the 9K side to set the new interfaces to 10GbE, add them to the ifgrp's and port channels, drop the original 10GbE interfaces out and raise the speed on the new interfaces up to 40GbE. . . Thanks in advance for any help. --Carl

4 6

← Newer
1
2
3
4
5
6
7
...
542
Older →

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