Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Feb 2023 08:33:48 -0500
From:      Paul Mather <paul@gromit.dlib.vt.edu>
To:        Andrea Venturoli <ml@netfence.it>
Cc:        User Questions <freebsd-questions@freebsd.org>
Subject:   Re: Current swap configuration: best practices?
Message-ID:  <99898374-C698-4077-B52F-54CE547267B8@gromit.dlib.vt.edu>
In-Reply-To: <5cdc2ef0-33e2-9465-0e65-6589b62e4256@netfence.it>
References:  <5cd5040b-d6c9-7c5f-9eae-e7e8a098eaca@chezmarcotte.ca> <5cdc2ef0-33e2-9465-0e65-6589b62e4256@netfence.it>

next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 8, 2023, at 7:07 AM, Andrea Venturoli <ml@netfence.it> wrote:

> On 2/7/23 19:48, Derek (freebsd lists) wrote:
>=20
>> Using ZFS:
>> * enabling mirror swap will break crash dumps
>=20
> Ugh!
> Why so? Any pointer?
> I've got several gmirror-based swap partitions: these boxes did not =
crash in a long time, but I'd expect a coredump, should that happen...
> Any way to test this, instead of waiting for it to happen?


I also have gmirror-based swap partitions set up and have not had =
problems with crash dumps being generated after kernel panics.

There is a special note in the gmirror(8) man page on setting up crash =
dumps.  It's near the end of the man page (on my 13-STABLE system), and =
begins with the sentence, "Doing kernel dumps to gmirror providers is =
possible, but some conditions have to be met."

Cheers,

Paul.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99898374-C698-4077-B52F-54CE547267B8>