Date: Mon, 22 Aug 2022 12:50:28 +0200 From: Santiago Martinez <sm@codenetworks.net> To: Toomas Soome <tsoome@me.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: kernel panic during zfs pool import Message-ID: <9b89b67a-567d-12e8-ac17-4bb529b9d0e3@codenetworks.net> In-Reply-To: <d252839b-8e70-cbbb-8da0-713d2e554e1e@codenetworks.net> References: <b70a200f-886a-a884-c409-8028b706ff1e@codenetworks.net> <5F75D096-F28C-436E-B5C0-4A0EFA7A5F3C@me.com> <d252839b-8e70-cbbb-8da0-713d2e554e1e@codenetworks.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Still the same with current.....(from today).
Opening a PR for it..
Santi
On 8/22/22 10:43, Santiago Martinez wrote:
> Thanks Toommas,
> I compiling current right now and will give it a try, hopefully, will
> be able to mount and recover the machine.
> Will also open a PR as even if the is any corruption/pool damage it
> should not panic the machine.
>
> Santi
>
>
> On 8/18/22 21:45, Toomas Soome wrote:
>>
>>
>>> On 18. Aug 2022, at 18:46, Santiago Martinez <sm@codenetworks.net>
>>> wrote:
>>>
>>> Hi everyone,
>>>
>>> I have a server running 13.1-stable that was powered off
>>> (gracefully) and now is been powered on again and we have the
>>> following problem.
>>>
>>> The server boots almost properly, kernel load and when zfs import
>>> other pools it panic with the following message.
>>>
>>> "panic : Solaris (panic) zfs: adding existent segment to range tree
>>> (offset=4af2ca9000 size=a0000)".
>>>
>>> if i boot into single user and the pools (most specifically pool01 )
>>> is not imported then there is no panic. but as soon as we try to
>>> import pool01 we get that panic error. it worth mentioning that the
>>> pool imported/online before.
>>>
>>> Have two question:
>>>
>>> * How i can tell to not import the pool automatically during boot
>>> so sever is not stuck in a boot/panic/reboot infinite loop?
>>
>> removing zpool.cache should do. unfortunately, you would need to boot
>> alternate root (usb/cd/net) for that.
>>
>>>
>>> * Anybody know what this panic means?
>>>
>>
>> in short - bug. I’d try to boot current and import pool there - maybe
>> the issue is fixed in current…
>>
>> rgds,
>> toomas
>>
>>> Thanks in advance!
>>>
>>> Santi
>>>
>>>
>>>
>>
[-- Attachment #2 --]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Still the same with current.....(from today).</p>
<p>Opening a PR for it.. <br>
</p>
<p>Santi</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 8/22/22 10:43, Santiago Martinez
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d252839b-8e70-cbbb-8da0-713d2e554e1e@codenetworks.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
Thanks Toommas, <br>
I compiling current right now and will give it a try, hopefully,
will be able to mount and recover the machine. <br>
Will also open a PR as even if the is any corruption/pool damage
it should not panic the machine.<br>
<p>Santi</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 8/18/22 21:45, Toomas Soome wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5F75D096-F28C-436E-B5C0-4A0EFA7A5F3C@me.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On 18. Aug 2022, at 18:46, Santiago Martinez
<<a href="mailto:sm@codenetworks.net"
class="moz-txt-link-freetext" moz-do-not-send="true">sm@codenetworks.net</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">Hi everyone,<br class="">
<br class="">
I have a server running 13.1-stable that was powered off
(gracefully) and now is been powered on again and we
have the following problem.<br class="">
<br class="">
The server boots almost properly, kernel load and when
zfs import other pools it panic with the following
message.<br class="">
<br class="">
"panic : Solaris (panic) zfs: adding existent segment to
range tree (offset=4af2ca9000 size=a0000)".<br class="">
<br class="">
if i boot into single user and the pools (most
specifically pool01 ) is not imported then there is no
panic. but as soon as we try to import pool01 we get
that panic error. it worth mentioning that the pool
imported/online before.<br class="">
<br class="">
Have two question:<br class="">
<br class="">
* How i can tell to not import the pool automatically
during boot so sever is not stuck in a boot/panic/reboot
infinite loop?<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>removing <span style="font-family: Hack;
background-color: rgb(255, 255, 255);" class="">zpool.cache
should do. unfortunately, you would need to boot alternate
root (usb/cd/net) for that.</span></div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
* Anybody know what this panic means?<br class="">
<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>in short - bug. I’d try to boot current and import pool
there - maybe the issue is fixed in current…</div>
<div><br class="">
</div>
<div>rgds,</div>
<div>toomas</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">Thanks in advance!<br class="">
<br class="">
Santi<br class="">
<br class="">
<br class="">
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</blockquote>
</blockquote>
</body>
</html>
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9b89b67a-567d-12e8-ac17-4bb529b9d0e3>