From: Forkner, Robert (forknerr@ACU.EDU)
Date: Wed Aug 07 2002 - 12:19:43 EDT
GREAT! I'll give that a try. Thanks.
-----Original Message-----
From: Sandor W. Sklar [mailto:ssklar@Stanford.EDU]
Sent: Monday, August 05, 2002 12:25 PM
To: aix-l@Princeton.EDU
Subject: Re: Unable to unmount a filesystem
On Monday, August 5, 2002, at 09:42 AM, Forkner, Robert wrote:
Thanks, that worked on the /u04 filesystem. I found that, somehow, syslogd
was using that filesystem.
Unfortunately, I have had the same problem with /u02, and fuser returned
nothing until I added the -d flag ("Reports on any open files which have
been unlinked from the file system (deleted from the parent directory)") and
now it is reporting the following:
$ fuser -dV /u02
/u02:
inode=446559 size=58296 23410e
inode=446559 size=58296 24992e
inode=446559 size=58296 25364e
inode=446559 size=58296 58638e
inode=446559 size=58296 59088e
inode=446559 size=58296 64194e
inode=446559 size=58296 64784e
inode=446559 size=58296 75822e
inode=446559 size=58296 90858e
so what is this output trying to tell me ... that although the data has been
deleted that it's still out there somehow? and whats with the numbers on
the right?
it is telling you that, though files have been unlinked, they are still
being accessed by the processes whose pids are listed in that last column.
All of those processes are accessing the file that has inode 446559; thus,
the disk space being used by the file is still in use. As soon as all of
those processes are ended, the disk space associated with that inode will be
freed up, and the filesystem will no longer be in use.
-s---
Sandor W. Sklar - Unix Systems Administrator - Stanford University
ITSS
Non impediti ratione cogitationis.
http://whippet.stanford.edu/~ssklar/
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:07 EDT