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 days ago, when I had all 4 devices
>> available.
>
> I don't think that the error is really about the missing devices.
> Most likely the real problem is that you are going too far back in history
where
> the data required to import the pool is not present. It's just that
there is no
> special error code to report that condition distinctly, so it gets
interpreted
> as a missing device condition.
Sounds reasonable.
When the RAM-corruption happened, a live update was started, where
several pool availability checks were done. No data write.
Last data write were view KBytes some minutes before the corruption, and
the last significant ammount written to that pool was long time before that.
So I still have hope to find an importable txg ID.
Are they strictly serialized?
Dou you know any other possibility to get data from a dataset (by
objetct id) without importing the whole pool?
zdz successfully checks the one datset (object ID) I'm interested in;
the rest of the pool isnt much an issue...
Thank you very much for your help!
-harry