HP3000-L Archives

May 2002, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Leonard S. Berkowitz" <[log in to unmask]>
Reply To:
Date:
Thu, 16 May 2002 13:07:35 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
It is an old phenomenon, that REPORT does not tell it "like it is," at
least not for sectors. We know this because a LISTF in MPEX (that totals up
the sectors) often reports a much lower quantity after numerous files have
been purged than REPORT reports.

Where I formerly worked, we ran FSCHECK SYNCACCOUNTING every weekend to
"fix" this. This is not the practice here.

On one of our systems, DISCFREE, probably in league with REPORT, tells us
we have 6% free space in one user volumeset, but we know from MPEX that it
is more on the order of 27%.

So the question is, which reading, if any, will cause processes to fail
because of an "out of disk space condition". In other words, if we know
(believe) that there is really 27% free, can we rely on that or will the
file system use whatever underlying structure REPORT and DISCFREE are
using?

Thanks.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-1955
pager: 781-226-2431

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2