Bezüglich Harry Schmalzbauer's Nachricht vom 03.10.2017 16:39 (localtime):
> Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 16:28 (localtime):
>> On 03/10/2017 17:19, Harry Schmalzbauer wrote:
>>> Have tried several different txg IDs, but the latest 5 or so lead to the
>>> panic and some other
Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 16:28 (localtime):
> On 03/10/2017 17:19, Harry Schmalzbauer wrote:
>> Have tried several different txg IDs, but the latest 5 or so lead to the
>> panic and some other random picked all claim missing devices...
>> Doh, if I only knew about -T some d
On 03/10/2017 17:19, Harry Schmalzbauer wrote:
> Have tried several different txg IDs, but the latest 5 or so lead to the
> panic and some other random picked all claim missing devices...
> Doh, if I only knew about -T some days ago, when I had all 4 devices
> available.
I don't think that the err
Bezüglich Andriy Gapon's Nachricht vom 03.10.2017 11:20 (localtime):
> On 03/10/2017 11:43, Harald Schmalzbauer wrote:
> ...
>> action: The pool can be imported despite missing or damaged devices. The
>> fault tolerance of the pool may be compromised if imported.
> ...
>> Is it impossibl
On 03/10/2017 11:43, Harald Schmalzbauer wrote:
...
> action: The pool can be imported despite missing or damaged devices. The
> fault tolerance of the pool may be compromised if imported.
...
> Is it impossible to import degraded pools in general, or only together> with
> "-X -T"?
It sh
Bezüglich Harry Schmalzbauer's Nachricht vom 02.10.2017 20:28 (localtime):
> Bezüglich Andriy Gapon's Nachricht vom 02.10.2017 13:49 (localtime):
>> On 01/10/2017 00:38, Harry Schmalzbauer wrote:
>>> Now my striped mirror has all 4 devices healthy available, but all
>>> datasets seem to be lost.
>
Bezüglich Andriy Gapon's Nachricht vom 02.10.2017 13:49 (localtime):
> On 01/10/2017 00:38, Harry Schmalzbauer wrote:
>> Now my striped mirror has all 4 devices healthy available, but all
>> datasets seem to be lost.
>> No problem for 450G (99,9_%), but there's a 80M dataset which I'm really
>> mis
Bezüglich Scott Bennett's Nachricht vom 01.10.2017 15:20 (localtime):
> On Sat, 30 Sep 2017 23:38:45 +0200 Harry Schmalzbauer
>
> wrote:
…
>>
>> OpenIndiana also panics at regular import.
>> Unfortunately I don't know the aequivalent of vfs.zfs.recover in OI.
>>
>> panic[cpu1]/thread=ff
On 01/10/2017 00:38, Harry Schmalzbauer wrote:
> Now my striped mirror has all 4 devices healthy available, but all
> datasets seem to be lost.
> No problem for 450G (99,9_%), but there's a 80M dataset which I'm really
> missing :-(
If it's not too late now, you may try to experiment with an "unwi
On Sat, 30 Sep 2017 23:38:45 +0200 Harry Schmalzbauer
wrote:
> Bez?glich Harry Schmalzbauer's Nachricht vom 30.09.2017 19:25 (localtime):
>> Bez?glich Harry Schmalzbauer's Nachricht vom 30.09.2017 18:30 (localtime):
>>> Bad surprise.
>>> Most likely I forgot to stop a PCIe-Passthrough NIC b
Bezüglich Harry Schmalzbauer's Nachricht vom 30.09.2017 19:25 (localtime):
> Bezüglich Harry Schmalzbauer's Nachricht vom 30.09.2017 18:30 (localtime):
>> Bad surprise.
>> Most likely I forgot to stop a PCIe-Passthrough NIC before shutting down
>> that (byhve(8)) guest – jhb@ helped my identifyi
Bezüglich Harry Schmalzbauer's Nachricht vom 30.09.2017 18:30 (localtime):
> Bad surprise.
> Most likely I forgot to stop a PCIe-Passthrough NIC before shutting down
> that (byhve(8)) guest – jhb@ helped my identifying this as the root
> cause for sever memory corruptions I regularly had (on stab
Bad surprise.
Most likely I forgot to stop a PCIe-Passthrough NIC before shutting down
that (byhve(8)) guest – jhb@ helped my identifying this as the root
cause for sever memory corruptions I regularly had (on stable-11).
Now this time, corruption affected ZFS's RAM area, obviously.
What I haven
13 matches
Mail list logo
