On 16 May 2017, at 19:58, Andriy Gapon wrote:
On 16/05/2017 16:49, Kristof Provost wrote:
On 16 May 2017, at 15:41, Andriy Gapon wrote:
On 10/05/2017 12:37, Kristof Provost wrote:
I have a reproducible panic on CURRENT (r318136) doing
(jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-
On 16/05/2017 16:49, Kristof Provost wrote:
> On 16 May 2017, at 15:41, Andriy Gapon wrote:
>> On 10/05/2017 12:37, Kristof Provost wrote:
>>> I have a reproducible panic on CURRENT (r318136) doing
>>> (jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-26 | nc dual 1234
>>> (dual) # nc -l 1
On 16 May 2017, at 15:41, Andriy Gapon wrote:
On 10/05/2017 12:37, Kristof Provost wrote:
I have a reproducible panic on CURRENT (r318136) doing
(jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-26 | nc
dual 1234
(dual) # nc -l 1234 | zfs recv -v -F tank/jupiter/var
For clarity, the
On 10/05/2017 12:37, Kristof Provost wrote:
> Hi,
>
> I have a reproducible panic on CURRENT (r318136) doing
> (jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-26 | nc dual 1234
> (dual) # nc -l 1234 | zfs recv -v -F tank/jupiter/var
>
> For clarity, the receiving machine is CURRENT r31
Hi,
I have a reproducible panic on CURRENT (r318136) doing
(jupiter) # zfs send -R -v zroot/var@before-kernel-2017-04-26 | nc dual
1234
(dual) # nc -l 1234 | zfs recv -v -F tank/jupiter/var
For clarity, the receiving machine is CURRENT r318136, the sending
machine is running a somewhat older
