[zfs-discuss] zpool always thinks it's mounted on another system

[Rich]

Hi zfs-discuss,

I was running Solaris 11, b42 on x86, and I tried upgrading to b44. I didn't have space on the root for live_upgrade, so I booted from disc to upgrade, but it failed on every attempt, so I ended up blowing away / and doing a clean b44 install.

Now the zpool that was attached to that system won't stop thinking that it's mounted on another system, regardless of what I try.

On boot, the system thinks the pool is mounted elsewhere, and won't mount it unless I log in and zpool import -f. I tried zpool export followed by import, and that required no -f, but on reboot, lo, the problem returned.

I even tried destroying and reimporting the pool, which led to this hilarious sequence:

# zpool import
no pools available to import
# zpool import -D
  pool: moonside
    id: 8290331144559232496


 state: ONLINE (DESTROYED)
action: The pool can be imported using its name or numeric identifier.
        The pool was destroyed, but can be imported using the '-Df' flags.
config:

        moonside    ONLINE


          raidz1    ONLINE
            c2t0d0  ONLINE
            c2t1d0  ONLINE
            c2t2d0  ONLINE
            c2t3d0  ONLINE
            c2t4d0  ONLINE
            c2t5d0  ONLINE
            c2t6d0  ONLINE


# zpool import -D moonside
cannot import 'moonside': pool may be in use from other system
use '-f' to import anyway
#

This is either a bug or a missing feature (the ability to make a filesystem stop thinking it's mounted somewhere else) - anybody have any ideas?

Thanks,
- Rich

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss