Date: Fri, 31 Aug 2018 15:21:03 -0400 From: Mark Johnston <markjdb@gmail.com> To: Eugene Grosbein <eugen@grosbein.net> Cc: Samuel Chow <cyschow@shaw.ca>, stable@freebsd.org Subject: Re: Cannot setup dumpdev on glabel disk Message-ID: <20180831192103.GC54904@raichu> In-Reply-To: <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net> References: <19f80f48-5fea-e105-18b2-1a64e06acc79@shaw.ca> <6f6685d0-08c6-dbe2-62b5-3628f91917d9@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 01, 2018 at 02:09:12AM +0700, Eugene Grosbein wrote:
> 31.08.2018 23:08, Samuel Chow wrote:
>
> > I am running 11-STABLE, and I am experiencing kernel panics when I am destroying a VIMAGE-based jail. Naturally, I flipped to the chapter about 'Kernel Debugging' to learn about 'Obtaining a Kernel Crash Dump'.
> >
> > However, I am finding that my permanently glabel'ed disk partition cannot be used as dumpdev. Is that true, and why not? I mean, swap can use it just fine. I am unable to find this restriction in the documentation.
> >
> >
> > # grep swap /etc/fstab
> > /dev/label/boot01b none swap sw 0 0
> > # swapinfo
> > Device 1K-blocks Used Avail Capacity
> > /dev/label/boot01b 41943040 0 41943040 0%
> > # glabel status | grep boot
> > label/boot01 N/A ada4s1
> > label/boot02 N/A ada5s1
> > # dumpon /dev/label/boot01b
> > dumpon: ioctl(DIOCSKERNELDUMP): Operation not supported by device
>
> That's not about label but underlying device that seems to be GEOM_PART_MBR
> and it allows kernel dumps only if slice (MBR partition) type is 0xa5 for "freebsd"
> or 0x82 ("linux swap"). Please show output of the command "gpart show ada4".
Ah, right, please ignore my other reply. When I actually test it
myself, dumpon /dev/label/foo seems to work; I assumed the lack of
handling for GEOM::kerneldump in the glabel code was a problem. Sorry
for the noise.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180831192103.GC54904>