From owner-freebsd-stable@FreeBSD.ORG Wed Oct 25 10:25:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1102216A492 for ; Wed, 25 Oct 2006 10:25:13 +0000 (UTC) (envelope-from dmitry@atlantis.dp.ua) Received: from postman.atlantis.dp.ua (postman.atlantis.dp.ua [193.108.47.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A74243D69 for ; Wed, 25 Oct 2006 10:25:06 +0000 (GMT) (envelope-from dmitry@atlantis.dp.ua) Received: from atlantis.dp.ua (localhost [127.0.0.1]) by postman.atlantis.dp.ua (8.13.1/8.13.1) with ESMTP id k9PAOb59093316; Wed, 25 Oct 2006 13:24:43 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Received: from localhost (dmitry@localhost) by atlantis.dp.ua (8.13.1/8.13.1/Submit) with ESMTP id k9PAObDA093306; Wed, 25 Oct 2006 13:24:37 +0300 (EEST) (envelope-from dmitry@atlantis.dp.ua) Date: Wed, 25 Oct 2006 13:24:37 +0300 (EEST) From: Dmitry Pryanishnikov To: Yoshihiro Ota In-Reply-To: <20061024233520.528b9f9d.ota@j.email.ne.jp> Message-ID: <20061025125123.K78719@atlantis.atlantis.dp.ua> References: <453DADC1.9090201@webmail.sub.ru> <20061024233520.528b9f9d.ota@j.email.ne.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Stable Subject: Re: out of memory in restore? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Oct 2006 10:25:13 -0000 Hello! On Tue, 24 Oct 2006, Yoshihiro Ota wrote: > I think you have to extend your user space memory by adding the > following to /boot/loader.conf. If 5.4-RELEASE doesn't support > these options, adjust your kernel. > > kern.maxdsiz="2048m" > kern.maxssiz="1024m" Well, the original poster didn't mention whether he's tried to restore in single or multiuser mode. This actually makes a big difference. On my RELENG_6 test system (csup-ped and rebuilt as of 24-Oct-2006) I still see that process resource limits in singleuser mode are _way_ too low. Here is multiuser mode root limits (as set in /etc/login.conf; system-wide limits are even higher as I have kern.max{d,s,t}siz="1G" in my /boot/loader.conf): root@test# limits Resource limits (current): cputime infinity secs filesize infinity kB datasize 524288 kB stacksize 524288 kB coredumpsize infinity kB memoryuse 131072 kB memorylocked 65536 kB maxprocesses 512 openfiles 600 sbsize infinity bytes vmemoryuse infinity kB However when I reboot into the singleuser mode (boot -s from the loader prompt), I see the following: # swapon -a && mount -a && limits -B Resource limits (current): cputime infinity secs filesize infinity kB datasize-max 1048576 kB datasize-cur 131072 kB stacksize-max 1048576 kB stacksize-cur 8192 kB coredumpsize infinity kB memoryuse-max infinity kB memoryuse-cur 1016100 kB memorylocked-max 1016100 kB memorylocked-cur 338700 kB maxprocesses 6164 openfiles 12328 sbsize infinity bytes vmemoryuse infinity kB I fail to see where those super-low datasize-cur and stacksize-cur get set (the aren't in /.profile nor in /etc/profile nor in ~root/.profile), but they could prevent using the memory-hungry application (I suppose I can call restore a memory-hungry). > Hiro > > On Tue, 24 Oct 2006 10:08:01 +0400 > Alex Povolotsky wrote: > >> Hello! >> >> I've tried an interactive restore from a dump, and glob fails, so >> restore fails with "out of memory". Is my dump useless now? >> >> (dumped and tried to restore under 5.4-RELEASE) >> >> Alex. Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: dmitry@atlantis.dp.ua nic-hdl: LYNX-RIPE