named problem on read-only system

We run named on our systems here, normally with no problems. However, in
some cases we make our hard disks read-only, to make systems more resilient
to power losses. We map ramdisks over /var, /tmp, /dev so they'll be
writeable.

named is actually working properly, except that in some cases when a client
accesses a new address that named has to look up, named is reporting:

named[367]: recvfrom: cannot assign requested address

The address lookup still succeeds, but this warning is disconcerting. It
also does *not* occur on every new access; I'd say 50% of new-address
requests result in this warning.

This does NOT occur when the disk is writeable, only in the read-only
environment.

Does anyone have any idea why this is occuring??

our systems:

linux 2.2.19
Bind version 8.2.1

In article <(E-Mail Removed)>, Daniel Miller wrote:
> We run named on our systems here, normally with no problems. However, in
> some cases we make our hard disks read-only, to make systems more resilient
> to power losses. We map ramdisks over /var, /tmp, /dev so they'll be
> writeable.
>
> named is actually working properly, except that in some cases when a client
> accesses a new address that named has to look up, named is reporting:
>
> named[367]: recvfrom: cannot assign requested address
>
> The address lookup still succeeds, but this warning is disconcerting. It
> also does *not* occur on every new access; I'd say 50% of new-address
> requests result in this warning.
>
> This does NOT occur when the disk is writeable, only in the read-only
> environment.
>
> Does anyone have any idea why this is occuring??
>
> our systems:
>
> linux 2.2.19
> Bind version 8.2.1

As a guess, I'd say it's trying to write information to a cache
that is not stored on a writable slice.

--
Seth H Holmes