We have just upgraded from 6.3.3 to 6.4.2P6 (now it is "GA") and suffered a nasty consequence. If an entry in /etc/quotas doesn't specify any of "K", "M" or "G" for the limit, e.g.
261 user@/home 81920 4000
then the units are taken to be bytes rather than (as before, since time immemorial) kilobytes. In the example the limit becomes 80 KB rather than 80 MB.
We have a daily useradmin job that runs overnight, and among other things builds a new /etc/quotas from another data source and then does a "quota resize". Our users weren't too happy to have all their quotas divided by 1024 in one swell foop... I have added an explicit "K" now, of course.
All the documentation I can find still claims that "The default for the disk limits and warning threshold is kilobytes", so maybe this is a bug. Or maybe it will be reclassified as a feature when NetApp get around to updating the documentation. Anyway, it's something anyone upgrading ought to beware of.
Chris Thompson Email: cet1@cam.ac.uk