toasters

toasters@lists.teaparty.net

13520 discussions

Re: SnapMirror Bi-directional possible?
by Michael Bergman 26 Jul '18

26 Jul '18

On 2018-07-24 23:35, Scott M Gelb via Toasters wrote: > For the same data set, bi-directional, you might want to POC Peer Software. > They PeerSync bi-directional and also have PeerLink which locks files on > either side while keeping in sync. FPOLICY is used for real time event > notification without file scans. Locks files... Well, if you can live with that, then *maybe* it's viable. But cumbersome and slow. Now, in many use cases w.r.t. NFS (which is what is used by the Applications to *do* something with that data right?) the problems which such locking incur can be devastating in practice. If it's just some ppl browsing files manually, then sure -- go ahead. But with many heavy application systems it's just not acceptable. So the whole things falls over in any case. This might not be detectable in a PoC; race conditions. It's a bogmire of ifs and buts. In a way normal one-directional SM also "locks" (or rather, makes not-available) files and dirs in the RO target volume. In a certain way. So if you run applications intensely on the RO copy (target FlexVol) via NFS there is always a short moment when inodes are shifted at the updates. This is absolutely unavoidable, but what will happen to the App is then 'Stale NFS file handle'. Ka-boom. So then you go into the complexity of trying to asynchronously time the app chain to not run (in certain ways at least) at the exact second(s) this shift inside the inode structure happens. And then you give up. Been there, done that. /M

5 4

mirror one volume read/write across snapmirror?
by John Stoffel 26 Jul '18

26 Jul '18

>>>>> "Scott" == Scott M Gelb via Toasters <toasters(a)teaparty.net> writes: Scott> From: Scott M Gelb <scottgelb(a)yahoo.com> Scott> To: "toasters(a)teaparty.net" <toasters(a)teaparty.net>, Eric Peng <epeng(a)esri.com> Scott> Date: Tue, 24 Jul 2018 21:34:46 +0000 (UTC) Scott> Subject: Re: SnapMirror Bi-directional possible? Scott> For the same data set, bi-directional, you might want to POC Peer Software. Scott> They PeerSync bi-directional and also have PeerLink which locks files on either Scott> side while keeping in sync. FPOLICY is used for real time event notification Scott> without file scans. And from my experience with fpolicy and CommVault for HSM (Archiving of old files) it's fragile as all hell and not reliable. When fpolicy goes down... all hell will break loose. And what happens when you have two different people editing the same file at seperate sites? Last edit wins? This way lies sanity... you need a cluster aware filesystems. Of course people will point out that you have the same problem with NFS if you edit the same file from two seperate clients at the same site. It just silently uses the last one to write is the answer. But for remote sites with fpolicy, I'm sure it will be even more fragile. John

1 0

Max volume count per node
by Alexander Griesser 26 Jul '18

26 Jul '18

Hey there, does anyone know what the real implication of the max volume count per node setting on the FAS systems is good for? Is there any chance that this limit gets raised on newer OnTap releases or is there any secret flag to raise it (knowing that support would not want to see that)? 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<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

3 4

Re: SnapMirror Bi-directional possible?
by Klise, Steve 24 Jul '18

24 Jul '18

You can also look at somthing like DFS or a global name space like panzura. I believe they can do multiple copies but have some hardware requirements. On July 24, 2018 at 4:40:09 PM PDT, Mike Gossett <cmgossett(a)gmail.com> wrote: You could look at metrocluster, potentially Sent from my mobile phone > On Jul 24, 2018, at 5:53 PM, Eric Peng <epeng(a)esri.com> wrote: > > Thanks all, for confirming that bi-directional SnapMirror on the *same* volume is not possible. We're still in the requirements gathering/planning part of the project, so we have some time to figure this out. This would be for keeping user profiles in sync between 2 different sites. I may take a look at that PeerSync software. > > Eric > > -----Original Message----- > From: toasters-bounces(a)teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Michael Bergman > Sent: Tuesday, July 24, 2018 3:07 PM > To: Toasters <toasters(a)teaparty.net> > Subject: Re: SnapMirror Bi-directional possible? > >> On 2018-07-24 23:35, Scott M Gelb via Toasters wrote: >> For the same data set, bi-directional, you might want to POC Peer Software. >> They PeerSync bi-directional and also have PeerLink which locks files >> on either side while keeping in sync. FPOLICY is used for real time >> event notification without file scans. > > Locks files... Well, if you can live with that, then *maybe* it's viable. > > But cumbersome and slow. Now, in many use cases w.r.t. NFS (which is what is used by the Applications to *do* something with that data right?) the problems which such locking incur can be devastating in practice. If it's just some ppl browsing files manually, then sure -- go ahead. > > But with many heavy application systems it's just not acceptable. So the whole things falls over in any case. This might not be detectable in a PoC; race conditions. It's a bogmire of ifs and buts. > > In a way normal one-directional SM also "locks" (or rather, makes > not-available) files and dirs in the RO target volume. In a certain way. So if you run applications intensely on the RO copy (target FlexVol) via NFS there is always a short moment when inodes are shifted at the updates. This is absolutely unavoidable, but what will happen to the App is then 'Stale NFS file handle'. Ka-boom. So then you go into the complexity of trying to asynchronously time the app chain to not run (in certain ways at least) at the exact second(s) this shift inside the inode structure happens. > > And then you give up. Been there, done that. > > /M > _______________________________________________ > Toasters mailing list > Toasters(a)teaparty.net > https://urldefense.proofpoint.com/v2/url?u=http-3A__www.teaparty.net_mailma… > > _______________________________________________ > 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

SnapMirror Bi-directional possible?
by Eric Peng 24 Jul '18

24 Jul '18

Just wanted to do a quick sanity check, is there any way to have SnapMirror replication go both directions between sites? We are running cDOT 9.x at both locations. I came across some older posts (several years ago) that seem to indicate that bi-directional snapmirror would not be possible. Just wondering if this might have changed with cDOT 9.x capabilities? Thanks, Eric

5 4

Mac OS X, SMB NTFS, and chmod/chown
by Ehrenwald, Ian 12 Jul '18

12 Jul '18

Hello I have users on Mac OS X that are unable to uncompress zip files in SMB shares which sit on top of NTFS security style volumes. I hadn't heard of this problem until I started migrating my users to new shares, previously they were all on UNIX security style volumes. If I am understanding my users correctly, they can reliably reproduce this problem this way: - In Finder, right click on a folder on a share, select Compress - Zip file is created successfully on share - Double click on Zip file that was created - Mac OS X archiver utility pops up an error box, "Unable to expand (zip name) into (target dir). (Error 13 - Permission denied). Examining the Zip file from the command line shows that it is a fully formed file, no corruption, etc. When I attempt to uncompress the Zip file using the command line on the same machine that created it, I can see that unzip is attempting to chmod the files and directories and getting a Permission Denied error back from the svm. Output: UserMachine:z TheUser$ unzip 3\:14\:18.zip Archive: 3:14:18.zip creating: 3:14:18/ chmod (directory attributes) error: Permission denied inflating: 3:14:18/FileNameXYZ.FC3.idml fchmod (file attributes) error: Permission denied creating: __MACOSX/ chmod (directory attributes) error: Permission denied creating: __MACOSX/3:14:18/ chmod (directory attributes) error: Permission denied inflating: __MACOSX/3:14:18/._FileNameXYZ.FC3.idml fchmod (file attributes) error: Permission denied inflating: 3:14:18/FileNameABC.ai fchmod (file attributes) error: Permission denied inflating: __MACOSX/3:14:18/._FileNameABC.ai fchmod (file attributes) error: Permission denied inflating: 3:14:18/FileNameLMN.png fchmod (file attributes) error: Permission denied inflating: __MACOSX/3:14:18/._FileNameLMN.png fchmod (file attributes) error: Permission denied inflating: 3:14:18/FileNameXYZ.FC3.indd fchmod (file attributes) error: Permission denied inflating: __MACOSX/3:14:18/._FileNameXYZ.FC3.indd fchmod (file attributes) error: Permission denied warning: cannot set permissions for __MACOSX/3:14:18/ Permission denied warning: set times/attribs failed for __MACOSX/3:14:18/ warning: cannot set permissions for __MACOSX/ Permission denied warning: set times/attribs failed for __MACOSX/ warning: cannot set permissions for 3:14:18/ Permission denied warning: set times/attribs failed for 3:14:18/ UserMachine:z TheUser$ This does make sense, since SMB/CIFS doesn't really understand UNIX ownership and attributes. Is the solution setting the security style of the volume to Mixed? Reading in detail about it at https://whyistheinternetbroken.wordpress.com/2017/01/24/mixed-perceptions-m… makes it seem like that's the right path to follow, but before I start down that trail I wanted to see what other people have done in this situation. Thanks for your help. Ian Ehrenwald Senior Infrastructure Engineer Hachette Book Group, Inc. 1.617.263.1948 / ian.ehrenwald(a)hbgusa.com This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.

7 14

How to resolve LUN misalignment?
by Chris Hague 25 Jun '18

25 Jun '18

Showing Alignment: misaligned on a large LUN which has been 7MTT migrated. Looking for a procedure for ONTAP 9.1, all articles seem to be for 7-Mode. Can anyone in this group offer any advice? This email is being sent by a subsidiary of Arthur J. Gallagher Holdings (UK) Limited, part of the Arthur J. Gallagher & Co. global group of companies. For details of the registered office, company number and, where applicable, regulated status of our subsidiaries, please visit https://www.ajginternational.com/legal-regulatory-information/. We are the data controller of any personal information you provide to us or personal information that has been provided to us by a third party. We collect and process information about you in order to arrange insurance policies and to process claims. Your information is also used for business purposes such as fraud prevention and detection and financial management. This may involve sharing your information with third parties such as insurers, reinsurers, other brokers, claims handlers, loss adjusters, credit reference agencies, service providers, professional advisors, our regulators, police and government agencies or fraud prevention agencies. We may record telephone calls to help us monitor and improve the service we provide. For further information on how your information is used and your rights in relation to your information please see our privacy notice at https://www.ajginternational.com/Privacy-Policy/. If you are providing personal data of another individual to us, you must tell them you are providing their information to us and show them a copy of this notice. Where you are obtaining a non-consumer policy of (re)insurance, or cover for additional risks or renewal under an existing policy, you are required to make a fair presentation of the risk to a (re)insurer which discloses every material circumstance which you know or ought to know relating to the risk to be insured. A circumstance is material if it would influence the judgment of a prudent insurer in determining whether to provide insurance for the risk and, if so, on what terms. Disclosure must be reasonably clear and accessible to a prudent insurer and made in good faith. The aforementioned duty of disclosure is the applicable duty under the laws of England and Wales. If your policy is not subject to English law you are expected to disclose risk information in accordance with the requirements of the applicable law. In such circumstances we expect you will disclose risk information at least equal to the standard required under English law and where the applicable law requires you to disclose information over and above the level required under English law you will provide such information in accordance with that law. Where you are obtaining a consumer policy of insurance, you must read each question and answer honestly and fully and must take reasonable care to not make a misrepresentation. Failure to comply with the above disclosure requirements, as they apply to you, could mean that your policy of (re)insurance is void, its terms are materially altered or that (re)insurers are not liable to pay all or part of your claim(s). If you are in any doubt as to your obligations you should ask your usual contact. This e-mail and any attachments are CONFIDENTIAL and may contain legally privileged information. If you are not the intended recipient of this e-mail message, please telephone or e-mail us immediately, delete this message from your system and do not read, copy, distribute, disclose or otherwise use this e-mail message and any attachments. Although the above company has taken reasonable precautions to ensure this e-mail and any attachments are free of any virus or other defect that may affect your computer, it is the responsibility of the recipient to ensure that it is virus free and the above company does not accept any responsibility for any loss or damage arising in any way from its use.

4 4

node too busy
by Peter D. Gray 20 Jun '18

20 Jun '18

Hi people, I saw a recent post from a list member asking about how to finsd out what is keeping a node so busy. No, I had a quick look at my systems and sure as eggs I have a node which is 99% bust pretty much all the time dispite not doing that mush I/O. Example: Node CPU_(%) *Total_Ops Total_(Bps) Latency_(us) UOW-DR-03 38 6507 178442598 4152 UOW-DR-01 40 6195 24945585 1142 UOW-DR-02 99 2618 79917069 3246 UOW-DR-04 2 0 0 0 This is just a 5 sec sample, but its pretty much like that all the time. How do a diagnose why? Ontap 9.3P2 Regards, pdg Peter Gray Ph (direct): +61 2 4221 3770 Information Management & Technology Services Ph (switch): +61 2 4221 3555 University of Wollongong Fax: +61 2 4229 1958 Wollongong NSW 2522 Email: pdg(a)uow.edu.au Australia URL: http://pdg.uow.edu.au

2 1

FAS8040 cpu pegged for over 1 month 24/7
by jordan slingerland 15 Jun '18

15 Jun '18

I have an 8040 is at 100% cpu all the time on all cores. It has been like this for at least a month, my stats do not go back further than this. I expect the cpu was not this high before upgradin to 9.3P2. I feel like i should be able to get more than 10k ops out of a 150TB hybrid aggregate with 222 disks in it. Any help or feedback on performance expectations will be appreciated. Let me know if any stats would be usefull, i stripped my email down as my first try was rejected for being too big. HOSTNAME::> node run -node HOSTNAME-0 HOSTNAME-01 HOSTNAME-02 HOSTNAME::> node run -node HOSTNAME-02 Type 'exit' or 'Ctrl-D' to return to the CLI HOSTNAME-02> sysstat prif set diag priv set diag Warning: These diagnostic commands are for use by NetApp personnel only. HOSTNAME-02*> sysstat -M 1 ANY1+ ANY2+ ANY3+ ANY4+ ANY5+ ANY6+ ANY7+ ANY8+ AVG CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 Nwk_Excl Nwk_Lg Nwk_Exmpt Protocol Storage Raid Raid_Ex Xor_Ex Target Kahuna WAFL_Ex(Kahu) WAFL_MPClean SM_Exempt Exempt SSAN_Ex Intr Host Ops/s CP 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 32% 0% 0% 0% 30% 10% 0% 0% 253%( 36%) 0% 0% 99% 18% 3% 353% 3748 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 33% 0% 0% 0% 29% 10% 0% 0% 235%( 33%) 0% 0% 70% 19% 3% 398% 3959 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 34% 0% 0% 0% 30% 9% 0% 0% 245%( 35%) 0% 0% 74% 19% 3% 385% 3802 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 30% 0% 1% 0% 28% 8% 0% 0% 236%( 33%) 0% 0% 76% 17% 3% 399% 3367 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 30% 0% 2% 0% 29% 8% 0% 0% 217%( 31%) 0% 0% 71% 16% 3% 422% 3427 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 36% 0% 1% 1% 33% 9% 0% 0% 242%( 34%) 0% 0% 91% 19% 3% 362% 3754 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 33% 0% 0% 0% 26% 4% 0% 0% 272%( 38%) 18% 0% 102% 18% 4% 320% 3496 60% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 34% 0% 1% 0% 24% 4% 0% 0% 258%( 36%) 3% 0% 87% 20% 3% 364% 4001 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 41% 0% 0% 0% 32% 5% 0% 0% 276%( 39%) 2% 0% 101% 24% 4% 312% 4752 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 44% 0% 0% 0% 27% 4% 0% 0% 268%( 38%) 1% 0% 101% 25% 4% 323% 5077 28% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 36% 0% 0% 0% 29% 2% 0% 0% 256%( 36%) 3% 0% 96% 21% 4% 352% 4105 2% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 40% 0% 2% 0% 22% 1% 0% 0% 252%( 36%) 2% 0% 114% 23% 4% 339% 4801 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 33% 0% 3% 0% 17% 1% 0% 0% 236%( 33%) 2% 0% 73% 20% 3% 410% 4280 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 33% 0% 1% 0% 16% 2% 0% 0% 232%( 33%) 1% 0% 67% 20% 3% 424% 4219 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 29% 0% 0% 0% 15% 1% 0% 0% 230%( 32%) 2% 0% 71% 18% 3% 429% 3719 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 31% 0% 0% 0% 24% 2% 0% 0% 241%( 34%) 3% 0% 75% 19% 3% 400% 4206 0% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 1% 28% 0% 0% 0% 46% 11% 0% 0% 263%( 37%) 67% 0% 82% 17% 3% 280% 3496 59% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 25% 0% 0% 1% 38% 7% 0% 0% 324%( 46%) 52% 0% 107% 16% 3% 226% 3127 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 100% 0% 0% 30% 0% 0% 1% 35% 7% 0% 1% 285%( 40%) 49% 0% 86% 18% 3% 285% 3633 100% 0% 0% 94% 20% 4% 341% 4300 100% HOSTNAME-02*> sysstat -x 1 CPU NFS CIFS HTTP Total Net kB/s Disk kB/s Tape kB/s Cache Cache CP CP_Ty CP_Ph Disk OTHER FCP iSCSI FCP kB/s iSCSI kB/s in out read write read write age hit time [T--H--F--N--B--O--#--:] [n--v--p--f] util in out in out 100% 6 0 0 3907 100046 124797 278121 20862 0 0 3s 94% 0% 0--0--0--0--0--0--0--0 0--0--0--0 25% 3 0 3898 0 0 99115 127259 100% 3 0 0 3869 60123 134198 411571 20704 0 0 4s 94% 0% 0--0--0--0--0--0--0--0 0--0--0--0 33% 5 0 3861 0 0 59346 120058 100% 0 0 0 4089 27375 116197 225213 18145 0 0 4s 93% 0% 0--0--0--0--0--0--0--0 0--0--0--0 23% 0 0 4089 0 0 26622 115872 100% 13 0 0 4175 35817 111147 260996 28849 0 0 2s 94% 0% 0--0--0--0--0--0--0--0 0--0--0--0 25% 0 0 4162 0 0 34874 125888 100% 2 0 0 4143 56386 99541 401056 23882 0 0 0s 93% 0% 0--0--0--0--0--0--0--0 0--0--0--0 37% 17 0 4124 0 0 55471 105104 100% 11 0 0 3750 25706 149389 364912 154655 0 0 2s 93% 43% 1--0--0--0--0--0--0--0 0--1--0--0 29% 0 0 3739 0 0 24904 119412 100% 4 0 0 3395 36225 45390 280507 211869 0 0 3s 92% 100% 0--0--0--0--0--0--0--1 0--0--1--0 40% 0 0 3391 0 0 35744 81843 100% 25 0 0 4713 46662 149078 307272 93644 0 0 4s 95% 100% 0--0--0--0--0--0--0--1 0--0--0--1 42% 184 0 4504 0 0 45774 118418 100% 2 0 0 3930 51697 110975 221814 105300 0 0 3s 93% 100% 0--0--0--0--0--0--0--1 0--0--0--1 26% 0 0 3928 0 0 50821 108484 100% 5 0 0 4148 54985 137949 267436 208711 0 0 3s 93% 100% 1--0--0--0--0--0--0--1 1--0--0--1 31% 9 0 4134 0 0 53645 142356 100% 16 0 0 4883 81959 108174 364367 666466 0 0 4s 94% 100% 0--0--0--0--0--0--0--2 0--0--0--2 40% 1 0 4866 0 0 81554 95623 100% 5 0 0 6111 74315 122018 268918 79372 0 0 3s 95% 100% 0--0--0--0--0--0--0--1 0--0--0--1 26% 4 0 6102 0 0 72956 126959 100% 3 0 0 4658 50514 119345 218663 157863 0 0 3s 94% 100% 0--0--0--0--0--0--0--1 0--0--0--1 22% 0 0 4655 0 0 50021 112484 100% 2 0 0 4125 61813 137044 244725 223996 0 0 3s 93% 100% 0--0--0--0--0--0--0--1 0--0--0--1 23% 0 0 4123 0 0 59479 135345 100% 6 0 0 4005 48098 158865 283920 54318 0 0 4s 95% 15% 0--0--0--0--0--0--0--0 0--0--0--0 26% 14 0 3985 0 0 47165 162826 100% 24 0 0 4490 45946 155717 266290 96976 0 0 2s 93% 0% 0--0--0--0--0--0--0--0 0--0--0--0 28% 0 0 4466 0 0 44575 146650 100% 7 0 0 4935 52081 155766 331777 11753 0 0 4s 93% 0% 0--0--0--0--0--0--0--0 0--0--0--0 32% 2 0 4926 0 0 51171 165626 100% 0 0 0 6518 39526 179763 350349 24130 0 0 1s 92% 0% 0--0--0--0--0--0--0--0 0--0--0--0 29% 4 0 6514 0 0 38678 177139 HOSTNAME-02*> qos exit logout HOSTNAME::> qos statistics characteristics show -iterations 0 -rows 10 Policy Group IOPS Throughput Request size Read Concurrency Is Adaptive? -------------------- -------- --------------- ------------ ---- ----------- ------------ -total- 8094 321.31MB/s 41627B 41% 17 - data02_PROD_2 1626 101.69MB/s 65578B 80% 7 false DEV_DATA_DEV_2 1528 147.53MB/s 101219B 57% 5 false _System-Work 1243 4.40KB/s 3B 1% 0 false DEV_DATA_DEV 749 6.51MB/s 9121B 93% 1 false data02_PROD 667 9.48MB/s 14911B 0% 1 false DEV_OS_DEV_2 470 28.78MB/s 64214B 35% 2 false data04_PROD 256 4.35MB/s 17812B 8% 0 false data03_PROD 191 3.64MB/s 19971B 0% 0 false os03_PROD_2 191 1.55MB/s 8496B 0% 0 false shares02_PROD 183 1382.41KB/s 7721B 84% 0 false -total- 9542 347.25MB/s 38158B 42% 21 - DEV_DATA_DEV_2 1675 83.11MB/s 52028B 71% 4 false data02_PROD_2 1547 103.42MB/s 70112B 86% 7 false _System-Work 1191 6.58KB/s 5B 0% 0 false DEV_OS_DEV_2 860 30.42MB/s 37095B 37% 2 false DEV_DATA_DEV 667 5.22MB/s 8208B 96% 0 false data03_PROD_2 627 11.51MB/s 19255B 2% 3 false data02_PROD 528 7.24MB/s 14370B 0% 0 false shares02_PROD 526 80.62MB/s 160604B 66% 3 false data01_PROD 411 4.87MB/s 12431B 0% 0 false data03_PROD 377 4.95MB/s 13746B 0% 0 false Policy Group IOPS Throughput Request size Read Concurrency Is Adaptive? -------------------- -------- --------------- ------------ ---- ----------- ------------ -total- 11004 218.56MB/s 20827B 36% 15 - _System-Work 3750 24.82KB/s 6B 0% 0 false DEV_DATA_DEV_2 1572 25.67MB/s 17129B 78% 2 false data02_PROD_2 1568 91.24MB/s 61028B 99% 7 false DEV_DATA_DEV 793 6.19MB/s 8185B 96% 0 false os03_PROD 652 5.18MB/s 8322B 4% 1 false DEV_OS_DEV_2 549 31.44MB/s 60082B 44% 2 false data01_PROD 411 6.96MB/s 17753B 0% 0 false shares02_PROD 304 34.42MB/s 118717B 42% 2 false data02_PROD 261 4.56MB/s 18303B 0% 0 false data03_PROD 237 3.59MB/s 15904B 0% 0 false

3 4

mgmtgwd.aggregate.used.rising
by Mike Thompson 14 Jun '18

14 Jun '18

Hey guys, In Ontap 8, we used to route this message to a group of operators, who would move volumes around when aggregates started getting full. I don't see the associated message in the Ontap 9 message catalog, or anything that looks similar. Any ideas?

4 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters