Opened 2 years ago

Closed 2 years ago

#223 closed defect (fixed)

Can't import zpool from FreeBSD 8.1 system

Reported by: riz Owned by:
Priority: major Milestone: 8.0-RELEASE
Component: GUI Version: 8.0-RC4
Keywords: Cc:

Description

Wanting to test zfs import before trying it with live data, I did the following, all under VMware Fusion 3.1.2 on a Mac.

On a FreeBSD 8.1 VM:

  • create a zpool named 'scratch' on a 20GB virtual disk
  • use zpool send/recv from another system to populate it with about 7G of data for testing, creating scratch/netbsd and scratch/netbsd/cvs-mirror file systems
  • zpool export scratch
  • detach the virtual drive

on another VM:

  • create a 2GB virtual disk to install FreeNAS 8.0RC4 on
  • install RC4 from iso image
  • attach the 20GB virtual disk from above (with reboot, etc)
  • attempt to use the auto-importer to import the zfs

The auto-importer lists "scratch" in the dropdown as a mirror (not quite right, but close enough). When I try to import it, I get "some error occurred". I was asked on freenode #freenas to grab the django traceback using firebug, I did so, and it's attached. One other piece of info I was asked for was the output of 'zpool import':

freenas# zpool import

pool: scratch

id: 17724180225838606816

state: ONLINE

status: The pool is formatted using an older on-disk version.
action: The pool can be imported using its name or numeric identifier, though

some features will not be available without an explicit 'zpool upgrade'.

config:

scratch ONLINE

da0 ONLINE

freenas#

...I also attempted to upgrade the zpool to version 15 (was version 14), but it didn't seem to help.

Attachments (1)

Django_traceback.txt (23.6 KB) - added by riz 2 years ago.
Django Traceback from Firebug

Download all attachments as: .zip

Change History (3)

Changed 2 years ago by riz

Django Traceback from Firebug

comment:1 Changed 2 years ago by riz

  • Summary changed from Can't import zpool from FreeBSD 7.1 system to Can't import zpool from FreeBSD 8.1 system

comment:2 Changed 2 years ago by william

  • Resolution set to fixed
  • Status changed from new to closed

This error has been fixed in trunk an will be available in the next public release (8.0.1-BETA3)

Note: See TracTickets for help on using tickets.