Hello,
My original question has been asked before (apologies for asking about this
for what appears to be the umpteenth time).
Thanks to
Didier Godefroy <dg_at_ulysium.net>
"Dr. Tom Blinn, 603-884-0646" <tpb_at_doctor.zk3.dec.com>
Cyndi Smith <cyn_at_odin.mdacc.tmc.edu>
"Davis, Alan" <Davis_at_Tessco.Com>
Robert Carsey <rcarsey_at_monmouth.edu>
Michael Bucholtz <mbucholt_at_ceiss.org>
who responded with varying degrees of patience and interest. First, I
inquired as to the cause of these messages, and Dr. Tom Blinn kindly
offered these words:
"I suspect that what may have happened is that users are creating and
deleting files in the /tmp directory (most users don't have the option to
create or delete files elsewhere in the root file system), and that the
AdvFS files that track disk use have become inconsistent."
>From this, I infer that AdvFS must think that the user (or group) has
somehow sunk below (or is about to do so) the zero-use threshold and has a
"credit".
Dr Tom Blinn also suggested that various summaries to this question have
been posted, so I searched. All the summaries but one said, in effect,
"It's a bug in AdvFS; it's benign; live with it." It is a long-standing
bug, and promises to fix it go back quite a while (there was one in which
it was claimed to have been fixed with the release of 4.0D, but it clearly
hasn't, as that's what I am running here).
It was suggested that fixing this would be quite difficult, but a way to
suppress the messages was offered by Denise Simon in a summary by JFYeh,
which states that enabling AdvFS quotas (even if they are not enforced) on
the filesystem and then running "quotacheck -v" will make them go away. It
is implied in other summaries that the messages may crop up again, at which
time rerunning "quotacheck -v" would be in order. In a Summary by Hugo
Steiner <hugo_at_hunterlink.net.au>, he stated that "Quotacheck often upsets
my ASE environment, so I don't like running it more than I need to."
Denise Simon avers that enabling quotas, even if they are not enforced, is
a Good Thing. I seem to recall Dr Tom Blinn saying something similar not
too long ago, as well.
The steps proposed were for a non-root filesystem, but I assume it will
work on the root filesystem as well (if this is incorrect, someone please
jump in and correct me before I try this next year; I am not a trained
stunt administrator).
For those who expressed interest in what I found out, I include below an
edited version of Denise Simon's solution based on what *I* think the
correct translation should be so that it applies to the root filesystem.
Those who might want to implement this should probably verify this for
themselves. The original summary message can be found at either
http://www.xray.mpe.mpg.de/mailing-lists/tru64-unix-managers/1999-07/msg0028
3.html
or
http://www.ornl.gov/its/archives/mailing-lists/tru64-unix-managers/1999/07/m
sg00278.html
The original post is included at the end.
Thanks, -- Bennet
<-- Begin Edited Instructions -->
Step 1. Set quota option on in the /sys/conf/HOSTNAME file with the line
options QUOTA
[I presume that, if the option wasn't there, that a kernel rebuild is in
order here.]
Step 2. Using rcmgr set quota option to yes with
#/usr/sbin/rcmgr set QUOTA_CONFIG yes
Step 3. Edit the /etc/fstab file and add quotas to the fileset so it is
mounted with quotas. You should do this even if you're not using quotas.
The example line would look like
root_domain#root / advfs rw,userquota,groupquota 0 0
Step 4. umount and mount the fileset for changes to occur
[Step 4 is for a non-root filesystem; I presume that the proper step here
would be a reboot.]
Step 5. [Run] quotacheck -v /
<-- End Edited Instructions -->
<-- Begin Original Posting -->
>The console log is showing the following messages, and I was wondering if
>someone could enlighten me as to how to what an underflow is and how I go
>about correcting it?
>
>chk_bf_quota: user quota underflow for user 448 on fileset /
>chk_bf_quota: user quota underflow for user 448 on fileset /
>chk_bf_quota: group quota underflow for group 7 on fileset /
>chk_bf_quota: user quota underflow for user 448 on fileset /
>
>The user 448 is a valid user, and group 7 is in the /etc/group file as the
>tty group. The line from /etc/fstab that mounts the / filesystem is
>
>root_domain#root / advfs rw 0 0
>
>which is not enabling any quotas.
<-- End Original Posting -->
<----- oOo ----->
Bennet Fauber
Social Science Data Service
University of California, Davis
Received on Sun Dec 19 1999 - 01:31:15 NZDT