SOLVED Unable to import zpools from OpenIndiana

[trondmm]

Hi.

I have a fresh install of FreeNAS 11.1-U6, and I'm trying to import zpools used in OpenIndiana oi151a

If i do a zpool import -a in the shell, the pools are imported correctly, with all filesystems. But, if I try do import them through the GUI (after exporting), the import fails with the error "out of space"

Code:

[2018/11/18 10:32:48] (ERROR) ZFSDatasetService.do_create():260 - Failed to create dataset
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/middlewared/plugins/zfs.py", line 258, in do_create
	pool.create(data['name'], params, fstype=getattr(libzfs.DatasetType, data['type']), sparse_vol=sparse)
  File "libzfs.pyx", line 1906, in libzfs.ZFSPool.create
libzfs.ZFSException: out of space

After this failed attempt to import the pool, the pool has actually been imported, but only the top level zfs filesystem is available, with no free space available.
In "View Volumes", the pool, with all its filesystems, is visible.

If I try to import the pool in the shell again, it'll now fail to mount the filesystems, and the top level filesystem now shows no free space available.

(It's still possible to import the volumes in openindiana, though, so no harm done, so far :) )

Any ideas how to fix this?


Motherboard: Supermicro X9SCM-F
SAS-controller: LSI 2008
Expanders/Blackplanes: Supermicro 846E1-R900B / Supermicro 847E16-RJBOD1

 

[kdragon75]

Do you have all space in use or reserved? I believe FreeNAS tries to create its own .system dataset if it does not already
have one.

libzfs.ZFSPool.create libzfs.ZFSException: out of space

 

[trondmm]

It's fuller than I'd like, but there's still room on it.

Code:

trondmm@openindiana:~$ zpool list bigpool
NAME	  SIZE  ALLOC   FREE  EXPANDSZ	CAP  DEDUP  HEALTH  ALTROOT
bigpool	29T  28,3T   725G		 -	97%  1.00x  ONLINE  -

 

[Ericloewe]

File a bug report and post the issue number here. Don't forget to tell the devs that you know the pool is dangerously full and intend on fixing that, otherwise they might not care.

 

[trondmm]

OK, I'm getting a little bit closer.

First of all, you're right about .system. I set the system dataset pool to use freenas-boot (I know it's not recommended). That got rid of the error message.

But, FreeNAS still believes that the pool has no available space, and it seems that this is the root problem.

Code:

root@freenas:~ # zpool list bigpool
NAME	  SIZE  ALLOC   FREE  EXPANDSZ   FRAG	CAP  DEDUP  HEALTH  ALTROOT
bigpool	29T  28.3T   725G		 -	  -	97%  1.00x  ONLINE  /mnt
root@freenas:~ # zfs list bigpool
NAME	  USED  AVAIL  REFER  MOUNTPOINT
bigpool  28.3T	  0  5.83T  /mnt/bigpool

This is why the other datasets "disappears", as FreeNAS can't mount them inside bigpool.

 

[Ericloewe]

Ah, figures, you probably have a reservation clogging things up. Go through your datasets and figure out where it is and remove it.

 

[trondmm]

I still haven't found out why FreeNAS and OpenIndiana reports different space available, and I didn't see any reserved space set on any of the datasets. However, it was as simple as clearing up some space.

I had a dataset on bigpool that I had already migrated to a different pool, but I had forgotten to remove the old one. So, I destroyed that, and tried again. Now it imported without any problems.

Thanks for the help.