[ previous ] [ next ] [ threads ]
 
 From:  "Chris Buechler" <cbuechler at gmail dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] DHCP; file system full
 Date:  Tue, 22 Jan 2008 23:27:21 -0500
On Jan 22, 2008 9:08 PM, Forest Bond <forest dot bond at logicsupply dot com> wrote:
> Hi,
>
> Thanks for your response.
>
> On Tue, Jan 22, 2008 at 07:39:46PM -0500, Christopher M. Iarocci wrote:
> > Forest Bond wrote:
> >> A customer is seeing "file system full" messages in his logs:
> >>
> >> Jan 15 12:21:56 monogw-rmueznet /kernel: pid 104 (dhcpd), uid 0 on /: file system full
> >> Jan 15 12:25:15 monogw-rmueznet /kernel: pid 104 (dhcpd), uid 0 on /: file system full
> >> Jan 15 12:26:36 monogw-rmueznet /kernel: pid 104 (dhcpd), uid 0 on /: file system full
> >>
> >> At this point the m0n0wall box is unable to provide more DHCP leases.
> >>
> >> If I understand things correctly, the file system in this case is in memory.
> >> Would adding more memory to the machine solve this problem?  It currently has
> >> 256MB.
>
> > Yes, the file system is in memory so adding memory should solve that issue.
> > However, look at the system status page and see if it is actually using
> > all memory to verify.
>
> He said that the system status page does *not* indicate that memory is
> exhausted.  How could this be?
>

Because only a fixed portion of the memory is for the filesystem, only
a portion of the memory is being exhausted.


> But, given enough memory, and assuming limited WAN bandwidth, the machine
> *should* be able to handle the load, right?
>

See my last post in this thread.

-Chris