-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Sep 26, 2016 at 04:38:01PM +0200, Tony van der Hoff wrote: > On 26/09/16 16:03, to...@tuxteam.de wrote: > > On Mon, Sep 26, 2016 at 12:54:49PM +0200, Erwan David wrote: > > > >> A possibility is that you have processes writing into deleted files. You > >> can see them with lsof +L1 (as root) > > > > Short and sweet. That's even better :-) > > > That's great; thanks Tomas and Erwan (and others who replied). > > So, I'm seeing this: > > root@shell:~# lsof +L1 > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME > mysqld 3164 mysql 4u REG 254,16 0 0 589839 > /tmp/ibvh7MKT (deleted) > mysqld 3164 mysql 5u REG 254,16 0 0 589840 > /tmp/ibT7D133 (deleted) > mysqld 3164 mysql 6u REG 254,16 0 0 589845 > /tmp/ibO9pgne (deleted) > mysqld 3164 mysql 7u REG 254,16 0 0 589851 > /tmp/ibOgMl6y (deleted) > mysqld 3164 mysql 11u REG 254,16 0 0 589852 > /tmp/ibON9JEJ (deleted) > > My interpretation is that mysql has 5 deleted files of 0 size open which > are each taking up an inode. ls /tmp is empty.
That's how I read that too. > I guess, if there were many (how many?) such entries, the disk would > appear full, if it ran out of inodes. > > Is that correct? Yes -- but you'd need a lot of inodes. I'd expect the mysql process to run into some limit on open files earlier. You can get an idea of the state of your file system with "tune2fs -l" (I'm assuming ext2/3/4 here). Regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlfpORYACgkQBcgs9XrR2kZouQCfYP4XLmlzWH5Zes4Nmcj+MoDx GOkAnRwwlzQD+QoxEuzNQdcZo5sKlzdH =h5zW -----END PGP SIGNATURE-----
