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. I guess, if there were many (how many?) such entries, the disk would appear full, if it ran out of inodes. Is that correct? -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
