Please remove me from this list
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Philbert Rupkins Sent: Tuesday, July 21, 2015 10:55 PM To: Roy McMorran Cc: toasters@teaparty.net Subject: Re: FAS-2554 cDOT sanity check requested
Disclaimer: Still on 7-mode so these commands may not apply to cluster mode. NetApp Technical Support should have gone through this with you so this may not be of any help. This information would be in a perfstat as well.
During the test, how does disk utilization look with the following commands. CPU?
# sysstat -u 1 # stats show disk:*:disk_busy -- look for hot spots in this output. # sysstat -m 1
Check out nfs statistics. You may need to explore the options available with nfsstat
# nfsstat
Check on any tcp errors.
# netstat -s
Check for any increasing error statistics on the ethernet interface
# ifstat -a
Are you using link aggregation on your NetApp's 10G nics?
Perhaps try a larger block size with IOZONE?
Did you add all your disks to the aggregate RG's at once? By chance, did you create the aggregate with the minimum number of disks, create the volume then add more disks to the aggregate later? If yes, look into reallocating the volume as you may have a few hot spots.
On Fri, Jul 17, 2015 at 1:51 PM, Roy McMorran <mcmorran@mdibl.org mailto:mcmorran@mdibl.org > wrote:
Hi Jordan, thanks for your reply. On 7/17/2015 2:32 PM, Jordan Slingerland wrote:
Are your aggregates full?
Nope, brand new box, hardly using anything at all.
Is there another workload? Check out sysstat –x 1 and see what the CP time column looks like and also check out disk busy.
My test server is the only thing talking to it at this point.
Rebuild in progress?
Nope
Snapmirrors in progress?
None exist
Deduplication in progress?
Not enabled on any volumes on this vfiler. Idle on the other vfiler.
Those are some small aggregates, but I would still expect more than 2Mb. Each aggregate is 1 raid group, right?
Yes. And 2MB went to 15MB after the 'setenv wafl_c2c_xfer_timeout 0' workaround. That's really the root of my question - is this as good as it'll get?
Personally, with that few disks, I would have assigned each disk type to 1 node and have them all in 1 aggregate, but it sounds like it is 2 late for that.
Maybe not, and thanks for the input. That's not something NetApp has suggested yet, and I don't want to change anything right now while we're working the case, but it's not in production and I could nuke it and start over at some point. Thanks, Roy
_______________________________________________ Toasters mailing list Toasters@teaparty.net mailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters