In this example, my user couldn’t understand why filesystem usage was still so high considering he had removed and zipped up some files. It was still showing 99% used.
Checking errpt showed:
LABEL: J2_FS_FULL
IDENTIFIER: F7FA22C9
Date/Time: Sat 14 Oct 13:50:00 2017
Sequence Number: 47470
Machine Id: 00C9A2F04C00
Node Id: xxxxxxxxxxx
Class: O
Type: INFO
WPAR: Global
Resource Name: SYSJ2
Description
UNABLE TO ALLOCATE SPACE IN FILE SYSTEM
Probable Causes
FILE SYSTEM FULL
Recommended Actions
INCREASE THE SIZE OF THE ASSOCIATED FILE SYSTEM
REMOVE UNNECESSARY DATA FROM FILE SYSTEM
USE FUSER UTILITY TO LOCATE UNLINKED FILES STILL REFERENCED
Detail Data
JFS2 MAJOR/MINOR DEVICE NUMBER
000A 0009
FILE SYSTEM DEVICE AND MOUNT POINT
/dev/hd1, /home |
So using that last recommended action when we use fuser as follows we see :
fuser -dV /home /home: inode=12409 size=633888747 fd=1 7274534 inode=12409 size=633888747 fd=1 12648680 inode=12409 size=633888747 fd=1 13762622 |
This is telling us there are 3 files that have been removed but are being used by an existing process, the PID of which is that last number.
Indeed, checking my process table I could see those three PID’s still exist. In order for the space to be released these processes need to be stopped.
