Hello, I've hit this same problem.
Hernan/Victor, I sent you an email asking for the description of this solution.
I've also got important data on my array. I went to b93 hoping there'd be a
patch for this.
I caused the problem in a manner identical to Hernan; by removing a zvol clone.
Exact same symptoms, userspace seems to go away, network stack is still up, no
disk activity, system never recovers.
If anyone has the solution to this, PLEASE help me out. Thanks a million in
advance.
Aaron
Well, finally managed to solve my issue, thanks to
the invaluable help of Victor Latushkin, who I can't
thank enough.
I'll post a more detailed step-by-step record of what
he and I did (well, all credit to him actually) to
solve this. Actually, the problem is still there
(destroying a huge zvol or clone is slow and takes a
LOT of memory, and will die when it runs out of
memory), but now I'm able to import my zpool and all
is there.
What Victor did was hack ZFS (libzfs) to force a
rollback to abort the endless destroy, which was
re-triggered every time the zpool was imported, as it
was inconsistent. With this custom version of libzfs,
setting an environment variable makes libzfs to
bypass the destroy and jump to rollback, undoing
the last destroy command.
I'll be posting the long version of the story soon.
Hernán
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
