1.1.27 dccm crashed

Gary Mills mills@cc.UManitoba.CA
Tue Feb 18 22:35:40 UTC 2003


On Tue, Feb 18, 2003 at 02:27:08PM -0700, Vernon Schryver wrote:
> > From: Gary Mills <mills@cc.UManitoba.CA>
> 
> > > >   mmap(dcc_db-new,0xfc000,0): Resource temporarily unavailable
> 
> The ancient bugs are in Sun's NFS client, not the NFS servers....well,
> I don't know for a fact whether this problem is related to the infamous
> and enduring old Sun NFS locking problems.

As far as I know, Solaris has no NFS locking problems.  They finally
fixed them several years ago.  Current Solaris locking works nicely.

Here's a truss of the failing operation:

write(6, "\0\0\0\0\0\0\0\0\0\0\0\0".., 4096)    = 4096
write(6, "\0\0\0\0\0\0\0\0\0\0\0\0".., 2160)    = 2160
mmap(0x00000000, 1032192, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0) Err#11 EAGAIN
write(2, " m m a p (", 5)                       = 5
write(2, " d c c _ d b - n e w", 10)            = 10

The error means:

     EAGAIN         The mapping could not be locked in memory.

                    There was insufficient room to  reserve  swap
                    space for the mapping.

                    The file to be mapped is already locked using
                    advisory  or  mandatory  record locking.  See
                    fcntl(2).

I don't know which of these would be affected by NFS.

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.