I think you spotted the base problem. I run 2 instances of pflogd since a few of days, and I forgot to set a separate pid file.
I put the new pflogd in log rotation with its own pid file, I hope this will solve the problem. Many, many thanks for the help. -- Cordialement, Pierre BARDOU -----Message d'origine----- De : Otto Moerbeek [mailto:o...@drijf.net] Envoyi : lundi 9 novembre 2009 09:55 @ : BARDOU Pierre Cc : Richard Toohey; misc@openbsd.org Objet : Re: Disk occupation problem On Mon, Nov 09, 2009 at 09:43:24AM +0100, BARDOU Pierre wrote: > Hello, > > I didn't delete anything by hand. > The space comes back after a reboot, yes. > > I found the problem : log rotation with pflogd. > I killed pflogd and started it again, and the free space came back. Do you have more than once instance of pflogd running? Or are you actually ruining current? becasue recently something changed here. -Otto > > But why log rotation fails ? > It worked like a charm since more than 2 years... > > If that helps : > # cat /etc/newsyslog.conf > # $OpenBSD: newsyslog.conf,v 1.26 2007/02/02 14:52:48 ajacoutot Exp $ > # > # configuration file for newsyslog > # > # logfile_name owner:group mode count size when flags > /var/cron/log root:wheel 600 3 10 * Z > /var/log/aculog uucp:dialer 660 7 * 24 Z > /var/log/authlog root:wheel 640 7 * 168 Z > /var/log/daemon 640 5 30 * Z > /var/log/lpd-errs 640 7 10 * Z > /var/log/maillog 600 7 * 24 Z > /var/log/messages 644 5 30 * Z > /var/log/secure 600 7 * 168 Z > /var/log/wtmp 644 7 * $W6D4 ZB > /var/log/xferlog 640 7 250 * Z > /var/log/ppp.log 640 7 250 * Z > #/var/log/pflog 600 3 250 * ZB > /var/run/pflogd.pid > /var/log/pflog 600 3 * 24 ZB > /var/run/pflogd.pid > > > TYVM for the help > > -- > Cordialement, > Pierre BARDOU > > > -----Message d'origine----- > De : Richard Toohey [mailto:richardtoo...@paradise.net.nz] > Envoyi : lundi 9 novembre 2009 09:21 > @ : BARDOU Pierre > Cc : misc@openbsd.org > Objet : Re: Disk occupation problem > > On 9/11/2009, at 9:11 PM, BARDOU Pierre wrote: > > > Hello, > > > > I have a strange problem with disk occupation. > > Df says my disk is nearly full (25G occupied), but when I do a du > > sh on the > > mountpoint it says only 10M used !? > > > > Are you deleting in-use log files? Does the space come back after a > reboot? > > > I had the same problem a few days ago on 4.5-stable ; I upgraded to > > 4.6-stable and it happens again. > > > > Some logs : > > # du -sh /var/ > > 10.7M /var/ > > # du -sh /var/* > > 2.0K /var/account > > 2.0K /var/audit > > 2.0K /var/authpf > > 1.3M /var/backups > > 4.0K /var/crash > > 22.0K /var/cron > > 2.2M /var/db > > 4.0K /var/empty > > 44.0K /var/games > > 12.0K /var/lib > > 4.2M /var/log > > 4.0K /var/lost+found > > 1.1M /var/mail > > 4.0K /var/msgs > > 92.0K /var/named > > 2.0K /var/quotas > > 96.0K /var/run > > 2.0K /var/rwho > > 24.0K /var/spool > > 4.0K /var/tmp > > 1.4M /var/www > > 28.0K /var/yp > > # df -h > > Filesystem Size Used Avail Capacity Mounted on > > /dev/sd0a 3.8G 2.1G 1.5G 59% / > > /dev/sd0d 28.6G 25.0G 2.2G 92% /var > > > > Could someone give me a clue on how to fix this ? > > TYVM > > > > -- > > Cordialement, > > > > Pierre BARDOU > > CSIM - Bureau 012 > > > > > > > > > > 12 rue Michel Labrousse > > BP93668 > > F-31036 Toulouse CEDEX 1 > > > > Til : 05 67 69 71 84 > > Fax : 05 34 61 51 00 > > Mail : bardo...@mipih.fr > > > > [demime 1.01d removed an attachment of type application/x-pkcs7- > > signature which had a name of smime.p7s] > > [demime 1.01d removed an attachment of type application/x-pkcs7-signature which had a name of smime.p7s] [demime 1.01d removed an attachment of type application/x-pkcs7-signature which had a name of smime.p7s]
