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/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 ?

closed as off-topic by mustaccio, hot2use, Marco, John Eisbrener, Paul White Mar 2 at 14:47

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Too localized - this could be because your code has a typo, basic error, or is not relevant to most of our audience. Consider revising your question so that it appeals to a broader audience. As it stands, the question is unlikely to help other users (regarding typo questions, see this meta question for background)." – mustaccio, Marco, Paul White
If this question can be reworded to fit the rules in the help center, please edit the question.

  • db2 doesn't calculate any free space itself. It got an error from the corresponding OS call probably. Check ulimit / disk quotas for the db2 instance owner. – Mark Barinstein Feb 21 at 14:56
  • Which logs exactly are you talking about? Diagnostic logs? Transaction logs? Are all the directories you show different mount points of different file systems? What else is using the file system in question? – mustaccio Feb 25 at 14:50
  • both of them, they have separate filesystems – boncalo mihai Feb 27 at 13:44

It seems that the OS was rebooted without shutting down the database and during shutdown process, after some filesystems were unmounted , the database dumped some errors on the same path were one of the filesystems was mounted. After server came up, the filesystem was automatically mounted on top of those files dumped by db2 thus they couldn't be seen.

  • +1 for reporting back the solution. – Lennart Mar 3 at 17:34

Not the answer you're looking for? Browse other questions tagged or ask your own question.