From: Green, Simon (SGreen@KRAFTEUROPE.COM)
Date: Mon Aug 05 2002 - 13:13:50 EDT
What has happened is that syslogd, (or some other process) was writing to
one or more log files in your filesystem. You deleted those files, but
syslogd still has them open. If you compare df and du output, you should
spot a discrepancy. (This is quite common.)
Those numbers at the end are the PIDs writing to the unlinked files. I'm
not sure what the suffix represents.
To sort things out, you need to stop whatever is writing to those files. If
it's just syslogd, then stopsrc/startsrc should do the trick.
Simon Green
Philip Morris ITSC Europe
AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l
<http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2> &r=1&w=2
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
<http://www.faqs.org/faqs/aix-faq/>
N.B. Unsolicited email from vendors will seldom be appreciated.
-----Original Message-----
From: Forkner, Robert [mailto:forknerr@ACU.EDU]
Sent: 05 August 2002 17:43
To: aix-l@Princeton.EDU
Subject: Re: Unable to unmount a filesystem
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?
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:06 EDT