Personal tools
You are here: Home → Issue tracker → Cannot import zpool after upgrading to GIT version
 

#34 — Cannot import zpool after upgrading to GIT version

State Resolved
Version:
Area Functionality
Issue type Bug
Severity Low
Submitted by (anonymous)
Submitted on Mar 15, 2010
Responsible Seth Heeren
Target release:
—
Return to tracker
Last modified on Apr 21, 2010 by Seth Heeren
In 0.6.0-stable after starting zfs-fuse daemon, 'zpool status' command shows my pool correctly:
---------------------------------------------------------
# /opt/zfs/zfs-fuse
# /opt/zfs/zpool status
  pool: zfsraid
 state: ONLINE
 scrub: none requested
config:

        NAME STATE READ WRITE CKSUM
        zfsraid ONLINE 0 0 0
          raidz1 ONLINE 0 0 0
            mapper/crypto_1 ONLINE 0 0 0
            mapper/crypto_2 ONLINE 0 0 0
            mapper/crypto_3 ONLINE 0 0 0
            mapper/crypto_4 ONLINE 0 0 0
            mapper/crypto_5 ONLINE 0 0 0
            mapper/crypto_6 ONLINE 0 0 0
            mapper/crypto_7 ONLINE 0 0 0
            mapper/crypto_8 ONLINE 0 0 0

errors: No known data errors
---------------------------------------------------------

But after checking out GIT version it says that there are no pools:
---------------------------------------------------------
# /opt/zfs.new/zfs-fuse
# /opt/zfs.new/zpool status
no pools available
---------------------------------------------------------

What's the catch? Or am i doing something wrong?
Pool's devices are device-mapper encrypted devices.
Added by (anonymous) on Mar 15, 2010 05:16 AM
P.S.
Kernel is 2.6.32.8 x86-64, FUSE is 2.8.1
Added by Seth Heeren on Mar 15, 2010 05:24 AM
Severity: Medium → Low
Responsible manager: (UNASSIGNED) → sgheeren
Most likely you have switched to a more recent version that moved zpool.cache from /etc/zfs/zpool.cache to /var/lib/zfs/zpool.cache

If you are caught unaware, this can be surprising.

A 'zpool import' should show the pool normally. You'd either have to copy the zpool.cache (a symlink will do nicely if you switch back and forth a bit) or you might opt to simply re-import.
Added by (anonymous) on Mar 15, 2010 05:25 AM
Huh, after exporting it with 0.6.0 i cannot import it back as it does not scan device-mapper devices for ZFS data:
--------------------------------------------------------
# zpool export zfsraid
# zpool import -v
/dev/sdl... nothing
/dev/sdk... nothing
/dev/sdj... nothing
/dev/sdi... nothing
/dev/sdh... nothing
/dev/sdg... nothing
/dev/sdf... nothing
/dev/sdd1... nothing
/dev/sdb1... nothing
/dev/md0... nothing
/dev/root... nothing
/dev/md1... nothing
/dev/sda1... nothing
/dev/sde... nothing
/dev/sda2... nothing
/dev/sda3... nothing
/dev/.mdadm.map... nothing
/dev/sdc2... nothing
/dev/sdc1... nothing
/dev/sdd... nothing
/dev/sdb... nothing
/dev/sda... nothing
/dev/sdc... nothing
/dev/loop7... nothing
/dev/loop1... nothing
/dev/loop4... nothing
/dev/loop2... nothing
/dev/loop5... nothing
/dev/loop6... nothing
/dev/loop3... nothing
/dev/loop0... nothing
--------------------------------------------------------
Added by Seth Heeren on Mar 15, 2010 05:27 AM
man zpool(1):

zpool import -d /dev/mapper

Recommended Canonical Method: (term invented here)

zpool import -d /dev/disk/by-id

This ensures proper operation with relocating physical disks, or in your case logical volumes
Added by (anonymous) on Mar 15, 2010 05:38 AM
Oops my lame, thank you. '-d dir' in zpool's short help didn't get me on the right way.
Added by Seth Heeren on Apr 21, 2010 01:00 PM
Issue state: unconfirmed → resolved
resolved