I have found this bug at the NOW site: 69823

Here is the text. There is a workaround documented and it is fixed in 6.3 and up:

Before OnTAP release 6.2, wafl.maxdirsize was a filer-wide option that could legally take on values larger than 64 MB (65,536 x 1,024 bytes). OnTAP 6.2 changes wafl.maxdirsize in two important ways. First, it obsoletes the single, filer-wide option and replaces it individual maxdirsize settings for each volume. Second, it allows maxdirsize to be set no higher than 64 MB. In filers that had set wafl.maxdirsize to a value greater than 65,536 (64 MB), an upgrade to OnTAP 6.2 sets the new per-volume maxdirsize value to its default, 10,240 (10 MB). The upgrade output does not highlight this change to the system administrator. Given that wafl.maxdirsize had been previously set to a much larger value, there is a good probability that the upgrade will produce a nontrivial number of directories that are now larger than the volume's new (relatively small) maxdirsize setting. Although all such directories can still be loaded into memory and handle lookups, they have been rendered "ungrowable". Workaround Formatted Before upgrading any filer whose wafl.maxdirsize is larger than 64 MB, examine its volumes to locate all "large" (over 10 MB) directories. If any such large directories exist, please reset wafl.maxdirsize on the filer to an appropriate value (that is still smaller than the new 64 MB limit) BEFORE the upgrade. This way, the upgrade to OnTAP 6.2 will propagate this more reasonable value to each volume. If any existing directories are LARGER than 64 MB, try to reduce their size below 64 MB. Since directories never shrink in OnTAP, you may be able to recreate these very large ones and thus get rid of a significant amount of wasted space. If, despite these efforts, you still have directories that are larger than 64 MB, then they will be "ungrowable" after the upgrade. If you have already upgraded one or more filers to OnTAP 6.2 whose wafl.maxdir option had been set to more than 64 MB, you should check them for any large directories that are now past the new 10 MB default per-volume maxdirsize setting. Use the "vol options" command to raise maxdirsize to a value large enough to make those directories growable again (as long as they are still below the new 64 MB maximum). Notes Formatted Network Appliance is working on a change to the maxdirsize portion of the OnTAP 6.2 upgrade that sets a more reasonable value in these circumstances. In cases where the filer-wide wafl.maxdirsize setting is found to be larger than 64 MB, the upgrade will choose a maxdirsize of 64 MB (instead of 10 MB). This guarantees that all existing directories that are still smaller than the new 64 MB limit are still growable, and minimizes user "surprise". The upgrade code will also print out a message describing the change in maxdirsize (and its implications) to administrators. Related Solutions Version Found Data ONTAP: 6.1.3R1 Likely Exists Data ONTAP: 6.1.3R1 through 6.2.2 Fixed-In Version Data ONTAP 6.3 (First Fixed) - Fixed Data ONTAP 6.3.1R1 (GA) - Fixed Data ONTAP 6.3.2(FCS) - Fixed Data ONTAP 6.4R1(FCS) - Fixed

-----Original Message----- From: Reinoud Reynders [mailto:Reinoud.Reynders@uz.kuleuven.ac.be] Sent: Wednesday, March 26, 2003 12:41 AM To: kyle; toasters@mathworks.com Subject: Re: maxdir size on ontap 6.2 and higher

Hi Kyle,

This is indeed a problem, and on this moment, there is no workaround. I have the same problem. We have done some migration from 1 directory to multi directories. Netapp is working on this issue, but for the details, you must contact your local netapp guys.

Best regards,

Reinoud

----- Original Message ----- From: "kyle" kyle@sportsline.com To: toasters@mathworks.com Sent: Tuesday, March 25, 2003 8:14 PM Subject: maxdir size on ontap 6.2 and higher

Seems there is a limit of 64k. This is keeping me from upgrading. I currently use 6.1R1 and just tried upgrading one of my lab netapps and see I cant go higher than 64k for maxdir size. Is there some workaround?