Then trying to tranfer 16MB chunks we get about 380MB/s transfer rates. 22-23 iops. I would of expected a bit more. Hmm ... your stats show that real IO size is much less, sounds more like 256KB. Probably it gets split at OS level. This could have impact on throughput. May be it is limited by vmfs block size? atleast 600MB writing to the rg. But your tests are pure read, not write?
... View more
Nitpicking - maxdirsize is irrelevant here. This is maxfiles option. Отправлено с iPhone 20 дек. 2013 г., в 20:22, "billshaffer" <xdl-communities@communities.netapp.com<mailto:xdl-communities@communities.netapp.com>> написал(а): <https://communities.netapp.com/index.jspa> Re: Inode getting filled created by billshaffer<https://communities.netapp.com/people/billshaffer> in Data ONTAP - View the full discussion<https://communities.netapp.com/message/122776#122776> Your permanent fix is to stop writing new files to the volume. Every time you write a file, you use up at least one inode. There is a finite number of inodes available in a volume - this can be increased with the maxdirsize option, but all you're doing there is resetting that finite number. As HenryPan2 points out, there are performance implications for increasing this value (though in truth I've modified it many times and never seen an impact). So if you truly want a permanent fix, you need to remove data from the volume. Archive/delete some old stuff. Migrate to a new volume. But if you continue to write files in this volume, you will continue to use inodes, and you will continue to run into this problem. Hope that helps Bill Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/122776#122776> Start a new discussion in Data ONTAP by email<mailto:discussions-community-products_and_solutions-data_ontap@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2877>
... View more
BY common sense I can figure out that RC stands for Running configurations.. Actually "rc" originates in first version of UNIX and stands for "run commands" (or more precisely, from old utility "runcom" at the time UNIX was created).
... View more
Today you should really always mention whether you mean 7-Mode or C-Mode … For C-Mode it is non-disruptive. For 7-Mode it is supported and is non-disruptive for volumes containing LUN only. I think you can actually move only between different aggregates (moving inside of the same aggregate does not really makes sense). You can move between different disk types.
... View more
Yes, it is possible. Just connect shelves to new filer and assign disks. Aggregate will be found automatically. They may be shown as “foreign” in which case you just need to online them, possibly after renaming.
... View more
For target HBA WWPNs are assigned based on slot position so if you replace it in the same slot it should retain WWPN. But of course you should always double check it after replacement ☺
... View more
You will need to completely reinstall filer losing all existing data; and the first thing you will need are c-mode licenses. Do you have them? You should also be able to reinstall back in 7-mode; again losing all existing data.
... View more
No. target and initiator PCI cards are two different cards with two different part numbers. It is impossible to reconfigure them in the field. Do not confuse with on-board adapters. The only exception that comes to my mind is mezzanine on 2240.
... View more
Space reservations on this provisioned volumes are not honored by containing aggregate. So in your case you have logical space reservation (in a volume) but it is not backed up by physical (in aggregate). Отправлено с iPhone 29 нояб. 2013 г., в 0:42, "John Luin" <xdl-communities@communities.netapp.com<mailto:xdl-communities@communities.netapp.com>> написал(а): <https://communities.netapp.com/index.jspa> Thick provisoned LUNs inside thin provisoned volumes? created by John Luin<https://communities.netapp.com/people/sedakill1> in Products & Solutions - View the full discussion<https://communities.netapp.com/message/121549#121549> Hello All! I've took over a FAS6280 and I'm trying to get a better understanding on how space is calculated using the following structure. The engineer before me create all of his LUNs leveraging thick provisioning and then he put them in a volume that's thin provisioned. Where I'm getting confused is if I look at the volume's utilization it's showing as your would expect, i.e., the LUNs full thick provisoned size; however, if I look at the actual aggr utilization it doesn't show this space as being accounted for? Why is this? TIA! Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/121549#121549> Start a new discussion in Products & Solutions by email<mailto:discussions-community-products_and_solutions@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2068>
... View more
Block protocols (FCP/iSCSI) licenses enable limited CIFS functionality. You are able to add filer to domain, authenticate users through domain and have access to /etc. I’m not sure it is full featured access, but it should be enough to be able to fetch files from it or drop firmware into it.
... View more