Date: Thu, 20 Jan 2005 12:30:20 +0100 (CET) From: Oliver Fromme <olli@lurza.secnetix.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Very large directory Message-ID: <200501201130.j0KBUKMZ066099@lurza.secnetix.de> In-Reply-To: <20050120094551.GK79646@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy <PeterJeremy@optushome.com.au> wrote:
> On Wed, 2005-Jan-19 21:30:53 -0600, Phillip Salzman wrote:
> > They've been running for a little while now - and recently we've noticed a
> > lot of disk space disappearing. Shortly after that, a simple du into our
> > /var/spool returned a not so nice error:
> >
> > du: fts_read: Cannot allocate memory
> >
> > No matter what command I run on that directory, I just don't seem to have
> > enough available resources to show the files let alone delete them (echo *,
> > ls, find, rm -rf, etc.)
>
> I suspect you will need to write something that uses dirent(3) to scan
> the offending directory and delete (or whatever) the files one by one.
>
> Skeleton code (in perl) would look like:
> [...]
I would suggest trying this simple hack:
cd /var/spool/directory ; cat . | strings | xargs rm -f
It's a dirty hack, but might work, if the file names in
that directory aren't too strange (no spaces etc.).
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München
Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.
"If Java had true garbage collection, most programs
would delete themselves upon execution."
-- Robert Sewell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501201130.j0KBUKMZ066099>