On Tue, Jan 22, 2008 at 01:43:27PM -0800, Dan Anderson wrote:
> > Is this *all* that was in the log?
>
> Here's some more context from system-idmap:default.log. It's too bad
> the error message ("database is full") isn't more specific. Hard to
> know what's going on or how to fix it with error messages like that!
I'll file a CR about the database full issue.
> Here's the two databases you mention. The system has plenty of memory
> (1GB) and more of swap:
> # swap -l
> swapfile dev swaplo blocks free
> /dev/dsk/c1d0s1 102,1 8 1220928 1116568
>
> # ls -l /var/idmap/idmap* /var/run/idmap/idmap*
> -rw------- 1 daemon daemon 5120 Dec 24 16:28 /var/idmap/idmap.db
> -rw------- 1 daemon daemon 7168 Jan 22 10:46 /var/run/idmap/idmap.db
Strange.
> Here's a pstack of the core. The core's are at
> http://dan.drydog.com/tmp/core.idmapd.1200940606 and core.idmapd.1200992205
>
> core 'core.idmapd.1200940606' of 500: /usr/lib/idmapd
> ----------------- lwp# 1 / thread# 1 --------------------
> [...]
> ----------------- lwp# 3 / thread# 3 --------------------
> 08061f2a idmap_lookup_batch_start (0, 2, d0d7da54) + 16
> [...]
That's:
6630586 idmap panic: process termintated by SIGSEGV
Nico
--
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
