It is reported as burt 106031. The workaround is to explicity specify 'K'.
- Rick -
-----Original Message----- From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] Sent: Tuesday, December 02, 2003 6:17 AM To: toasters@mathworks.com Subject: Default units for quotas in 6.4.2P6
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
Rick Ehrhart writes:
It is reported as burt 106031. The workaround is to explicity specify 'K'.
Thanks. Today I can even see the bug details rather than that annoying "Bug information not available" state! As this is said to be fixed in 6.4.2P10, I presume it was a known bug before I posted to toasters.
Which causes me to wonder what has happened to Bug Profile Alert messages recently. I don't seem to have received one since 27 October: has anyone else? or is it just me?
Maybe the timing is such that I wouldn't have seen this bug in time anyway.
Chris Thompson Email: cet1@cam.ac.uk
On 5 December, I wrote:
Rick Ehrhart writes:
It is reported as burt 106031. The workaround is to explicity specify 'K'.
Thanks. Today I can even see the bug details rather than that annoying "Bug information not available" state! As this is said to be fixed in 6.4.2P10, I presume it was a known bug before I posted to toasters.
Which causes me to wonder what has happened to Bug Profile Alert messages recently. I don't seem to have received one since 27 October: has anyone else? or is it just me?
It was just me. Apparently I managed to mangle my e-mail address in my NOW profile so the messages weren't getting out. Thanks to the NetApp people who sorted this out for me.
[Hint for anyone who gets into similar trouble: follow the "history" link in the Action column of "Existing Bug Alert Profiles" and you can find out what bugs you ought to have been sent messages about and when. It would be even more useful if you could see the list sorted by date, though.]
Maybe the timing is such that I wouldn't have seen this bug in time anyway.
And indeed that turns out to be the case: I would have received the message on/after 3 December, and we upgraded to 6.4.2P6 on 1 December and suffered the conseqences the next night. C'est la vie ...
Chris Thompson Email: cet1@cam.ac.uk
-
Chris Thompson -
Ehrhart, Rick