Date: Fri, 14 Apr 2017 20:37:30 -0500 From: Larry Rosenman <ler@lerctr.org> To: <rgrimes@freebsd.org> Cc: "Ngie Cooper (yaneurabeya)" <yaneurabeya@gmail.com>, "src-committers@freebsd.org" <src-committers@freebsd.org>, Alan Somers <asomers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, Slawa Olhovchenkov <slw@zxy.spb.ru>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, Ngie Cooper <ngie@freebsd.org> Subject: Re: svn commit: r316938 - head/sbin/savecore Message-ID: <B6B4FC16-55E0-401B-8630-0B8F8C7850BB@lerctr.org> In-Reply-To: <201704150135.v3F1ZD2S009211@pdx.rh.CN85.dnsmgr.net> References: <AB41FBB8-12D6-48D7-BE34-664D2F267A2F@lerctr.org> <201704150135.v3F1ZD2S009211@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/14/17, 8:35 PM, "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> wrote:
> Yeah, I have the following:
> borg.lerctr.org /home/ler $ swapctl -l
> Device: 1024-blocks Used:
> /dev/mfid0p3 8388608 0
> /dev/mfid1p3 8388608 0
> /dev/mfid2p3 8388608 0
> /dev/mfid3p3 8388608 0
> /dev/mfid4p3 8388608 0
> /dev/mfid5p3 8388608 0
> borg.lerctr.org /home/ler $ sysctl hw.physmem
> hw.physmem: 137368682496
> borg.lerctr.org /home/ler $
>
> SO 6 8G partitions (48G), but the dump is larger than 8G.
Larry,
This is a very good concern and point given todays more
common huge memory foot prints and lots of spindles. I'll
keep this in they back of my mind as I tromp around in the
dump code. I have another solution that may work for you
and that is to use Netdump rather than swapdump. This
basically eliminates the trip to swap space and you end
up going to savecore style output on the netdump server.
--
Rod Grimes rgrimes@freebsd.org
What does it take for NetDump to work to a FreeNAS (9.10 nightly) server since that’s what is “next to” this server?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B6B4FC16-55E0-401B-8630-0B8F8C7850BB>