Date: Sun, 16 Sep 2018 15:16:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231400] Crashdumping to a geom mirror doesn't result in /var/crash being populated Message-ID: <bug-231400-227-jL4daqrNWU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231400-227@https.bugs.freebsd.org/bugzilla/> References: <bug-231400-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231400 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |markj@FreeBSD.org --- Comment #2 from Mark Johnston <markj@FreeBSD.org> --- Did you follow the notes from the man page? Doing kernel dumps to gmirror providers is possible, but some conditio= ns have to be met. First of all, a kernel dump will go only to one component and gmirror always chooses the component with the highest priority. Reading a dump from the mirror on boot will only work if the prefer balance algorithm is used (that way gmirror will read only from the component with the highest priority). If you use a different bala= nce algorithm, you should add: gmirror configure -b prefer data to the /etc/rc.early script and: gmirror configure -b round-robin data to the /etc/rc.local script. The decision which component to choose f= or dumping is made when dumpon(8) is called. If on the next boot a component with a higher priority will be available, the prefer algorit= hm will choose to read from it and savecore(8) will find nothing. If on = the next boot a component with the highest priority will be synchronized, = the prefer balance algorithm will read from the next one, thus will find nothing there. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231400-227-jL4daqrNWU>