Re: [discuss] assertion failed: space_map_open

2014-10-31 Thread Alexander Pyhalov via illumos-discuss
On 10/24/2014 17:48, Alexander Pyhalov via illumos-discuss wrote: Hello. I was moving OI Hipster installation from physical server to KVM VM. So I was continuing my attempts to move zfs pool to another host. Funny, but it already takes about a week. I decided to move zfs filesystems one by

Re: [discuss] assertion failed: space_map_open

2014-10-25 Thread George Wilson via illumos-discuss
On 10/25/14, 2:09 PM, Alexander Pyhalov wrote: One other question, do you have an old 'zpool status' of the pool you're trying to import? I'm trying to verify that the pool configuration shown above under $import looks correct to you. Should that pool have more than one device? Is that the

[discuss] assertion failed: space_map_open

2014-10-24 Thread Alexander Pyhalov via illumos-discuss
Hello. I was moving OI Hipster installation from physical server to KVM VM. I've created two lvm-based disks (the same size as original LUNs) and used dd to copy content from physical disks to LVM volumes. One disk is root pool (32 GB) and another one is data pool (512 GB). After turning VM

Re: [discuss] assertion failed: space_map_open

2014-10-24 Thread Alexander Pyhalov via illumos-discuss
On 10/24/2014 17:48, Alexander Pyhalov via illumos-discuss wrote: Hello. ... Any ideas what could go wrong? I suppose that it could be just data corruption (but why?). Of course, I can just recreate the data pool and send/recv data from physical server to VM, but the whole panic looks

Re: [discuss] assertion failed: space_map_open

2014-10-24 Thread George Wilson via illumos-discuss
This looks like it could be caused by illumos bug# 5213. We are trying to push a fix upstream but it's still out for review: https://reviews.csiden.org/r/110/ Can you please provide the ::spa -v output from the core file? Thanks, George On 10/24/14, 9:48 AM, Alexander Pyhalov via