DB2 V10.5, RHEL 7.5
We had an issue when DB2 was stuck not being able to write log files to disk because of disk full error just that there was more than enough free disk space on the filesystem that DB2 uses.
For example, we have the folowing filesystem structure:
/a /a/b DB1 database /a/b/c DB1 diagnostics logs /a/b/d DB1 transaction logs /a/b/e DB1 archived logs
I had DIA8312C Disk was full Error (OS) for filesystem /a together with OSERR: ENOSPC (28) and also DIA8312C Disk was full Severe level and many more errors , because filesystem /a was full.
Is this normal, considering that all filesystems that DB2 uses ( /a/b, /a/b/c, a/b/d/..) had enough free space ?