Prev: postmulti: inet_interfaces for each instance ?
Next: looking for solution
From: Stan Hoeppner on 2 Mar 2010 21:12
donovan jeffrey j put forth on 3/1/2010 8:06 AM:
> Greetings
>
> I had several of these on my primary MX this weekend and one just popped
> up. Can someone explain where this Insufficient system storage is ?

What filesystem are you using? Are you running out of inodes?

/$ df -i

--
Stan

From: Wietse Venema on 2 Mar 2010 21:28
Wietse Venema:
> donovan jeffrey j:
> >
> > On Mar 2, 2010, at 7:31 PM, Daniel V. Reinhardt wrote:
> >
> > >> this is default on all my systems.
> > >
> > >>
> > >> MX1
> > >> /dev/disk1s3 77G 51G 26G 66% /
> > >>
> > >> MX2
> > >> /dev/disk0s3 234G 46G 187G 20% /
> > >>
> > >>
>
> It may be worthwhile to run the Postfix fsspace test program.

Not needed. The Postfix SMTP server logs this with verbose mode
turned on:

msg_info("%s: blocks %lu avail %lu min_free %lu msg_size_limit %lu",
myname,
(unsigned long) fsbuf.block_size,
(unsigned long) fsbuf.block_free,
(unsigned long) var_queue_minfree,
(unsigned long) var_message_limit);

That is, it logs the file system blocksize, the number of free
blocks, and the "queue_minfree" and "message_size_limit" Postfix
parameter values.

Based on these, it decides if the number of free blocks is more
than queue_minfree, and if the message size limit in blocks is less
than the free blocks/1.5.

Wietse

> - Download any Postfix source code that compiles on your system.
>
> - cd into the source tree, then execute the following commands:
>
> make makefiles
> cd src/util
> make fsspace
> ./fsspace /var/spool/postfix
>
> and report if the numbers look wrong.
>
> Postfix uses the fsspace routine to determine the amount of
> free space in the queue file system.
>
> Wietse
>
>

From: donovan jeffrey j on 2 Mar 2010 22:54

On Mar 2, 2010, at 9:03 PM, Wietse Venema wrote:

> It may be worthwhile to run the Postfix fsspace test program.
>
> - Download any Postfix source code that compiles on your system.
>
> - cd into the source tree, then execute the following commands:
>
> make makefiles
> cd src/util
> make fsspace
> ./fsspace /var/spool/postfix
>
> and report if the numbers look wrong.
>
> Postfix uses the fsspace routine to determine the amount of
> free space in the queue file system.
>
> Wietse

mx1:/usr/local/postfix-2.7.0/src/util root# ./fsspace /var/spool/postfix
/var/spool/postfix: block size 4096, blocks free 6836216
mx1:/usr/local/postfix-2.7.0/src/util root# df -i
Filesystem 512-blocks Used Avail Capacity
iused ifree %iused Mounted on
/dev/disk0s3 160574256 105372640 54689616 66%
13235578 6836202 66% /
devfs 198 198 0 100%
590 0 100% /dev
fdesc 2 2 0 100%
4 253 2% /dev
<volfs> 1024 1024 0 100%
0 0 100% /.vol
/dev/disk1s3 489972528 46944240 443028288 10% 5868028
55378536 10% /Volumes/SSHD2
automount -nsl [212] 0 0 0 100%
0 0 100% /Network
automount -fstab [223] 0 0 0 100%
0 0 100% /automount/Servers
automount -static [223] 0 0 0 100%
0 0 100% /automount/static
/dev/disk2s3 489972528 105210640 384761888 21% 13151328
48095236 21% /Volumes/MX1



I was sitting on a memory upgrade, and I through some in , possibly
some Virtual memory foo in the OS. i also did a block level clone to
another larger drive /dev/disk2s3 as a backup. did a reboot. nothing
yet. I'lll have to wait and see if maybe the reboot makes this vanish.
still running on original drive. maybe the drive isn't so S.M.A.R.T

stay tuned. :)

-j

From: Wietse Venema on 3 Mar 2010 00:09
donovan jeffrey j:
>
> On Mar 2, 2010, at 9:03 PM, Wietse Venema wrote:
>
> > It may be worthwhile to run the Postfix fsspace test program.
> >
> > - Download any Postfix source code that compiles on your system.
> >
> > - cd into the source tree, then execute the following commands:
> >
> > make makefiles
> > cd src/util
> > make fsspace
> > ./fsspace /var/spool/postfix
> >
> > and report if the numbers look wrong.
> >
> > Postfix uses the fsspace routine to determine the amount of
> > free space in the queue file system.
> >
> > Wietse
>
> mx1:/usr/local/postfix-2.7.0/src/util root# ./fsspace /var/spool/postfix
> /var/spool/postfix: block size 4096, blocks free 6836216

That would be 26 GBytes.

> Filesystem 512-blocks Used Avail Capacity
> iused ifree %iused Mounted on
> /dev/disk0s3 160574256 105372640 54689616 66%
> 13235578 6836202 66% /

And that's 26 GBytes as well.

It would be interesting to see what Postfix smtpd logs. You can
turn it on selectively

postconf -e debug_peer_list=127.0.0.1
postfix reload

Then do "telnet 127.0.0.1 25", and "grep smtpd_check_queue /the/maillog/file".

You can kill the logging with

postconf -e debug_peer_list=

Wietse

From: donovan on 6 Mar 2010 19:36

On Mar 3, 2010, at 5:24 PM, Wietse Venema wrote:

> donovan jeffrey j:
>> Mar 3 09:49:59 mx1 postfix/smtp[1054]: name_mask: resource
>> Mar 3 09:49:59 mx1 postfix/smtp[1054]: name_mask: software
>> Mar 3 09:49:59 mx1 postfix/qmgr[603]: 0529299C4604: removed
>> Mar 3 09:49:59 mx1 postfix/smtp[1054]: < 127.0.0.1[127.0.0.1]: 220
>> [127.0.0.1] ESMTP amavisd-new service ready
>
> You need to instrument the smtpd process after the content filter,
>
> Wietse
>

This turned out to be an Autowhitelist growing out of control in /var/
clamav/.spamassassin

68816850944 Mar 6 16:39 auto-whitelist

I suspect something is up with this heap.
-j

First  |  Prev  | 
Pages: 1 2
Prev: postmulti: inet_interfaces for each instance ?
Next: looking for solution