Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Jun 2000 10:35:54 -0400
From:      "Troy Settle" <troy@picus.com>
To:        "Jeff Gray" <jwg2@adsl-63-201-55-220.dsl.snfc21.pacbell.net>
Cc:        <freebsd-questions@FreeBSD.ORG>
Subject:   RE: df -  du leakage
Message-ID:  <NIEBLEDADLBOBAJFKPHDOEGECAAA.troy@picus.com>
In-Reply-To: <Pine.BSF.4.10.10006050633080.24502-100000@adsl-63-201-55-220.dsl.snfc21.pacbell.net>

next in thread | previous in thread | raw e-mail | index | archive | help


At this point, no.

I think your best option, is to boot to single-user mode, and manually fsck
the filesystem.

I'm sure there may be another way, but nothing comes to mind at the moment.

-Troy



** -----Original Message-----
** From: owner-freebsd-questions@FreeBSD.ORG
** [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Jeff Gray
** Sent: Monday, June 05, 2000 9:35 AM
** To: Troy Settle
** Cc: freebsd-questions@FreeBSD.ORG
** Subject: RE: df - du leakage
**
**
** Troy,
**
** Thanks for the details, appreciate.
**
** How do you know/find which file is being affected?  Log file is a good
** guess but there are several <g>.
**
** Sorry I missed your earlier explanations.
**
** Jeff
**
**
** >
** > Something moves/renames/deletes an open log file.  The
** filename is gone, but
** > the inode is never released.  In fact, the process that has
** the file open
** > will continue to write to it.
**
**
**
** To Unsubscribe: send mail to majordomo@FreeBSD.org
** with "unsubscribe freebsd-questions" in the body of the message
**



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NIEBLEDADLBOBAJFKPHDOEGECAAA.troy>