This hints at problems with UNICODE file names. Snapshot is read-only, so if original files did not have UNICODE version of file name, it cannot be generated on the fly.
... View more
Thanks. Would you be so kind … 1. Ha-config also offers option “auto”. What does it do exactly? 2. Could you explain why we need different options for chassis and controller? From your example it follows that either system is HA pair or not. Under which conditions would “chassis” and “controller” setting differ?
... View more
If 2TB is added to the same raid group as 1TB, then it will use a 2TB drive as parity Do you mean that if I add 2TB drive to existing 1TB raid group it will automatically make it parity drive? I vaguely recall something like this already discussed and I think that this works (assuming this really works) only for RAID4, not for RAID_DP. Do you have any pointers (I remember the was BURT dealing with this, may be KB or anything)?
... View more
At the moment in-place update without capacity extension is not supported. You may try to raise the issue with your NetApp representative, if they can come with solution. If you update to 8.1.1 anyway, it is possible to reverse SnapMirror from 64 bit back onto 32 bit aggregate. You will get 64-bit volume on 32-bit aggregate.
... View more
WAFL is unique in its ability to create large numbers of snaps that impart no performance penalty. Let's be fair. ZFS (and appliances based on ZFS) can create far more snapshots per file system with the same (lack of) performance impact. 255 snapshots per volume is not really that much, especially on a SnapVault destination. NetApp is showing its age here.
... View more
Well … on Solaris obsolete patch is still present in installed patch database. Even for new releases which integrate all previous patches (analog of slipstream Windows installation) information about applied patches is present. Is there anything similar on Windows?
... View more
I think this message I received after doing "aggr XXX options root" in maintenance mode pretty much explains what happened *> aggr options system root aggr options: Could not copy the FCP, ISCSI and igroup configuration information from the previous root 'aggr0' to the new root 'system'. Use the fcp, iscsi, igroup, lun and vfiler commands to verify the configuration information and recreate it if needed. Contact NetApp Global Services for further assistance. Aggregate 'system' will become root at the next boot. *> So when you issued "vol ... options root" under running system, it overwrote definitions on old root. I wish there were easy way to save and restore block-protocol related settings, or at least that how they are stored were documented in more details.
... View more
NetApp collects detailed performance stats (with second resolution) by default. This is large amount of data so it will automatically delete older stats when consumed space exceeds threshold. Threshold is computed as percentage of root volume size which explains why it changes when root volume is resized. There is KB article about performance archiver, I do not remember exact number.
... View more