Last Friday night I put 5.2.1D5 (the successor to 5.2.1P1) on one of the F630's. It didn't panic, and I've got my quotas back. Ahhhh, yeah.
Just one leetle caveat, one which caused me to believe I had a hung filer and to place a down-filer call to NetApp technical support. It seems that 5.2.1D5 sets the floppy-boot? environment variable for you by default. So when you boot, you see something like...
NetApp Release 5.2.1D5: Mon Mar 8 23:54:01 PST 1999 Copyright (c) 1992-1998 Network Appliance, Inc. Starting boot on Sat Mar 13 07:50:19 GMT 1999 Scanning for disk drives: floppy boot? .......................... Spinning up disk drives: 8a.12 8b.12 8a.13 8b.13 8a.14 8b.14 Configuring disk drives: 8b.14 8a.14 8a.9 8a.12 8b.11 8b.12 8b.9 8b.8 8b.4 8b.5 8b.1 8a.3 8a.10 8a.2 8a.11 8a.5 8b.0 8b.10 8b.13 8b.2 8b.3 8a.13 8a.8 8a.1 8a.0 8a.4
and then, apparently, the filer hangs, with the LCD saying "Configuring disk 8a.4" (or whichever one was last).
Turns out that that "floppy boot?" way up there at the top was a prompt. It's waiting for you to type "yes" or "no" on the console. A "no" causes the boot to finish normally. Then a "setenv floppy-boot? false" and a reboot gives you a happy filer.
Thanks to the NetApp tech support guy for reacting so graciously to being beeped in the middle of his Friday night.
Brian