![cloud station client version 2361 cloud station client version 2361](https://uploads.golmedia.net/uploads/articles/article_media/16282778171645638275gol1.jpg)
Options nfs onĪggregate aggr0 (online, raid_dp) (block checksums) Tried many NFS options stopped for now at:įstab on the client 192.168.1.200:/vol/vol_1
![cloud station client version 2361 cloud station client version 2361](https://img.freepik.com/free-vector/glass-building-industry-factory-logo-vector-symbol-icon-design-illustration_15473-2361.jpg)
It has been recently wiped clean, installed Ontap 7.3.7, configured - and now I am just testing to see why is this happening before moving a few KVM machines on the filer. But NFS shouldn't exercise this on a filer with a single file copied over from a single station. As my filer has a single core, no M option for me, and I really think this is a load pure and simple. With NFS v3 it's around 60-70% but this is a no no, the speed is halved.
![cloud station client version 2361 cloud station client version 2361](https://mlwqpdzmxkwy.i.optimole.com/xBGn12Y-VkDYcwYV/w:365/h:299/q:90/https://www.quantsnote.com/wp-content/uploads/2020/12/Cloudways-Setting-Up-Server-and-Application-6_mark.png)
My client machines (a CentOS 6.4 and a openSUSE 12.3 used for testing) get kind of stuck and they freeze in the process. Now problem is I am trying to make use of NFS namely vs4 and I get always 95-100% CPU load during transfers, and it's dramatic on files over 5GB. I have a FAS2020 single controller, 12 300GB 15k SAS, NICs aggregated in a vif, a bunch of servers and 2 stations all running linux, everything GB LAN, connected to a SG300-28 Cisco switch. Hello, I hope I am asking this in the right area.