Finding large objects that are blowing up the system ASP -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Finding large objects that are blowing up the system ASP
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 23 Apr 2025 10:49:18 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I've asked this before, and I keep forgetting the answer.

We have a customer box for which the system ASP recently shot up from a relatively benign 70-something to 95%. What's the best way to find out what's eating disk space?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Finding large objects that are blowing up the system ASP , Jack Woehr

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.