Additionally keep in mind that if you have snapshots on volume, running reallocate may “grow” snapshots significantly. To the extent that volume runs out of space. Also may have huge impact on SnapMirror reansfer. It could be avoided using “physical reallocation” (reallocate -p), but then problem is shifted from FlexVol to containing aggregate. ... View more

I would certainly be interested in more details of environment in both examples (host OS versions, details of interface configurations, routing tables on hosts/filers etc) as well as network sniff results if you have them available. ... View more

Have you tried to boot back into P1? ... View more

Well … with 24G of memory and no direct IO you are basically writing to server cache. ... View more

Traffic between hosts with multiple interfaces in the same subnet have  no deterministic source IP/interface for sending traffic, either for  initiating or replying Again - this is incorrect statement. To put it mildly. Traffic has very well defined source address and interface for each connection. It is true that source address/interface may differ between connections. In quite deterministic way But it becomes off-topic here. ... View more

Operating systems don't have deterministic connections between multiple  IP's on the same subnet.  Since all are of equal value from a routing  standpoint, the traffic can leave and enter any interface it wants. Sorry for being pedantic, but this is wrong. IP traffic is pretty much deterministic. Do not start yet another town legend ... ... View more

I believe I asked already – how much memory your client has and what are NFS mount options. ... View more

I believe, there was NetApp knowledge base and the problem definitely was discussed here already. IIRC this won’t work, account needs to be proper user account, not the machine one. Unfortunately I can’t find references right now, try to search kb/communities. ... View more

Yes, it is possible to shrink volume below logical LUN size. At the time of executing “vol size” NetApp counts physical space consumption, not logical. So if your LUN is 60% deduplicated, it actually consumes only 260G on file system which is shown in “df –h” output. If you think about it a bit, this is pretty much logical. After all, the whole point of deduplication is to be able to store more data than physically fits on storage. It does not matter whether this is single file or multiple files – the point is, sum of logical sizes exceeds physical volume space. I do not think there is single command to do what you want. As mentioned, you also can have many files, each one being relatively small but in total exceeding volume size. It should be relatively easy to script though. May be if you explain why you need to compare LUN size with volume size someone could suggest alternative way to do it. ... View more

Because I have seen reconstruction failures caused by latent sector failures, and my priority is data availability above data access speed ☺ Such failures are probably less likely on NetApp due to the way data is placed on disks … but old habits die hard ☺ Proactive disk sparing requires 2 spares so it is out of question here anyway. ... View more

Personally I’d rather have RAID_DP without spares ☺ ... View more

Is deduplication active for this volume? ... View more

You should as long as you still have enough spares left after this. Converting to RAID_DP consumes one spare per raid group, and you most probably have just one anyway. ... View more

For a start, compare single threaded application with single threaded one. Your sio_ntap runs with 4 concurrent threads, so any comparison with single threaded dd is pointless. Also raw numbers are meaningless without information about your environment (RAM size, mount options, whether you remount file systems between tests, etc). ... View more

If it is HA pair, you could try takeover/giveback. ... View more

No. It expects different boot image ☺ There are 4 different images for different types of controller. Go to Data ONTAP downloads on NOW and check which one is suitable for your hardware. ... View more

Why do you ask questions if you do not listen to answers ... You have hardware problem. Disk controller initialization fails. Before you can start with disk assignment you need to resolve this. It could be open loop. It could be as simple as failure on controller B. It could be failure on connecting cable or ESH module in shelf. Disconnect everything from controller B. Set it correctly (read hardware documentation on NOW). Check whether it sees any disk. If yes - troubleshoot issue between controller and shelf. If no - controller is broken. ... View more

I am not aware of any inherent limitation for working in failover mode. And best practice is to size your solution so that one controller can handle combined load. ... View more